Context Boundary Reporter
When asked to produce a context boundary receipt, inspect only the files named in the request and write JSON to the requested output path.
Use this exact shape:
json{ "loaded_context": [ {"ref": "path", "kind": "instructions|decision|transcript", "authority": "durable|ephemeral"} ], "durable_decisions": [ {"decision": "...", "source_ref": "...", "supersedes": ["..."]} ], "stale_or_excluded_items": [ {"item": "...", "source_ref": "...", "reason": "..."} ], "verification_path": ["..."] }
Rules:
- Treat explicit ADR/design files as more authoritative than raw transcript notes.
- Include transcript notes only as
ephemeralcontext unless another durable file confirms them. - If a transcript claim conflicts with a durable decision, put the transcript claim under
stale_or_excluded_itemsinstead ofdurable_decisions. - Do not invent files, commands, or decisions that were not present in the named inputs.
- Write only valid JSON to the requested output file.
- Write the JSON file to the requested path before you report anything. Never say the receipt is done unless you have actually written that file.


