From 81556669530d4883ea9c02abd4b463fcea0f7522 Mon Sep 17 00:00:00 2001 From: alexruidan <41616537+xLagerFeuer@users.noreply.github.com> Date: Tue, 17 Nov 2026 22:46:03 +0300 Subject: [PATCH 1/3] fix(protocol): carry explicit roadmap C implementation through qualified Upgrade and fork-local review gate --- PROTOCOL.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/PROTOCOL.md b/PROTOCOL.md index d9bbb0d..d089402 100644 --- a/PROTOCOL.md +++ b/PROTOCOL.md @@ -34,7 +34,23 @@ Read [docs/FORK_METADATA.md](docs/FORK_METADATA.md) for the initial JSON contrac 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 improvement record, schedule, or second mutable ledger solely for an unimplemented roadmap. 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. -**Boundary:** roadmap success is a source-linked integration proposal, not delivery of code, confirmed `C`, formal Index reassessment, Profile amendment, implemented autonomy or measured cost savings. `upstream upgrade` and `upstream upgrade batch N` / `upstream batch [N]` remain unchanged. +**Boundary:** roadmap success is a source-linked integration proposal, not delivery of code, confirmed `C`, formal Index reassessment, Profile amendment, implemented autonomy or measured cost savings. **Subsequent explicit implementation requests activate the bounded full-cycle Upgrade handoff below; they are not discharged by the original `PLAN_ONLY` result.** `upstream upgrade` and `upstream upgrade batch N` / `upstream batch [N]` retain their other gates and semantics. + +### Roadmap → implementation handoff (explicit execution intent) + +**Intent is binding, not the last artifact label.** A plain `upstream roadmap OWNER/REPO` request remains `PLAN_ONLY`. However, when the owner then says **"implement this roadmap/contract", "bring this C target to a fork-local PR", "продолжи до local PR"**, or otherwise explicitly requests product implementation, do **not** treat the prior `PLAN_ONLY` receipt as a stop instruction. Re-enter the existing **single-original `upstream upgrade OWNER/REPO`** engineering route; the named original stays locked and no new research batch, Profile update or automatic Index grade is authorized. A request to **edit the protocol only** is not an implementation mandate. + +**Mandatory implementation handoff for a qualified `C` target:** + +1. **Verify current inputs anew:** exact original default SHA and current issue/PR/feature overlap; latest accepted Index evidence (historical grades only), approved implementation contract and native alternative; original contribution/licensing/AI policies; matching fork parent, current default SHA and `opensiro/meta` `ALLOW/PAUSE/STOP` controls. Reconcile earlier proposal with *today's* source; do not blindly implement speculative interfaces. +2. **Pass the existing functional-delta gate:** identify a product-native task the proposed first-party constructor will materially enable versus shipped behavior, with a specific S-function disturbance/decisive owner/return witness. Do not implement solely to increase `C` coverage; if the gap is gone, record `NO_MATERIAL_DELTA` and stop coding. +3. **Implement the smallest full first-party vertical slice:** named source event → real selectable options → function-specific agent-composable decisive right → policy/authorization enforcement → observable change in later operation/feedback. Implement the approved `C` contract in the **matched authorized fork's product feature branch**, not in the Upstream docs or on `opensiro/meta`. A demo-only module, README or optional uninstalled generic plugin is not delivery. +4. **Prove it with native tests:** run the source-native suite and the contract's matched positive, negative, unauthorized, stale-input, mode/owner and feedback acceptance cases, or explicitly report which could not run. Pin implementation commit and preserve exact output and any source-native limitations. No synthetic `C` grade; only a later Index-owned reassessment can classify actually shipped source. +5. **Persist an independently real contribution:** an evidence-linked schema-v2 `.opensiro/contributions/.json` on `opensiro/meta` and append-only attributed event when justified; check provenance chronology for `ASSESSMENT_DERIVED` versus `ASSESSMENT_INFORMED`. Never put `.opensiro/` metadata in a product PR. +6. **Reach the fork-local review gate:** prepare an exact, source-template-compliant PR title/body and changed-file diff from the feature branch to the *same fork's* default branch. Verify branch/head/commit, tests, forks and no duplicate live review PR. Under the existing **separate exact-publication-consent gate**, request consent to publish the **public fork-local PR** after showing exact destination/action/text/diff; publish and read it back **only when consent is granted**. If not granted, stop at `READY_FOR_FORK_LOCAL_PR_APPROVAL — NOT PUBLISHED`, with branch and complete handoff rather than claiming PR creation. +7. **Finish or explicitly fail closed:** success is an actual authorized fork-local review PR (when permitted) or a fully reproducible approval-ready feature branch when public publication is not permitted. Missing permissions, native closure, tests, consent or first-party support are individually named blockers—not `PLAN_ONLY complete`. External original PR/issue/comment requires **another** separate exact approval. Never merge the fork-local or third-party PR merely because this route was invoked. + +**Continuity rule:** once an operator explicitly asks to implement a completed roadmap contract, continue this route within the requested task; do not stop after rewriting the specification or redirect the user to start `upstream upgrade` manually. A roadmap document alone never creates an implementation obligation or third-party publication permission. ## Capability-first `upstream upgrade` (new work, not historical batching) From 316a16ec9527f6a96937f8d5d6f8f47f54471409 Mon Sep 17 00:00:00 2001 From: alexruidan <41616537+xLagerFeuer@users.noreply.github.com> Date: Tue, 17 Nov 2026 22:46:21 +0300 Subject: [PATCH 2/3] docs(roadmap): distinguish plan-only from separately authorized implementation follow-up --- docs/CAPABILITY_ROADMAP.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/CAPABILITY_ROADMAP.md b/docs/CAPABILITY_ROADMAP.md index 3f1ff21..d6ce824 100644 --- a/docs/CAPABILITY_ROADMAP.md +++ b/docs/CAPABILITY_ROADMAP.md @@ -19,6 +19,14 @@ The normative [Profile](https://github.com/opensiro/vsm-harness-profile/blob/mai 6. **Matched cost experiment:** Predeclare equivalent native vs VSM-informed user tasks and measure total implementation, integration, review/test, maintenance/regression effort and output quality. Report `NOT_MEASURED` until data exist. Never claim proven cheaper or performance superiority from a diagram. 7. **Handoff:** Produce [Capability Roadmap Receipt](#capability-roadmap-receipt) and optional [external architecture issue](../templates/EXTERNAL_ARCHITECTURE_ISSUE.md) with exact source links; keep `DRAFT — NOT PUBLISHED` until separate current owner consent for the exact destination/full text/diff. Plan-only ends even with zero code, zero PR, or no qualified improvement. +## Explicit implementation follow-up (not part of PLAN_ONLY) + +A bare `upstream roadmap OWNER/REPO` request stops at a source-linked proposal without product edits. When the owner **separately requests implementation of this roadmap/constructor contract, including a fork-local review PR**, it activates the already-defined [full-cycle Upgrade handoff](../PROTOCOL.md#roadmap--implementation-handoff-explicit-execution-intent) for that **same original**. The previous roadmap's `PLAN_ONLY` label describes the *past stage*, not a veto on new implementation intent. + +A qualified `C` constructor is **not delivered** by the contract, code sample, fake completion tests or a generic plugin extension. Carry the smallest first-party path from disturbance and proposed options through real developer-composed decision owner, enforced authority, next-operation application and observation. Test the original-native capability delta and contract acceptance cases. Stage implementation/test code on the verified `opensiro-contributions` fork's product branch; keep schema-v2 evidence on `opensiro/meta` only. Prepare original-template PR diff and five-link handoff. A public fork-local PR itself still needs **separate exact current-conversation approval of its destination, action, full title/body and diff**; no blanket authorization is inferred from "implement". If that gate remains unapproved, report the tested branch plus `READY_FOR_FORK_LOCAL_PR_APPROVAL — NOT PUBLISHED` rather than falsely marking a PR complete. No external original publication or grade upgrade follows automatically. + +If the native delta or a true S4/S3/etc decision/closure witness is not established, say `NO_MATERIAL_DELTA` or `IMPLEMENTATION_BLOCKED` with source-backed reasons, and do not add a fake first-party controller to fill a grade. + ## Capability Roadmap Receipt A compact, **read-only Markdown report** in chat, or a dated **non-authoritative example**. Do not create another issue/PR queue or a fork-local contribution ID just for a proposal. Required evidence sections: From f07bb5f5f1d5131d52063c2f1823605a8d44be2c Mon Sep 17 00:00:00 2001 From: alexruidan <41616537+xLagerFeuer@users.noreply.github.com> Date: Tue, 17 Nov 2026 22:47:24 +0300 Subject: [PATCH 3/3] docs(changelog): record roadmap-to-Upgrade continuation gate as unreleased --- CHANGELOG.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index bb2f1cc..74d014d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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 +**Roadmap-to-Upgrade execution continuity (unreleased):** Keep `upstream roadmap` strictly plan-only when that is the owner's request, but route a subsequent explicit instruction to implement the accepted `C` constructor through the existing single-original full-cycle Upgrade. Require verified source/overlap and capability delta, actual first-party vertical-slice code and native positive/negative tests, a verified fork product branch plus schema-v2 meta evidence, and exact draft fork-local PR handoff. The existing separate public fork-local and external-publication consent gates are unchanged; no automatic PR, Index grade, protocol version bump or Release. + **Roadmap C-target construction/acceptance contract (unreleased):** Require a function-specific first-party constructor interface, independently composable agent decision ownership, authorized return to subsequent operation, boundary reachability and native positive/negative acceptance cases before describing a roadmap target `C` as implementable. Add a Paperclip S4=C proposal with ten falsifiable test scenarios, tied to the accepted November Index reassessment; no first-party Paperclip code, external publication, automatic grade change, SemVer bump or Release. **Roadmap assessment-freshness advisory (unreleased):** If the most recent successful Index semantic review/check is more than 30 calendar days old, recommend an Index-owned source-pinned re-assessment before confident architecture-gap claims. Material product change can trigger an earlier recommendation. Preserve the old accepted vector until Index admission; allow explicitly provisional read-only roadmaps while the re-assessment is pending. No automatic regrade, periodic Index mandate, new assessment controller, third-party publication, SemVer bump or Release.