docs(openspec): say where work runs — this repo, or another repo via /xr:change (verbara-meta/ADR-0023) - #310
Merged
Conversation
…/xr:change (verbara-meta/ADR-0023) Rollout of the 2026-09-25 amendment to verbara-meta/ADR-0023, which carries the escalation half of the verbara-meta/ADR-0006 ruling (work runs where its commits land) on the one tracked channel that reaches every propose, apply and archive: context:.
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.
Rollout of the 2026-09-25 amendment to verbara-meta/ADR-0023 (
context:also says where work runs), which carries the escalation half of the verbara-meta/ADR-0006 ruling: work runs where its commits land. Same-shaped PR in all five code repos, touchingopenspec/config.yamlonly.What changes
context:gains one paragraph after "Cross-repo standards live in the private verbara-meta repo as ADRs.": a change whose commits land only in this repo is proposed, applied and archived here; one that needs a commit in another repo is hosted via/xr:change; a change that turns out to need one records the finding intasks.mdand recommends/xr:change. It advises rather than orders a halt, becausecontext:"cannot override … the planning boundary" (generatedpropose.md).context:also carries the hub-rule sentence: a Web-behaviour change keeps its OpenSpec change here while its code lands in Web, and that is not a cross-repo change for this rule.rules.tasks— the pack/restore line stops describing cross-repo editing and is rescoped to verifying against a locally built Sdk/Pro.Verification (the ADR-0023 runbook)
context:carries the paragraph.openspec instructionsdelivers it to proposal, tasks, apply and archive, checked on a throwaway change that was deleted and never committed. The rescopedrules.tasksline reachestasks, and the old line reaches nothing.openspec validate --all --strictrc=0 andopenspec validate --archivedrc=0.origin/main; no primary checkout was touched.No CHANGELOG entry, following the 2026-09-20 rollout of this ADR.
🤖 Generated with Claude Code