Repository navigation
docs(protocol): fork Issue → .opensiro case → separately consented original Issue - #37
Merged
Merged
Conversation
…l issue Pin two independent public issue publication gates, original issue dedupe, non-transfer semantics, isolated meta-worktree storage and no implicit implementation. Remove central per-fork roadmap copies already migrated to matched fork metadata and preserve source-neutral validator tests.
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
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.
Why
Fix the confusion between fork GitHub Issue, issue-local evidence in a fork's
.opensiro/, and fork-local review PR. The owner selected this workflow:Fork Issue (if approved) → research/contract under
.opensiro/issues/<case-id>/→ original Issue only on separate exact approval.There is no cross-owner GitHub native Issue transfer in this route; it is a separately created original Issue or a reference to an existing original Issue. Do not duplicate an existing original native proposal, claim comments/reactions/number are transferred, or automatically close the fork Issue.
Changes
PROTOCOL.md: new explicit four-stage issue publication/evidence route; require separate current-conversation exact approval for a public fork Issue and for a new original Issue; preflight matching parent and live owner-control; original issue dedupe; readback/cross-links; no implicit product PR, code implementation, Index regrade or automatic closure.docs/FORK_METADATA.md:.opensiro/issues/<case-id>/on the fork's dedicatedopensiro/metaworktree is authoritative for per-fork roadmap, source-native research, construction/acceptance contract and issue drafts. Distinguish this from actual.opensiro/contributions/implementation records, meta controls and GitHub Issues.docs/CAPABILITY_ROADMAP.md: route requested durable plans to verified fork issue-local storage and link accepted migrated Paperclip/Browser Harness records. Generic protocol/validator only in Upstream.docs/examples/{browser-harness-roadmap-20261117,paperclip-roadmap-20261117,paperclip-s4-constructor-acceptance-20261117}.mdfrom current Upstream. Their content was already saved/read back on the correctly parented forkopensiro/metabranches, and historical central commits are retained.CHANGELOG.mdunreleased note. No version/release change.Existing fork-local artifact sources
Validation
python3 -m unittest discover -s tests -q: 118 PASS.python3 -m compileall -q scripts: PASS.git diff --check: PASS.