Macro-5 Staging TD Candidate Object Model — R2-B2 (2026-06-19)
Macro-5 Staging TD Candidate Object Model — R2-B2 (2026-06-19)
Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 14 of 110) · Editorial revision: rev1
Class: non-executable staging TD candidate (object model) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO write performed.
Metadata convention. Editorial revision (rev1) only. AgentData storage revision/
content_lengthauthoritative at read time.
NON_EXECUTABLE_TD_CANDIDATE. No SQL/DDL/migration/rollback script/command/schema file/table. Object roles + field families only; no real object is created.
0. Status and non-authorization
STATUS: PASS — engineering / design-only. The conceptual object model of the workbench — roles, not tables. Engineering PASS ≠ authority PASS. Default: HOLD.
1. Purpose
Name the conceptual objects a future workbench would need, as roles with field families.
2. Sources / evidence read
Macro-4 staging workbench concept (D6); B2 input/output contracts (D29/30); prompt §9.2 (object list). Main process, no reader-agents.
3. Accepted baseline (carried)
Use conceptual objects only; do not create real objects.
4. Evidence / analysis — conceptual objects (field families only)
| Candidate object | Role | Field family (illustrative, not a schema) |
|---|---|---|
| run candidate | one disposable producer run | run-id family, channel-id family, rule-set-version family, start/end family |
| input candidate | disposable projection of uncertified-row shape | identity family, metadata family, governance-role family |
| output candidate | candidate inspect results | candidate-PEN/STAMP/GATE family, candidate-reason family |
| error candidate | fail-closed failure | candidate-error-code family, candidate-reject-reason family |
| evidence candidate | append-only observation | counts family, per-failure family, reproducibility-hash family |
| delete candidate | the disposal unit | run-id / namespace family |
| provenance candidate | where input came from (staging-tagged) | source-ref family (staging only; never KG) |
| owner candidate | governance owner pointer | role-pointer family (no row written) |
| promotion blocker candidate | the firewall marker | blocked-by-Owner-gate family |
| production firewall candidate | the forbidden-surface guard | forbidden-target family |
5. Candidate / requirement / gate / result
These are roles and field families, not columns. No type, constraint, DDL, or object is declared. The model is a vocabulary for a future TD, nothing built.
6. Owner-gated future work
Declaring real objects/columns is Owner-gated future TD; forbidden now.
7. What remains unresolved
Concrete types/keys/indexes are FUTURE_TECHNICAL_DESIGN_REQUIRED.
8. Ready for GPT/Codex review
Yes — Codex should confirm no field family hardens into a schema.