T-V75E-reconcile-s-0004-composition-spectrum-dependents-s-0003
Status: closed/superseded · Impact: medium · Complexity: small
Merged PR #410 rewrote S-0004-sdlc-cli-llm-head-deterministic-tail from the
old “LLM-head / deterministic-tail” binary into a 5-point composition spectrum
that legitimizes deliberate, bounded nested-LLM steps under three guardrails.
Two dependents were never reconciled: S-0003 still models its layer boundary as
a wall (no LLM port), and S-0004 cites the still-open/proposed
D-VSLI-distributed-work-runner-architecture as normative. Until they are reconciled, the
two standards give contradictory answers to “may a lib op invoke an LLM.”
| Location | Role today |
|---|---|
docs/planning/standards/S-0003-deterministic-general-extension-points.md | Four-layer extension-point boundary; no amendment for bounded LLM judgment ports; applies_to.paths still scopes the dead plugin/** tree. |
docs/planning/standards/S-0004-sdlc-cli-llm-head-deterministic-tail.md | Composition-spectrum rewrite (PR #410); its Notes section explicitly calls for the S-0003 alignment; cites D-VSLI as normative for mechanism 2 (LLM task-runners); applies_to.paths still scopes plugin/cli/**, plugin/lib/**, plugin/skills/**. |
docs/planning/decisions/D-VSLI-distributed-work-runner-architecture.md | Still status: open/proposed — S-0004’s citation is a forward reference to an unaccepted decision. |
Proposed
Section titled “Proposed”S-0003’s boundary states that a layer-2 lib op MAY embed a bounded LLM judgment
port under S-0004’s three guardrails — a permeable port, not a wall — edited in
place per the rewrite-standards-in-place-during-alpha convention. The D-VSLI
forward reference is resolved: either D-VSLI advances to open/accepted (owner
call) or S-0004’s citation softens to non-normative. Both standards’
applies_to.paths scope the live apps/sdlc/** tree.
Approach
Section titled “Approach”- Amend S-0003’s layer-boundary prose: a layer-2 lib op may embed a bounded LLM judgment port under S-0004’s three guardrails; cross-link the S-0004 Notes sentence that demands this alignment.
- Fix
applies_to.pathsin both standards:plugin/**→apps/sdlc/**(S-0003); the threeplugin/*/**globs →apps/sdlc/{cli,lib,skills}/**(S-0004). - Resolve the D-VSLI citation: put the advance-vs-soften call to the decision owner; apply whichever edit results (D-VSLI status flip, or S-0004 citation softened to “direction recorded in”).
- Re-run
sdlc entities validateover both standards and the decision.
Files to touch
Section titled “Files to touch”| Location | Kind | Change |
|---|---|---|
docs/planning/standards/S-0003-deterministic-general-extension-points.md | modify | Boundary-as-port amendment + applies_to.paths fix. |
docs/planning/standards/S-0004-sdlc-cli-llm-head-deterministic-tail.md | modify | applies_to.paths fix; possibly soften the D-VSLI citation. |
docs/planning/decisions/D-VSLI-distributed-work-runner-architecture.md | modify | Status advance to accepted, if the owner takes that arm. |
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: S-0003 contains the bounded-LLM-port amendment and names S-0004’s three guardrails.
- AC-2: Neither S-0003 nor S-0004 carries a
plugin/**-prefixedapplies_toglob. - AC-3: S-0004’s D-VSLI reference is no longer a normative citation of an
open/proposeddecision (either the decision advanced, or the citation softened). - AC-4:
sdlc entities validatepasses on all three touched files.
Out of scope
Section titled “Out of scope”- Rewriting the composition spectrum itself (PR #410 settled it).
- Building the D-VSLI runner registry.
Dependencies
Section titled “Dependencies”- Owner call on D-VSLI advance-vs-soften (Approach step 3); no hard task dependency.
Discovery context
Section titled “Discovery context”Follow-up to merged PR #410 (S-0004 composition-spectrum rewrite), captured as B-V75E-reconcile-s-0004-composition-spectrum-dependents-s-0003 and promoted 2026-06-19. Promotion scaffolded an empty template; the authored backlog body was ported in on 2026-08-01 by the full-corpus audit.