Macro-4 LEGO Boundary Map — 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 3 of 90) · Editorial revision: rev1 Class: LEGO boundary map · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NOT_LEGO_COMPATIBLE guard · NO write performed.

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

---

0. Status and non-authorization

STATUS: PASS — engineering / design-readiness. Maps the LEGO boundaries so every deliverable stays independently reviewable/replaceable/discardable and the workbench never becomes a mega-machine. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Show that Macro-4 is large only at the orchestration layer (90 files) and adds no system coupling: each part is born/checked/replaced/rolled-back separately and connects only through explicit IO contracts.

2. Sources / evidence read

Macro-3 Option-D LEGO boundary map + no-mega-pipeline lock; Owner LEGO invariant; pilot-slice staging IO contract §12 (one-directional, producer-only); inspect-producer §5/§13 (B2 boundary + B2-AC-1…14). Main process, no reader-agents.

3. Accepted baseline (carried)

Owner LEGO invariant: isolated blocks / explicit contracts / born-tested-replaced-rolled-back separately; no mega-registry / mega-graph / mega-birth-pipeline / hidden coupling / auto-fix-without-gate.

4. Evidence / analysis — boundary map

Surface	Boundary	Connects via	Coupling?
B2 (primary)	inspect producer only — writes inspect_* candidates in staging	B3 inspect_* shape (IO contract)	none
Staging workbench	disposable draft surface	IO contract envelope	none (separate from production)
IO contract envelope	versioned per-block contract	explicit input/output/error/evidence/rollback/owner surfaces	none (contract, not registry)
B5 backlog / B7 gate	dependency-only	referenced, not designed	none
R1/KG (Điều 39)	cross-check-only	read-only invariant check	none

5. Contract / requirement / matrix / result

Every one of the 90 deliverables is a separate file with pointer-only cross-refs; deleting one breaks none. If any deliverable cannot be independently reviewed/replaced/discarded → mark NOT_LEGO_COMPATIBLE and HOLD. Status this run: NOT triggered.

6. Owner-gated future work

Assembling B2's neighbors (B1/B4/B5/B6/B7, S3/S4) is Owner-gated and must preserve the Codex-noted split (B1/S3, B6/S4, K3/S6 separate).

7. What remains unresolved

Physical separability of the runtime artifacts is a future-build proof; here it is a design property only.

8. Ready for GPT/Codex review

Yes — Codex should attack any deliverable that couples to another or makes B2 do more than produce inspect_*.