docs(site): Mon SEO — registry model rights + deprecated/revoked Q&As - #143
Merged
Merged
Conversation
…ed lifecycle Q&As Two honest Q&As grounded in registry spec 005, spec 026 v1.1.0 and decision-log entry 127: what the model rights record declares (signed declaration, not legal certification) and how deprecated/revoked versions behave for ranges vs exact pins. States open work plainly: traverse#1598 (CLI/runtime), registry#631 (crate exact-pin alignment + publish), registry#623 (agent backfill). Wire hub, llms.txt and relatedLinks.
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 SEO Q&As for the registry spec 026 work that landed last week:
/questions/does-the-registry-record-model-rights.html/questions/what-happens-when-a-capability-version-is-revoked.htmlGrounded in registry spec 005 (FR-004), spec 026 v1.1.0 (contract signature over committed bytes), and decision-log entry 127 Q11. Open work stated plainly: traverse#1598, registry#631, registry#623. No new product claims; Traverse-side enforcement is marked not shipped.
Wired into the questions hub, llms.txt, and relatedLinks on the attribution, contract-versioning, and capability-registry pages.