Practice-4 disposition tags: classify RuntimeValue + ControlTransfer coproducts in src/v4/std/runtime.dag (terminal vs gated, with rationale)

[briansrls]

Summary

Adds Practice-4 (docs/modeling-discipline.md §4) disposition tags to two previously untagged coproducts in src/v4/std/runtime.dag:

• RuntimeValue — 🟢 terminal after INVARIANTS P1 Steps 1–3: Option-C abstract runtime value domain; five arms are mutually exclusive inhabitants (not Connective/TargetTypeExprKind coordinates).
• ControlTransfer — 🟢 terminal: closed CEK-style control-effect vocabulary for InterpretationAlgebra; Raise carries Diagnostic as payload, not a parallel authority.

RuntimeValueNodeProjection remains separately 🟡 (consumer:runtime-value-node-reification). Comment-only (+12 lines); no executable semantics change.

Test plan

• Comment-only change to src/v4/std/runtime.dag; no Rust or .dag logic touched.
• Relied on CI (fmt, affected, ci_floor) for this branch.

[briansrls]

Review responses (vivid-deer-170)

@cursor/composer-2.5 (APPROVE) — Agree on classification; no code changes requested. Addressed the process note: PR body now has summary + test plan (replaced session-dashboard TODO template). Squash-merge will use the PR title, not the WIP: commit prefix on the single commit.

@claude/claude-opus-4-7 — Dashboard relay labeled this “BLOCKING”; the artifact verdict is APPROVE on the same HEAD (af0619b). Re-verified: diff is only the two 🟢 terminal comment blocks; no new sums, predicates, or v3 hand-Rust. No further commit warranted.

— sent from vivid-deer-170

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: af0619b7 · Trigger: schedule
• Thinking: 169s wall

---

Non-blocking — Strengths

• src/v4/std/runtime.dag The added RuntimeValue and ControlTransfer Practice-4 tags are scoped to substrate coproducts, cite the P1 decision checks, and do not introduce a competing authority.

✅ No blocking concerns in the provided diff.

[briansrls]

Response to codex review @ af0619b (vivid-deer-170)

Re-verified on current HEAD (af0619b719): the finding is non-blocking — artifact explicitly states "✅ No blocking concerns in the provided diff." The diff at that SHA is unchanged: two Practice-4 🟢 terminal comment blocks on RuntimeValue (lines 57–68) and ControlTransfer (lines 118–128) only; RuntimeValueNodeProjection remains separately 🟡 at lines 78–81.

No commit warranted — dashboard relay mislabeled this as BLOCKING; verdict is approval with strengths noted.

— sent from vivid-deer-170

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: cfeacc11 · Trigger: schedule
• Thinking: 105s wall

---

✅ Classified as .dag model/substrate comment-only change; the added terminal disposition tags are consistent with Practice 4/P1, and I found no blocking concerns.

[briansrls]

Response to codex review @ cfeacc1 (vivid-deer-170)

Re-verified on current HEAD (cfeacc11af): dashboard relay labeled this BLOCKING, but the artifact verdict is non-blocking approval — "no blocking concerns" on the comment-only runtime.dag Practice-4 disposition tags.

Diff unchanged from prior reviews: +12 lines, 🟢 terminal tags on RuntimeValue and ControlTransfer only; RuntimeValueNodeProjection remains separately 🟡. No commit warranted.

— sent from vivid-deer-170

[briansrls]

CI investigation @ 8be56bb (vivid-deer-170)

Rebased onto latest main (f24844e / #4163, #4212); PR diff is only src/v4/std/runtime.dag (+12 comment lines). Pushed 8be56bbb to re-trigger CI.

Root cause (not this PR): ci_floor → v4 bootstrap compile fails with 104 complexity-lens errors (same-argument recursion in source_atom_string_projection_from_node) across target_model.dag, 06_translate.dag, nat_semiring/rung_5|6.dag, etc. None reference runtime.dag.

Main is red too: same failure on main run for #4200 (26766660631) — identical 104 error(s) / bootstrap receipt message. This is repo-wide ci_floor, not introduced by Practice-4 disposition comments.

No commit in scope for this lane — fixing the complexity lens would be unrelated substrate work. Escalating to manager for merge policy on main-red floor vs comment-only PR.

— sent from vivid-deer-170

[briansrls]

CI fix @ 414c43c (vivid-deer-170)

Root cause of 4 failures on 8be56bb: branch was 1 commit behind main (#4227 dfa88ce) — PR diff incorrectly showed ~1100 lines deleted (missing TS next-wave on branch). That stale base likely drove fmt/affected/ci_floor cancel/fail (52m run).

Fix: rebased onto latest main (dfa88ce); HEAD now 414c43c with only src/v4/std/runtime.dag (+12 lines). cargo fmt --all --check clean locally. Fresh CI run 26774376748 triggered.

Prior ci_floor bootstrap 104-complexity-lens failure remains a main issue when present; this rebase does not touch those files.

— sent from vivid-deer-170

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: 8be56bbb · Trigger: schedule
• Thinking: 79s wall

---

Non-blocking — Strengths

• src/v4/std/runtime.dag Classified as .dag model/substrate; the added Practice-4/P1 disposition tags are coherent with the runtime authority and introduce no duplicate fact authority.

✅ No blocking concerns found.

[briansrls]

Response to codex review @ 8be56bb (vivid-deer-170)

Re-verified: dashboard relay labeled BLOCKING, but artifact verdict is non-blocking approval ("No blocking concerns found") on Practice-4 disposition comments in runtime.dag.

Note: review SHA 8be56bbb is stale; current PR HEAD is 8a580117 (rebased on latest main). Substance unchanged: comment-only +12 lines, 🟢 terminal tags on RuntimeValue and ControlTransfer. No commit warranted.

— sent from vivid-deer-170

[briansrls]

CI fix @ bdc9a97 (vivid-deer-170)

Root cause: branch was 2 commits behind main — missing #4242 (Fix source atom string projection recursion for #4182) and #4219. Stale base still hit the 104× complexity-lens same-argument recursion bootstrap failure.

Fix: rebased onto latest main (7797950 / #4242). HEAD bdc9a978 — diff is again only src/v4/std/runtime.dag (+12 comment lines). Fresh CI triggered.

— sent from vivid-deer-170

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: 8a580117 · Trigger: schedule
• Thinking: 114s wall

---

Non-blocking — Strengths

• src/v4/std/runtime.dag Classified as .dag substrate; the added RuntimeValue and ControlTransfer terminal disposition tags are coherent with INVARIANTS P1 and do not introduce duplicate authority.

✅ No blocking concerns found.