docs: capture a rule the plans deletion would erase - #73
Merged
Conversation
Reviewing the planning documents before removal found one decision still in force with no current record: job creation goes through domain endpoints, and there is no POST /job. The rule is expressed as an absent endpoint, so nothing a reader opens mentions it. Relocating what the architecture documents say would not produce it, because those documents do not say it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Thank you for contributing to this project! 😊🕹️ |
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.
Adds task 3.9 to
specify-documentation-homes.Section 4's review of the 76 planning documents found seventy that were implementation choreography for shipped work, and six carrying decision rationale. Five of the six describe architecture the repository still documents. One does not.
The rule
The unified-domain-endpoint plan decided to remove
POST /joband route all job creation through domain endpoints. Verified still in force: the onlypost:remaining on the job API is/api/job/{id}/retry, an action on an existing job rather than a way to create one.No current document states it — not
api-guidelines.md, notarchitecture.md, notCLAUDE.md.Why it needed its own task
The rule is expressed as an endpoint that is absent. Nothing a reader opens will mention it, and a contributor adding a domain has no way to discover the constraint before violating it.
Tasks 3.1 and 3.2 relocate requirements from
principles.md,api-guidelines.md, andjob-architecture.md. Since none of those state this rule, lifting their contents would not produce it — it would have fallen through the same wayspecsfell through section 4's repository list.Without this task, removing
docs/plans/deletes the last written record of a rule still binding new work.The other seventy-five need no backfill. The architecture documents describe what exists, nobody is re-litigating those decisions, and
git log docs/plans/answers anyone who asks why.🤖 Generated with Claude Code