docs(r3): Q-LBP option (b) + Q-Class-2 option (a) RATIFIED — canonical authority propagation

[briansrls]

Summary

• Brian directive 2026-05-06: "author the propagation PR, option (b) locked"
• Resolves parallel-authority drift identified per feedback_parallel_representation_debt: the two ratifications at gunbc#828 #issuecomment-4385329180 (zesty-bear-812 Director session) had landed S2 canvas + R4 carve-out routing ledger on main (PR R3 Substrate #1782) but canonical authority docs still showed Q-LBP-R3-Closeability as RED + Class 2 Workflow capabilities integration #61 as chain-broken
• Propagates Q-LBP-R3-Closeability option (b) + Q-Class-2-Chain-Break option (a) to canonical authority across 3 docs / 4 sections / multiple cite-points

Two ratifications propagated

Q-Lens-Behavioral-Parity-R3-Closeability — option (b) RATIFIED

T-LBP narrows R3 scope to complexity + cost lenses only:

• Q1 (option a) REJECTED — full T-LBP scope requires landing 4c caller-side effect-set pinning carrier inside R3; substrate-fact-introduction-without-confirmed-bridge-consumer; circular against R3 close per INVARIANTS.md P1
• Q2 (option b) RATIFIED — both in-R3 lenses share T-E-P producer dependency; closing simultaneously is critical-path fastest
• Carved to R4 per docs/r4-carve-out-routing.md (commit 811de219f):
  • C1 §1.8 BB-2: Implement per-node corpus test generation with level 1a/1b support #81 parallelism_lens_behaviorally_complete (Stage 2e walker port + rewire)
  • C2 §1.8 Blue Team Lane 1: RF-B1, SDLC-1 through SDLC-4 #82 effect_enumeration_lens_behaviorally_complete (4c caller-side effect-set pinning carrier P1 substrate-fact-introduction)
  • C3 §1.8 Implement auth_input config and fail-closed auth validation (RT1-RT4) #83 lens_capability_register_zero_proxy_zero_stub NARROWED to in-R3 lenses (complexity + cost)

Q-Class-2-Chain-Break — option (a) RATIFIED

• Narrowed gap-test (function-valued data + evaluator consumption; lens-behavior out of scope) is correct as Class 2 closure
• Substrate fact under test = "function-valued data is first-class", not "any specific lens reaches BEHAVIORALLY COMPLETE on this input" — narrowing strips the non-substrate axis
• §1.8 Workflow capabilities integration #61 RED → DECLARED YELLOW; chain-break dissolved
• Single-prereq-blocked on T-E-P-Producer-Broadening Phase 1 + E6-G0d (E6-G0d landed at feat(v3-eval): E6-G0d constructor Callable runtime execution #1813)
• S1 worker brief authored at docs/briefs/r3-substrate-s1-gap-test-representative-worker.md

Files changed

File	Change
docs/r3-program-plan.md	§10.3 Q-LBP-R3-Closeability row HOLD→RATIFIED option (b); §10.3 Q-Class-2-Chain-Break row ENGAGE-NOW→RATIFIED option (a); §1.4 Class 2 chain-break narrative dissolved; §1.4 line 8 R3 close definition (Q-LBP removed from unresolved); §1.8 rows #79-83 split (IN R3 / R4-CARVED / NARROWED); §1.8 row #61 RED→DECLARED YELLOW
docs/r3-structure.md	§"Acceptance" T-Lens-Behavioral-Parity gate descriptions: per-gate IN R3 vs R4-CARVED vs NARROWED markers
docs/r3-design-schedule-2026-05-06.md	§S1 ENGAGE-NOW→CLOSED (option a RATIFIED); §S2 ENGAGE-NOW→CLOSED (option b RATIFIED) with full cascade-impact summary

Test plan

• §10.3 Q-LBP-R3-Closeability row reads RATIFIED 2026-05-06 (option b) with verbatim Director-thread citation
• §10.3 Q-Class-2-Chain-Break row reads RATIFIED 2026-05-06 (option a)
• §1.8 ledger rows Add corpus-based test generation for DAG nodes #79-83 split markers consistent across r3-program-plan.md + r3-structure.md
• §1.4 Class 2 chain-break narrative dissolved (chain-break designation gone; original analysis preserved for traceability)
• §S1 + §S2 in design-schedule reflect CLOSED state with cascade-impact summary
• Cross-references to docs/r4-carve-out-routing.md C1/C2/C3 in all touch-points
• Cascade work (T-E-P P1 / S10 / quick-koi-190) intentionally NOT touched — authority-doc cleanup, not scope reopening

Cross-session coordination note

Both Director sessions (deep-wolf-155 + zesty-bear-812) share operator authority but don't share state by default. The ratification was made via #828 thread; this PR reflects it on main canonical authority. Substrate Mgr (#1739) has been asked to cross-relay future Director-tier ratifications across both inboxes to prevent drift.

🤖 Generated with Claude Code