docs(api): reword id-permanence 'no hard delete' clause (TRA-885 follow-up)#203
Merged
Merged
Conversation
…RA-885 follow-up) 'There is no hard delete' is literally false — corruption/maintenance cleanup can hard-delete a row out of band. Scope the claim to the API surface, which only ever soft-deletes. The never-reused guarantee is unchanged and holds regardless, since ids come from a sequence that never walks backward. Operator-approved. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
🚀 Preview Deployment Update ✅ This PR has been successfully merged into the preview branch. The preview environment will update shortly at: https://docs.preview.trakrf.id |
Deploying docs with
|
| Latest commit: |
6a7f469
|
| Status: | ⚡️ Build in progress... |
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.
TRA-885 follow-up — reword the
id-permanence "hard delete" clausePost-merge review (bb-253) caught that the permanence line shipped in #202 said
"there is no hard delete" — which is literally false: corruption/maintenance cleanup
can hard-delete a row out of band. This scopes the claim to the API surface, which
only ever soft-deletes.
Change (3 spots — id-format.md, resource-identifiers.md, changelog.md):
The never-reused guarantee is unchanged and holds regardless of delete type — ids come
from a sequence that never walks backward, so a deleted id's value is never re-issued.
Operator-approved (Mike). Same gate posture as #202; no consumers exist pre-cutover, so no
correctness exposure.
pnpm buildpasses.🤖 Generated with Claude Code