Macro-5 Staging Object: Provenance Candidate — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 29 of 110) · Editorial revision: rev1 Class: staging object candidate (provenance) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO write performed.

Metadata convention. Editorial revision (rev1) only. AgentData storage revision/content_length authoritative at read time.

NON_EXECUTABLE_TD_CANDIDATE. Conceptual object only. Staging provenance only — never KG universal_edges.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. The provenance conceptual object: where a staging input came from, tagged STAGING. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Describe staging-local provenance without ever touching KG provenance (R1 lane).

2. Sources / evidence read

Macro-4 R1/KG scope lock (D67); no-mega-graph lock (D69); FRESH universal_edges 2,199/0-prov. Main process, no reader-agents.

3. Accepted baseline (carried)

B2 must not write KG provenance; Điều 39 (2,199/0-prov) is respected, not resolved.

4. Evidence / analysis — provenance candidate

Aspect	Description (no schema)
role	a staging-local pointer to where the input projection came from
field family	source-ref (staging only), sample-method, run-id
never	a universal_edges write; a KG edge; a provenance tag on production
FRESH	universal_edges 2,199 / 0 prov — untouched, read-only

5. Candidate / requirement / gate / result

Staging provenance is a disposable breadcrumb inside the run's delete unit — categorically distinct from KG provenance. Any edge/graph write = R1_SCOPE_CREEP → HOLD. No provenance is written here.

6. Owner-gated future work

KG provenance is the R1 lane, a separate Owner-gated workstream; not opened here.

7. What remains unresolved

Điều 39 (2,199/0-prov) remains OPEN, untouched.

8. Ready for GPT/Codex review

Yes — Codex should confirm staging provenance never crosses into the KG lane.