Conversation
Two maintainer rulings from the v0.8.0 review, landed together because both came out of the same read of what the release had left standing. spc-26 is closed and itd-121 ships. The record-id dispatch form has been live for some time — `abcd itd-20`, `spc-26`, `adr-23` and `iss-110` all render their path, status, links and next moves — while its spec sat in `open/` and its intent in `planned/`. That is the silent half of the definition of done: nothing runs the close for you, and a planned intent is not refused by the release cut, merely unseen. It was deliberately not closed during the v0.8.0 cut. The changelog is composed from the records that reach a terminal folder since the anchor tag, so closing it mid-cut would have written a 0.8.0 line for work that shipped earlier, and broken the completeness bijection the section had already proved. Closing it now moves that line to the next cut instead, which is still not the release that carried the work. `spec close` has no `--shipped-in` escape, unlike `capture resolve`, so there is no way through this verb to close the record and keep it out of the cut. Worth deciding at the next cut whether the line stands or the escape is worth adding. The ahoy ruling is recorded rather than implemented. `ahoy install` defaults `--docs-target` to `both` and plants a block opening "Managed by abcd" into a target repository's committed CLAUDE.md and AGENTS.md, while `prepare-this-repo` promises in its acceptance criteria that no abcd-internal content appears in any committed artefact. The v0.8.0 gate caught the contradiction and the prose was corrected to match the code; the ruling is that the promise was the right end and the behaviour is what should change, so implementing it reverses that correction deliberately. The record carries what the change has to settle rather than just the verdict: the marker is what promotes a folder to managed-repo, so a nameless block must still classify; the rule loader has to keep being discoverable; and the real question is the `both` default rather than the wording of the block. Refs: iss-2609110944498549, iss-110 Assisted-by: Claude:claude-opus-5[1m]
…-record-ahoy-ruling
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.
Two maintainer rulings from the v0.8.0 review, landed together because both came out of the same read of what the release had left standing.
spc-26 is closed and itd-121 ships: the record-id dispatch form (
abcd itd-20,abcd iss-110rendering a record's path, status, links and next moves) has been live for some time while its spec sat inopen/and its intent inplanned/. It was deliberately not closed during the v0.8.0 cut, because closing it mid-cut would have written a 0.8.0 line for work that shipped earlier. Closing it now puts that line in the next cut instead, which is still not the release that carried the work; the intent'sshipped_inis left for the cutting session to stamp.The second ruling files iss-2609110944498549:
ahoy installmust not write abcd by name into a target repository — adoption stays nameless.Brought up to today's
mainby merge;lint-decisions,record-lint,lint-issuesanddocs-lintare clean on the branch.Refs: iss-2609110944498549, iss-110
Assisted-by: Claude:claude-fable-5-1