Governed context assembly v1

This is an additive contract for evidence packages. It does not change the frozen Bundle Wiki profile or the OKF 0.2 core.

• Producer index: concepts, whole evidence passages, directed assertions and explicitly scoped evidence requirements.
• Assembled package: resolved concepts, selected records, traversal paths, provenance, omissions and evidence sufficiency.
• Evaluation case: independent assessor requirements; these must not be supplied to the assembler as retrieval seeds.
• Synthetic controls: declared mutations and expected failure handling, kept separate from source-backed inputs.
• Common definitions: closed shapes shared by those contracts.

The TypeScript contract is maintained in apps/okf-explorer/src/lib/context/types.ts. Validate JSON with scripts/check_context_assembly.py; the schema registry resolves these local files only. Unknown fields are rejected. Missing provenance and authority remain representable where the engine needs to report incomplete evidence: passing shape validation alone is not evidence sufficiency. Runtime validation also rejects non-string review status, invalid original assertion IRIs and undeclared alias-object fields before assembly.

Package identity is SHA-256 of canonical JSON with context_id and budget.used_bytes omitted. The final byte count measures the complete UTF-8 JSON package. Evidence items are retained whole or omitted with a reason. The package never contains a generated AI answer.

See the implementation guide and evaluation method.

Optional full-source discovery

The governed package may contain a retrieval object recording whole-page lexical candidates, corpus coverage, query terms, transfer budgets and omissions. This is separate from concept resolution and completeness requirements. See the full-source decision.

Optional logical evidence units and corpus v2

• Evidence-unit metadata describes exact ordered UTF-8 source spans, explicit joins and boundary uncertainty. It is optional on existing evidence records. Whole-text provenance hashes retain their meaning.
• Corpus v2 manifest separates physical page counts from retrieval-unit counts and declares bounded ID ranges for loading referenced destinations. It retains the existing posting and record-shard formats.

See the decision for source-inclusion, whole-unit and authority boundaries. The consumer checks cross-field offsets, ordering, fragment hashes and budgets in addition to these shape schemas.