KB-4958 rev 2

Macro-8 — Owner/Delegate Five-Gate Decision Record — R2-B2 Disposable Staging Workbench (2026-06-19)

11 min read Revision 2
laws-newmacro8r2-b2staging-workbenchowner-decisionauthority-recordfive-gate2026-06-19

Macro-8 — Owner/Delegate Five-Gate Decision Record

R2-B2 Disposable Staging Workbench

Field Value
Path knowledge/dev/laws-new/newlaws/consolidation/macro8-owner-five-gate-decision-r2-b2-staging-workbench-2026-06-19.md
Date 2026-06-19
Revision (editorial) rev1
Decision type Owner/Delegate authority decision record (single artifact)
Replaces The proposed 80-file Macro-8 sprawl (Owner chose "decide the 5 gates now")
Lifecycle status REQUEST: COMPLETE · GRANT: RECORDED (5/5) · EXECUTE: NOT STARTED
Runtime status Default HOLD on all runtime mutation (no write performed by this artifact)
Builds on Macro-7 preflight HOLD-before-write (Codex-accepted clean read-only baseline)

0. Status and non-authorization

This document is an authority record only. It records the Owner/Delegate's decision on five gates that have held the R2-B2 disposable staging workbench at HOLD-before-write since Macro-7. It converts "recommended, not decided" into "decided, not yet executed." It performs no runtime action of any kind.

Engineering/authority decision ≠ runtime enactment. This artifact closes the paper decision. It does not perform the runtime action. The first write-enabled step is Macro-9, which is not launched by this record.

Non-authorization locks — ALL HELD in this turn:

  • ✅ HELD — no DB write outside this KB artifact
  • ✅ HELD — no DDL
  • ✅ HELD — no DML
  • ✅ HELD — no schema / table / corpus created
  • ✅ HELD — no workbench built
  • ✅ HELD — no channel wired / bound / promoted
  • ✅ HELD — no governance_object_ownership row written
  • ✅ HELD — no Điều 0-G source patched / adopted / recovered
  • ✅ HELD — no source / law / prior report patched
  • ✅ HELD — no bad-input test run
  • ✅ HELD — no actual B2 technical design opened
  • ✅ HELD — no B2 algorithm implemented
  • ✅ HELD — no KG / universal_edges write
  • ✅ HELD — no production inspect_* write
  • ✅ HELD — no certification / promotion
  • ✅ HELD — no backlog processing
  • ✅ HELD — no pg_cron install / worker enable / host-cron change
  • ✅ HELD — Macro-9 NOT launched

1. Purpose

Record the Owner/Delegate decision that closes — at the authority/paper level — the four blockers (P1 build approval, P2/GATE-4 channel, P3/GATE-5 S2 owner, P4/GATE-3 Điều 0-G mode) plus the SB-4 isolation scheme, producing a clean, bounded GO precondition for a future write-enabled Macro-9 build of exactly one disposable staging workbench shell for R2-B2.

This single artifact deliberately replaces the proposed 80-file Macro-8 package. Rationale: the macro chain (Macro-2 → -3 → -4 → -5 → -6 → -7) was a documented non-converging loop — every iteration ended in "Default HOLD / all blockers OPEN / engineering PASS ≠ Owner-auth" with the substrate unchanged. The real blocker was never analysis; it was an Owner decision on five gates. That decision is recorded here.


2. Sources / evidence read

Source Status Evidence type Used for
Macro-7 preflight HOLD-before-write report (Codex-accepted) Read (inherited) Baseline Substrate state, OPEN gates
Macro-6 Owner Go/No-Go memo Read (inherited) Prior decision prep Gate framing
Macro-5 staging build authorization + preflight checks (channel / S2 / Điều 0-G / go-no-go) Read (inherited) Recommendation set P2/P3/P4 options
Macro-4 IO-contract + TD-entry-gate (Codex PASS_WITH_CAVEATS) Read (inherited) Contract candidates Shell scope
birth-registry-law · Điều 32 approval law · operating-rules Read (inherited) Governance anchors Authority bounds

Evidence basis: INHERITED. No fresh runtime query was run in this decision turn — the Owner elected to decide now, not re-verify. Substrate facts in §3 are carried from the Codex-accepted Macro-7 read-only baseline, not re-measured this turn, and are flagged as such.


3. Accepted baseline (inherited from Macro-7 — not re-measured this turn)

  • birth_registry: ~1,213,412 total / 1,402 certified (frozen 2026-03-21 one-shot batch) / ~1,212,010 uncertified (growing because nothing processes it).
  • uncertified-with-inspect: 0 · governance_object_ownership: 0 · universal_edges: 2199 / 0-provenance.
  • pg_cron: ABSENT · agent-api: 2 contracts / 0 birth-bound (KG-explain only), healthy :8090 · host-cron: 54 jobs / 0-birth.
  • No r2_b2 / macro7 / macro8 / workbench schema or table exists (re-confirmed: KB target path was empty before this write).
  • Substrate lives in the directus DB / public schema.
  • At Macro-7: GATE-3 (Điều 0-G), GATE-4 (channel — non-waivable), GATE-5 (S2 owner — non-waivable) all OPEN.

4. Evidence / analysis — why each decision is safe to record now

Each decision below is a paper choice that resolves one OPEN gate at the authority level without enacting any runtime change. None of them, individually or together, performs a write. The build that would consume these decisions is gated behind an explicit, separate Macro-9 launch with its own preflight and abort conditions (§8). The decisions are bounded to a disposable, prod-untouched, delete-fast shell — the smallest, most reversible unit — so the authority risk of recording them is minimal and the runtime risk in this turn is zero.


5. The five decisions (GRANT — Owner/Delegate authority record)

P1 — Owner build approval → GO (conditional GRANT)

  • Decision: Conditional GRANT for Macro-9 to build exactly one disposable staging workbench shell for R2-B2.
  • Bounds: staging-only · prod-untouched · delete-fast · abort-on-drift · strictly limited to the P2/P3/P4/SB-4 set below.
  • Not granted: Macro-9 in this turn; backlog processing; certification; promotion; B2 algorithm; any production write.
  • Execution: Macro-9 executes; nothing builds in this turn.

P2 / GATE-4 — Channel → agent-api, staging-only (directional)

  • Decision: Choose the agent-api staging-only contract as the directional channel for the staging workbench.
  • Explicitly NOT done: not wired in runtime; not bind/promote of any contract.
  • Rejected for this scope: host-cron · pg_cron · manual one-shot.

P3 / GATE-5 — S2 owner → role designated (no row written)

  • Decision: Accept the staging-only role "R2-B2 Staging Workbench Owner."
  • Holder structure:
    • Owner-of-record / accountable owner: User/Owner.
    • Delegated orchestrator: GPT.
    • Execution steward: Claude Code, only within the scope of each assigned macro (e.g., Macro-9).
  • Authority bounds: owns staging-workbench lifecycle + delete-fast + no-production-touch proof. Does NOT own production certification; cannot promote; cannot write source law; cannot write KG.
  • Not done: no governance_object_ownership row written in this step.

P4 / GATE-3 — Điều 0-G mode → accept-with-caveat (staging-only)

  • Decision: Accept-with-caveat for staging only.
  • Caveat envelope: all results are provisional / candidate only; no source patch; no production inspect_*; no certified; no promote; no backlog processing.
  • Residual (carried, not waived): real Điều 0-G source recovery remains REQUIRED before any production / certify use. Recover-first is deferred, not cancelled.

SB-4 — Isolation scheme → separate schema inside directus DB

  • Decision: A run-scoped dedicated schema inside the directus DB · zero production data · delete-fast mandatory.
  • Delete-fast mechanism: DROP SCHEMA … CASCADE in Macro-9 (if/when permitted).
  • Rejected: tagged disposable objects in public.
  • Acknowledged: a separate DB is safer but deferred for speed.
  • Hard Macro-9 abort condition: if the separate schema cannot prove no-production-touch AND delete-fast, Macro-9 must ABORT.

5b. REQUEST / GRANT / EXECUTE separation (explicit)

Stage State Meaning
REQUEST COMPLETE The five-gate question is fully specified and answered.
GRANT RECORDED (5/5) Owner/Delegate decided all five gates at authority-record level.
EXECUTE NOT STARTED No runtime action taken by this artifact.
Macro-9 NOT LAUNCHED The first write-enabled step; builds the disposable shell within granted bounds.

6. Owner-gated future work (all forbidden until Macro-9 is explicitly launched)

Macro-9, if separately launched, may only create the dedicated run-scoped staging schema and minimal empty/synthetic shell objects required to represent the disposable workbench, then prove no-production-touch and delete-fast readiness. Macro-9 must not wire/bind the agent-api staging contract, must not write any governance_object_ownership/S2 owner row, must not patch/adopt Điều 0-G source, must not implement PEN/STAMP/GATE logic, must not write production inspect_*, must not certify, must not promote, must not process backlog, and must not run bad-input tests. Any future channel wiring, owner-row write, Điều 0-G source recovery/adoption, or B2 logic belongs to a later separately authorized macro after the shell is proven safe.


7. What remains unresolved

  • Điều 0-G source recovery (deferred; required before any production / certify path).
  • agent-api staging contract not yet wired / bound (directional decision only).
  • No fresh runtime re-verification this turn — decision rests on the inherited Macro-7 baseline.
  • SB-4 abort-on-drift (no-prod-touch + delete-fast proof) must be demonstrated at Macro-9 build time.

8. Macro-9 readiness verdict

CONDITIONAL GO to author Macro-9 (the write-enabled build of one disposable staging shell), subject to ALL of:

  1. Explicit Owner launch of Macro-9 (this record does not auto-launch it);
  2. Macro-9 preflight re-confirming the inherited baseline with a fresh read-only check;
  3. SB-4 abort condition satisfied — prove no-production-touch + delete-fast before/while building;
  4. Build stays strictly within the P1–SB-4 bounds (disposable shell only; no B2 logic, no certify, no promote, no backlog).

This is NOT an automatic launch and NOT a grant to execute now.


9. Ready for GPT / Codex review

Yes. This single artifact replaces the proposed 80-file Macro-8 package and is ready for GPT review, then Codex adversarial review. If accepted, the Owner may separately authorize a write-enabled Macro-9 build of one disposable staging workbench shell. No automatic build.

Back to Knowledge Hub knowledge/dev/laws-new/newlaws/consolidation/macro8-owner-five-gate-decision-r2-b2-staging-workbench-2026-06-19.md