Macro-4 Staging Workbench Lifecycle — R2-B2 (2026-06-19)
Macro-4 Staging Workbench Lifecycle — R2-B2 (2026-06-19)
Date: 2026-06-19 · Workstream: R2-B2-MACRO-4-STAGING-WORKBENCH-IO-CONTRACT-TD-ENTRY-GATE-2026-06-19 (Deliverable 8 of 90) · Editorial revision: rev1
Class: staging workbench lifecycle · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · CONCEPT-ONLY · NO write performed.
Metadata convention. Editorial revision (rev1) only. Storage revision/
content_lengthauthoritative at read time.
0. Status and non-authorization
STATUS: PASS — engineering / design-only. The conceptual lifecycle of the workbench surface and the draft runs inside it. Engineering PASS ≠ authority PASS. Default: HOLD.
1. Purpose
Define the workbench lifecycle so "draft → test → reject → delete" is a clean, repeatable loop with production untouched.
2. Sources / evidence read
Pilot-slice staging IO contract §3/§9/§10; operating-rules v7.58 (Assembly First; "/tmp not SSOT"); inspect-producer §10 (rollback unit). Main process, no reader-agents.
3. Accepted baseline (carried)
"Nháp thoải mái" is safe because (a) nothing a draft does writes production, and (b) the whole experiment can be thrown away in one delete-fast with production provably untouched.
4. Evidence / analysis — lifecycle stages (conceptual)
| Stage | What happens | Constraint |
|---|---|---|
| Provision | a disposable workbench surface is stood up (future build) | separate from production; Owner-gated |
| Seed | a bounded disposable sample mirroring uncertified-row shape | no live-data extraction designed here |
| Exercise | a candidate B2 produces candidate inspect_* (genuine per-stage) |
PEN→STAMP→GATE; one column per inspector; fail→staging audit |
| Observe | staging-tagged evidence records counts/ids/failures | records, never decides |
| Reject/Adjust | a wrong design is discarded; a new one drafted | no production cleanup needed |
| Dispose | the whole surface deleted in one unit | production byte/count-identical before/after |
5. Contract / requirement / matrix / result
The lifecycle has no automatic promotion stage: a validated candidate is evidence, not a production write. Promotion is a separate Owner gate outside the loop. The loop never touches production, never certifies, never canonicalizes.
6. Owner-gated future work
Provisioning/seeding/exercising/disposing are all Owner-gated future TD; forbidden now.
7. What remains unresolved
Seed population (how a sample is obtained) and the disposal mechanism are FUTURE_TECHNICAL_DESIGN_REQUIRED.
8. Ready for GPT/Codex review
Yes — Codex should confirm the lifecycle has no implicit staging→production step.