drift: four defects the context-weight sweep found in passing #103

New issue

Closed

opened 2026-08-10 14:49:03 +00:00 by john · 1 comment

john commented

2026-08-10 14:49:03 +00:00

Owner

Four prose/code drifts found while sweeping for context weight. None is a token cut; all four are the class self-verify exists to catch and currently does not.

cadence-core/workflows/execute.md:241 names "the phase_start line in start". There is no step named start — the line is appended in git_guard.
cadence-core/workflows/execute.md:36 resolves workflow.test_command, but it is consumed only at :369, on the parallel path. A sequential run resolves a config key it never reads.
cadence-core/references/config-reach.md:136-138 names workflows/execute.md as the reach site for the three parallelization.* keys. Correct today; moves if the execute_parallel deferral lands. Track alongside that change.
cadence-core/references/seams.md:236-240 says git-guard.md is consulted at steps 1, 2, 3 "and in its guardrails block", but skills/cad-land/SKILL.md's current guardrails cite no git-guard. Either the sentence is stale or the guardrail was dropped — resolve which. If the cad-land guardrails compression lands, fix this in the same commit.

Worth considering

1 and 2 are both "prose names a step or key the code does not use at that point". Check 2 already lints script invocations and check 1 lints config keys for existence, but neither checks that a resolved key is consumed on the path that resolves it. If that is cheap to add, it belongs with the other self-verify work in this milestone.

Four prose/code drifts found while sweeping for context weight. None is a token cut; all four are the class self-verify exists to catch and currently does not. 1. **`cadence-core/workflows/execute.md:241`** names "the `phase_start` line in `start`". There is no step named `start` — the line is appended in `git_guard`. 2. **`cadence-core/workflows/execute.md:36`** resolves `workflow.test_command`, but it is consumed only at `:369`, on the parallel path. A sequential run resolves a config key it never reads. 3. **`cadence-core/references/config-reach.md:136-138`** names `workflows/execute.md` as the reach site for the three `parallelization.*` keys. Correct today; moves if the `execute_parallel` deferral lands. Track alongside that change. 4. **`cadence-core/references/seams.md:236-240`** says `git-guard.md` is consulted at steps 1, 2, 3 "and in its guardrails block", but `skills/cad-land/SKILL.md`'s current guardrails cite no git-guard. Either the sentence is stale or the guardrail was dropped — resolve which. If the cad-land guardrails compression lands, fix this in the same commit. ## Worth considering 1 and 2 are both "prose names a step or key the code does not use at that point". Check 2 already lints script invocations and check 1 lints config keys for existence, but neither checks that a resolved key is consumed on the path that resolves it. If that is cheap to add, it belongs with the other self-verify work in this milestone.

john added this to the v2.6.2 milestone

2026-08-10 14:49:03 +00:00

john commented

2026-08-12 15:10:49 +00:00

Author

Owner

All four drifts fixed in the current tree: the 'start' step reference is gone from execute.md, workflow.test_command resolves only at its consumer on the parallel path, config-reach.md names execute-parallel.md for the moved keys, and the stale seams.md guardrails claim is gone.

john closed this issue

2026-08-12 15:10:49 +00:00