The cycle's sixth step was not stack-neutral, and the next repository proved it - #252
Merged
Conversation
… proved it Step 6 named spec_validate, spec_drift and specs/. That is true for a generated .NET application and meaningless for an npm library — which is the next repository due to carry this text, and the reason the flaw surfaced before it shipped anywhere it would have been wrong. The step now says what it always meant: run THIS repository's own contract check, whatever proves that what is committed still equals what is built, and get it clean. The engine, the PublicAPI files, the export-and-docs gate — each repository's skill names its own, because the check is stack-specific while the sequence is not. The application-shaped detail did not disappear; it moved into the sentence that says which repositories it describes. skills-parity now also holds goldpath's own copy of cycle.md identical to the one the templates ship, and compares only that file for the root layer — the maintainer's skills and hook are deliberately different shapes under D2 and D4, and a gate that demanded they match would be enforcing the opposite of the decision. Verified against a planted drift in the root copy. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
omercelikdev
added a commit
that referenced
this pull request
Sep 8, 2026
…ft a gap (#253) Every repository named in the delivery-cycle RFC now carries the layer: mockifyr #417, qorpe/ui #49, mediant #166, api-portal #74, factoring-poc #7, specdrift #13, specanchor #1. Only coexist's regeneration and D6's spec chain are left. The two repositories that carried NO agent layer also carried no docs gate, and writing one for each found live drift in both — recorded in the row because a gate that never caught anything is a gate nobody trusts: specdrift README pinned 0.4.1 while the csproj shipped 0.4.3, so the Docker tag and Action ref in the run-it-anywhere table were two releases stale. `--help` printed `specdrift mcp` below the prose about the other two verbs. specanchor the ledger called the shipped licence gate "still owed"; the README's "Next:" named the gates, the CLI and MCP, all three built and exercised in CI; `specanchor mcp` was documented nowhere at all; one section was written in Turkish, in a repository whose whole product is an auditable trail read by client-side reviewers. T28 records what the sweep exposed. cycle.md now lives in nine places and nothing compares the copies ACROSS repositories — skills-parity.sh only compares the three inside this one. The cycle has already been revised once (#252 made §6 stack-neutral); the next revision reaches adopters only if a person remembers, and `goldpath init` does not ship the skills family because template-completion D5 assigns that to the unbuilt transformation pack. The thread carries the owner's no-extra-spend constraint in its proof column, because that is what rules out the obvious answers. All five gates green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 6 named
spec_validate,spec_driftandspecs/. That is true for a generated .NET application and meaningless for an npm library — which is the next repository due to carry this text, and the reason the flaw surfaced before it shipped anywhere it would have been wrong.The step now says what it always meant: run this repository's own contract check, whatever proves that what is committed still equals what is built, and get it clean. The engine, the PublicAPI files, the export-and-docs gate — each repository's skill names its own, because the check is stack-specific while the sequence is not. The application-shaped detail did not disappear; it moved into the sentence that says which repositories it describes.
The parity gate grows one copy
skills-parity.shnow also holds goldpath's owncycle.mdidentical to the one the templates ship — and compares only that file for the root layer. The maintainer's skills and hook are deliberately different shapes under D2 and D4, and a gate demanding they match would enforce the opposite of the decision.Sixteen files across three copies, five deliberate divergences accounted for. Verified against a planted drift in the root copy.
🤖 Generated with Claude Code