# Context Assembly Plan

Toolkit schema: `PAISEH-TK-1.0`
Source artifact: Chapter 5 **Context Assembly Plan**

Complete `../common-artifact-header.md` first. Use one plan per distinct task or evidence contract.

## 1. Purpose and Ownership

- Supported behavior and task ID:
- Context owner and plan version:
- Prompt and harness dependencies:
- Change rationale and compatibility:

## 2. Evidence Requirements

| Requirement ID | Required fact/evidence | Required/optional | Freshness/effective-time need | Minimum support | Explicit non-requirements |
| --- | --- | --- | --- | --- | --- |
| | | | | | |

- Evidence-sufficiency rule:
- Minimum viable context package:

## 3. Actor, Purpose, and Permission Scope

- Actor and tenant/domain inputs:
- Declared purpose and workflow role:
- Authorization decision reference and enforcement stage:
- Filtered unit: source / record / field / passage / memory item
- Time-dependent scope and cache/index constraints:
- Denial behavior that does not reveal protected metadata:

## 4. Source Policy

| Source | Authority domain | Primary/derived/advisory/user-asserted | Provenance | Freshness/effective time | Permission scope | Unavailable/stale behavior |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |

- Conflict precedence rules:
- Conflicts that prohibit automatic resolution:

## 5. Assembly Pipeline

| Stage | Input | Decision/method | Output metadata | Failure state |
| --- | --- | --- | --- | --- |
| Eligibility and scope | | | | |
| Retrieval | | | | |
| Normalization and provenance | | | | |
| Deduplication and ranking | | | | |
| Coverage and conflict handling | | | | |
| Shaping and budgeting | | | | |
| Package validation | | | | |

- Query derivation and tie-breakers:
- Coverage and stopping rule:
- No-eligible-evidence representation:

## 6. Shaping, Memory, and Lifecycle

| Allocation | Hard/elastic | Capacity/priority | Shedding or overflow behavior |
| --- | --- | --- | --- |
| | | | |

- Protected-fact invariants and original-evidence recovery:
- Lossless and allowed lossy methods:
- Ordered shedding and minimum-package overflow behavior:

| Memory class | Scope/purpose | Owner/source | Provenance/precedence | Correction/deletion | Retention/expiry | Read eligibility |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |

- Invalidation triggers:

## 7. Context Package Contract and Checks

- Package schema/version:
- Item provenance, authority, effective-time, and transformation lineage:
- Missing-evidence and conflict representation:
- Completeness states: complete / partial / stale / conflicting / unauthorized / unavailable
- Budget, shedding, timestamp, and assembly-version metadata:

| Check | Requirement/invariant | Test input | Expected assembly result | Evaluation handoff |
| --- | --- | --- | --- | --- |
| | Permission, freshness, coverage, provenance, conflict, protected fact, or budget | | | |