GPT Review — IU b/c/f Pure Read-Only Proof + Next Live Apply

Date: 2026-05-28 Reviewer: GPT Council via Web Connector fallback

Evidence considered

• Agent report for IU_B_C_F_PURE_READONLY_LIVE_PROOF_100000X.
• KB search result for knowledge/dev/reports/architecture/iu-b-c-f-pure-readonly-live-proof-2026-05-28.md.
• Existing command/refactor packs for IU b–f.

Verdict

READ_ONLY_PROOF_ACCEPTED_NEXT_LIVE_APPLY_BCF_DOT_WRAPPER

The read-only proof passed and is accepted. b, c, and f are now live-proven by SELECT-only evidence.

The 11m51s runtime is not a failure of the Agent; it shows that the prompt scope was intentionally small after safety correction. To reach the target 45–60m, the next macro should bundle the next meaningful safe live-apply step rather than another planning/refactor pass.

Accepted findings

1. Test b PASS: domain/professional axis can be queried live. legal_domain has applied values and knowledge_systems maps to 16 law_unit IUs from Điều 39.
2. Test c PASS: tree/subtree is queryable live via fn_iu_subtree; zero orphans, cycles, and dangling parents in the checked scope.
3. Test f PASS: all 3 SQL links validate/resolve read-only against live objects; enabled=false does not block validation.
4. Caveat: 23 units have stale stored axis_c_depth=0 despite parent. fn_iu_subtree relative depth is authoritative; stored depth should not be trusted until refresh/autowire is fixed.
5. No mutation was observed: dot_iu_command_run stable at 45 and no DDL/DML was performed.

Next operating decision

Proceed to the next safe live-apply macro:

IU_B_C_F_ADDITIVE_DOT_WRAPPER_AND_HARNESS_LIVE_APPLY_100000X

This macro should be C2 additive implementation, not C1 read-only.

It may create/patch read-only wrapper functions and DOT command catalog rows, then run the DOT-callable harness for b/c/f. It must not touch gates, event delivery, split/merge, or 4 Mothers.

Why this is the right scale

The previous macro proved read-only capability. The next macro must turn that proof into reusable DOT automation:

• preflight apply channel;
• backup and rollback;
• object diff;
• existing object reuse check;
• add only missing STABLE/read-only wrappers;
• add/patch DOT catalog rows;
• run b/c/f through DOT/harness;
• produce evidence rows and KB report;
• verify no forbidden tables changed;
• verify rollback path if tests fail.

This is a real 45–60m class macro while still bounded and safe.

Forbidden still applies

No 4 Mothers implementation. No gate flip. No event type registration. No split/merge. No delivery. No Qdrant/vector write. No schema/table/template/collection creation beyond approved additive functions/catalog rows needed for DOT wrapper automation.