Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@
**Release status:** a protocol version merged to `main` is **not** automatically a published GitHub Release. Check [published Releases](https://github.com/opensiro/upstream/releases). At the 2026-11-16 review, v0.13.0 was the latest published release, and the [v0.16.0 consolidated candidate](docs/RELEASE_CANDIDATE_v0.16.0.md) awaits final owner approval. Individual v0.14–v0.16 history entries below remain valid intermediate main snapshots, not claims of three separate GitHub Releases.

## Unreleased
**C-first capability roadmap + approved v2 fork Issue template (unreleased):** Roadmap research now explicitly seeks a minimal, user-justified first-party `C` construction path for relevant functions without confirmed `C` or `A`. Existing `A`/`A(P)` and `C`/`C(P)` are exempt from mandatory C targets; `P` rights remain legitimate. Distinguish P0 C sufficiency, P1 enabling dependencies and P2 optional independent modes. Adopt the eight-section evidence and target-matrix fork Issue template v2; require a source-native coverage/acceptance and no-grade gate. No automatic implementation, Index write, version bump or external publication.

**Generic fork-local roadmap Issue template (unreleased):** Add a concise, project-neutral, evidence-first Issue skeleton for Opensiro's own verified working forks. It ties the user's outcome to existing original code/Issues/PRs, optional VSM-derived priorities, acceptance, native alternatives, paired cost measurement and a conditional handoff, while keeping case artifacts on `opensiro/meta`. This is distinct from the existing external architecture Issue template and authorizes no public Issue, implementation or new grade. No named-fork research edited, version bump or Release.

**Fork Issue → issue-local evidence → separately consented original Issue (unreleased):** Source-pinned case roadmaps, construction contracts, drafts and results belong in the verified matching fork's `opensiro/meta:.opensiro/issues/<case-id>/`. Public fork GitHub Issue creation and external original Issue publication each require their own exact owner approval; dedupe original issues and link rather than manufacture duplicates. Do not claim GitHub cross-owner native transfer, mirror comments/reactions, or auto-close internal Issues. Named Paperclip and Browser Harness case examples migrated to their forks; central Upstream retains generic methods and source-neutral validator fixtures. No product code, Index grade, version bump or Release.
Expand Down
6 changes: 5 additions & 1 deletion PROTOCOL.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,10 +36,14 @@ Read [docs/FORK_METADATA.md](docs/FORK_METADATA.md) for the initial JSON contrac

**Route contract.** `upstream roadmap OWNER/REPO` is a **conversational, named-original, source-analysis-read-only-by-default architecture route**, with an explicitly requested persistent case stored only in the verified fork's `opensiro/meta:.opensiro/issues/<case-id>/`. It remains separate from `upstream upgrade` and both batch commands. It is not a new CLI command, research batch, VSM assessment, implementation mandate, publication approval, or contribution state. A source-backed **plan-only** architecture issue draft may be a complete success with zero code changes and zero published PRs. Follow [Capability Roadmap](docs/CAPABILITY_ROADMAP.md), the [fork-local roadmap Issue template](templates/FORK_CAPABILITY_ROADMAP_ISSUE.md) for OpenSiro discussion, and the separate [external architecture Issue template](templates/EXTERNAL_ARCHITECTURE_ISSUE.md) for a permitted original-project proposal.

**Roadmap default objective — function-scoped C sufficiency, not grade maximization.** For each relevant function without confirmed `C`/`C(P)` or `A`/`A(P)` at the declared first-party boundary, **investigate a minimal, useful, function-specific construction path sufficient for a future `C` witness**. First resolve stale `?` evidence and source drift, and retain `P` as a valid autonomous-actor-absent, parent-governed arrangement with reserved authority. A function already at `A`/`A(P)` is **not required** to be converted into `C`: `A` does not logically prove a reusable `C` constructor, but it satisfies this route's default no-mandatory-C-work exclusion. `C`/`C(P)` also need no duplicate constructor target. Prioritize user need and defensible engineering materiality; do not manufacture changes simply to fill a historical low grade. If no useful `C` target survives current-source validation, explicitly report `NO_USEFUL_CHANGE` or `NEEDS_EVIDENCE`, with reasons, rather than silently substituting unrelated general enhancements.

**Mandatory research priority and sufficiency receipt:** `P0` = the strongest qualified, useful **C-target capability** with complete proposed minimal coverage; `P1` = dependencies and integration/authority/test changes required to enable that target (these may execute first); `P2` = optional independent modes `C(P)`/`A(P)` and other separately justified enhancements. These are **work priorities**, not a maturity ordering of `A`, `C`, `P` and **not a universal grade ladder**. For every candidate, show accepted historical state, actual current-source evidence, original Issues/PRs with status, target and smallest necessary new changes, exact decision/feedback constructor, rights, supported reachability, observable positive/negative acceptance and **why the combined set would be sufficient** for a later `C` assessment. State what remains unverified. When a selected function already has `A`/`A(P)` or `C`/`C(P)`, mark it **excluded from mandatory C targets**; any further source-native enhancement needs a separate material user benefit. Preserve the legitimate parent `P` boundary.

1. **Freeze one source and check rights.** Pin the actual original default HEAD, source boundary/recursion, existing Index assessment file SHA plus historical `review_ref`/`reviewed_at`, Profile/Methodology versions and observed relevant PR/issue refs. An unmerged reassessment is not canonical. Perform the existing read-only license/formalities and autonomy preflights. Verify fork and owner controls before effectful work; unreadable metadata is unknown, not permission.
2. **Recommend re-assessment when the accepted assessment is older than one month.** At the roadmap observation date, compare against the most recent **successful Index semantic re-review / reassessment** recorded for this harness (the accepted `reviewed_at`, or a later `last_checked_at` only when it is backed by successful longitudinal evidence under the applicable Skills Methodology). If **more than 30 calendar days** have passed, **recommend a source-pinned Index re-assessment before finalizing confident VSM gap/ownership claims**; also recommend it sooner when material product evolution is observed. Cite the dated canonical assessment, source HEAD and any actual Index re-review issue/PR; if none exists, offer the Index-owned `[Assessment re-review]` route. A calendar threshold is a **soft freshness recommendation, never an automatic grade change, mandatory waiting gate, new batch/round, or permission to open an issue or PR**. Without a completed accepted re-assessment, the roadmap may continue **read-only, explicitly provisional**, grounded in current original code and with the old accepted vector labeled historical. Unknown freshness remains unknown; a superficial source check, open issue/PR, or roadmap itself cannot reset it.
3. **Map real work and residual outcomes.** Identify shipped behavior, open or merged PR heads/diffs/tests, issues, experiments, and adjacent maintainer governance *separately*. For each relevant S1/S2/S3/S3*/S4/S5 mechanism name a native actor/task, disturbance, decisive owner/right, enforcement, feedback/closure and unserved user outcome. Record current main → competing PR → residual user capability with evidence and alternative; a missing historical grade does not independently justify a feature, a new controller, or a claimed grade.
4. **Design for useful composability before autonomy.** Prioritize a **function-specific** constructor that, when actually shipped and verified, can support `C`, not generic routing/hooks or an unrealized plan. **If the roadmap proposes implementing a `C` target, require an actionable construction contract before treating the plan as implementation-ready:** define the function's external/operational disturbance, proposed first-party entry point and durable state, inputs/options, who would own the decisive decision when an autonomous actor is composed, enforcement and return-to-operation feedback, distribution/mode reachability, native baseline and overlapping original work, plus positive and unauthorized/missing-closure acceptance tests. A notification, ordinary callback or optional generic plugin is not an independently justified `C`. Clearly label proposed interfaces rather than asserting they already exist. Optional `C(P)` and `A(P)` are separate two-mode capabilities only for S3/S4/S5, under the published Methodology, not a universal grade ladder; `P` alone may be the legitimate final choice. S1/S2/S3* do not publish parent-mode notation. Never imply a stage or future PR changes the Index score or transfers rights to an agent.
4. **C sufficiency first; useful composability before autonomy.** Use the `P0/P1/P2` research priority above. For each qualifying function lacking confirmed `C` or `A`, either produce a **complete, source-native constructor/acceptance contract** explaining the minimal *combined* set of shipped primitives, reusable original Issues/PRs and additional proposed work sufficient for `C`, or name why no such path can be responsibly proposed. The contract must establish a real actor counterfactual, specific operational/external disturbance, first-party function-specific decision/feedback port (not generic hooks), independently developer-composable autonomous actor and legitimate authority, state/options lifecycle, enforcement, return into subsequent operation, supported boundary reachability, positive and unauthorized/missing-closure/compatibility native acceptance tests. No existing Issue/open PR or future plan itself certifies shipped `C`; only a subsequent Index-owned review can classify actually shipped source. `C(P)` and `A(P)` are separately supported optional modes only for S3/S4/S5, not a mandatory progression. `P` alone can remain appropriate; S1/S2/S3* have no published parent notation. A simpler project-native solution or `NO_USEFUL_CHANGE` is preferable to a fake C controller.
5. **Offer three independent choices.** (a) Integration/limited source-native PRs that respect existing work; (b) feedback/PRs to normative [Profile](https://github.com/opensiro/vsm-harness-profile) or separate [Skills](https://github.com/opensiro/vsm-harness-skills) assessment method; (c) legally permitted domain-specific fork experiment with an explicit task/boundary, simple native alternative and no expectation of original-project adoption. None is obligatory for maintainers.
6. **Test the cost hypothesis.** Predeclare comparable native-vs-VSM-informed tasks, functionality and all-in implementation/integration/review/test/maintenance costs. Until independently measured, mark cost claims `NOT_MEASURED`, never "proven cheaper".
7. **Stop at a decision-ready draft.** Produce the [Capability Roadmap Receipt](docs/CAPABILITY_ROADMAP.md#capability-roadmap-receipt) and optionally an original-native external issue draft marked `DRAFT — NOT PUBLISHED`. Do **not** open an Upstream issue, fork-local *contribution* record, schedule, or second mutable ledger solely for an unimplemented roadmap. When durable case storage is requested, use only the verified fork's `.opensiro/issues/<case-id>/`; a public fork GitHub Issue remains a separate approved publication. For an actual implementation, re-enter the existing full `upstream upgrade` material-delta, native validation, schema-v2 fork-local contribution and five-link handoff rules. External original issue/comment/PR and public fork-local PR still each need separate **exact current-conversation owner approval** of destination, action, full text and diff.
Expand Down
Loading
Loading