From f1cdb9d226153e9ea7b721057944495d17d76940 Mon Sep 17 00:00:00 2001 From: alexruidan <41616537+xLagerFeuer@users.noreply.github.com> Date: Tue, 17 Nov 2026 21:53:48 +0300 Subject: [PATCH 1/6] docs(roadmap): specify testable Paperclip S4 constructor acceptance contract --- ...clip-s4-constructor-acceptance-20261117.md | 75 +++++++++++++++++++ 1 file changed, 75 insertions(+) create mode 100644 docs/examples/paperclip-s4-constructor-acceptance-20261117.md diff --git a/docs/examples/paperclip-s4-constructor-acceptance-20261117.md b/docs/examples/paperclip-s4-constructor-acceptance-20261117.md new file mode 100644 index 0000000..4559ecf --- /dev/null +++ b/docs/examples/paperclip-s4-constructor-acceptance-20261117.md @@ -0,0 +1,75 @@ +# Paperclip S4=C — proposed construction and acceptance contract + +**Status:** `PLAN_ONLY / DESIGN CANDIDATE`, observed 2026-11-17. **No Paperclip implementation exists in this document.** This is a reproducible engineering *target* for a possible first-party S4-specific constructor, **not a new Index score, a proven missing user demand or permission to publish an external issue/PR**. It is subordinate to [the Paperclip roadmap](paperclip-roadmap-20261117.md) and the current [Skills Methodology 0.3.8](https://github.com/opensiro/vsm-harness-skills/blob/main/skills/assess-vsm-harness/references/autonomy-states.md). + +## 1. System, evidence and counterfactual + +- **System in focus:** one Paperclip company with supported first-party agent execution, company configuration, real task/run lifecycle, CEO/management (S3), human board ultimate policy (S5) and independently scoped review (S3*). An uninstalled plugin, provider agent, private Cloud router or the Paperclip OSS maintainer organization does not supply ownership by default. +- **Accepted Index baseline:** [Paperclip canonical reassessment](https://github.com/opensiro/vsm-harness-index/blob/975a58814b767cfca414c152480f787bfe80944b/assessments/pa/paperclip.md), source `7f9867895c4e7e9589b233a93aa9efceb0c992d0`, `S4=—`. The separately observed original `master` at roadmap time was `904c01d1a3a16de817792432d5d5a24f6e4bde12`; do not silently credit those unassessed commits. +- **Native issue / strongest overlap:** [#20848 — model-release notifications and compatibility-aware upgrade recommendations](https://github.com/paperclipai/paperclip/issues/20848), observed OPEN. Compare current catalog work [#16658](https://github.com/paperclipai/paperclip/issues/16658), protected settings [#10125](https://github.com/paperclipai/paperclip/issues/10125) and any later merged equivalent before proposing new code. +- **Existing first-party boundaries:** [CEO heartbeat](https://github.com/paperclipai/paperclip/blob/7f9867895c4e7e9589b233a93aa9efceb0c992d0/server/src/onboarding-assets/ceo/HEARTBEAT.md), [company core concepts](https://github.com/paperclipai/paperclip/blob/7f9867895c4e7e9589b233a93aa9efceb0c992d0/docs/start/core-concepts.md), [approval routes](https://github.com/paperclipai/paperclip/blob/7f9867895c4e7e9589b233a93aa9efceb0c992d0/server/src/routes/approvals.ts), [AI connection router host](https://github.com/paperclipai/paperclip/blob/7f9867895c4e7e9589b233a93aa9efceb0c992d0/server/src/services/ai-connection-router.ts). [Experimental router contract](https://github.com/paperclipai/paperclip/blob/7f9867895c4e7e9589b233a93aa9efceb0c992d0/doc/connections/AI-CONNECTION-ROUTERS.md) is default-off and delegates policy to a plugin; generic model/account routing does **not** already establish S4. +- **User-level unmet task to verify:** a company operator wants to consider an *external future change* (new/retired model + changed execution-compatibility/price), compare future operating options, delegate bounded analysis to an agent, and know that an accepted recommendation actually changed the next eligible operating run without affecting unapproved current tasks. **This is an engineering hypothesis until supported by native user evidence.** +- **Simplest existing alternative:** operator checks official release notes, inspects actual agent/adapter versions and eligible accounts, manually edits a compatible model setting and checks the next run. If this is sufficient, choose `NO_USEFUL_CHANGE` rather than adding a framework. + +## 2. Functional witness required for a positive S4 constructor + +A proposed `S4=C` mapping requires **all** of the following first-party reachable capabilities, not merely a code module named “adaptation”: + +| Link in loop | Proposed required output | Owner / negative control | +| --- | --- | --- | +| External and prospective observation | A dated, source-attributed model availability/deprecation/capability signal relevant to an actually configured company agent | Polling/storage are deterministic; release-note ingestion alone is not S4 | +| Model present vs possible future | At least **hold** and **candidate change** options, grounded in a snapshot of current agent configuration, adapter/client compatibility, eligible account, budget, reviewer role and predicted future-run impact; unknowns explicit | Internal task scheduling or a new-model notification alone is not prospective option formation | +| Decisive S4 decision/feedback constructor | A **function-specific first-party decision port** by which a developer can compose a real autonomous evaluator/agent and bind a bounded organization-level option-selection right | The composed actor owns choosing between options; generic event hooks or a human-only button do not establish autonomous `C` | +| Authorized selection | Persisted option choice (including reject/defer/hold), decision principal, policy/approval evidence, concurrency generation and reason | An evaluator cannot mint S5 authority; board/parent retains reserved policy approval | +| Return to S3/present capability | Controlled **future-run-only** configuration stage/commit, or another concrete first-party company-capability revision, with actual effective-state/next-run receipt and failure feedback | A recommendation in a dashboard, an unexecuted ticket, or a test mock with no first-party return path is not closure | + +**Owner counterfactual:** with a configured evaluator removed, the first-party interface still exposes a meaningful S4-specific choose/authorize/return path, but it cannot independently exercise autonomous option-selection judgment. With the developer-composed agent connected, its different decisions must lead to different authorized later company states through that same path. If the core itself selects and closes the function autonomously, examine `A`; if only a legitimate human parent closes a function-specific loop and no autonomous constructor is supported, examine `P`. A separate closed parent S4 mode might justify `C(P)`, **never** simply because a board can approve an ordinary configuration edit. + +## 3. Proposed minimal first-party ports (names illustrative, NOT existing endpoints) + +A *thin* slice may implement the following contracts using current Paperclip type/authorization/concurrency conventions; these logical names are proposals, not assertions about current routes, files or stable APIs. + +1. **`ReleaseSignalSource`**: import a verified provider release/change record with `companyId`, `provider`, `currentModelId`, `candidateModelId`, `sourceUrl`, `sourceObservedAt`, `effectiveAt`, `sourceDigest` and `idempotencyKey`. A test fixture or operator-imported official manifest is enough for the first slice; a live poller may be optional. Store provenance, never treat an unverified provider listing as account entitlement. +2. **`S4AdaptationCaseStore`**: persist `caseId`, source event revision, affected company/agent IDs, current configuration revisions, an environment snapshot, predicted differences, *at least hold and test/stage alternatives*, capability/price evidence, known/unknown/blocked compatibility and expiry. Distinguish `observation` → `options-ready` → `decision-pending` → `accepted/rejected/stale`; cap fanout/deduplicate by source/model/company. +3. **`S4DecisionPort`**: expose an explicit, company-scoped `evaluateAdaptationCase(caseId, snapshot)` / `submitAdaptationDecision(caseId, choice, actor, expectedVersion, reason)` path **for a configured autonomous agent actor**. The developer composes its model/authority within the existing Paperclip agent/harness contract. The core validates principal, delegated decision scope, idempotency and version but does **not** fabricate the substantive S4 option choice. +4. **`FutureRunCapabilityBridge`**: accept only an authorized **staged future-use** change after compatibility, reserved board approvals and concurrency checks. It must not silently rewrite an active run, agent's unrelated configuration, independent reviewer binding, credentials, shared access or budgets. Capture before/after configuration revision; reject stale proposals and revoked rights. A safe manual approval may be a gating policy, but is not evidence of an autonomous `C` owner. +5. **`S3ReturnAndObservation`**: attach an immutable decision→staged-revision→next-eligible-run reference. Confirm which model/config was *actually resolved* for that run, feed success/denial/fallback to the current company/CEO management view, and let the authorized owner hold/revise/revert a future-use choice. “Queued change” alone is not sufficient feedback. + +**Implementation boundary:** a generic MCP connection, webhook, task list, arbitrary callback registration, model catalog or `Ask first` permission is only supporting machinery. To count toward `C`, the *shipped first-party distribution* must expose an intentionally S4-specific constructor path and an example showing a developer-composed agent actually selecting a future-oriented adaptation option and receiving closure into later company operation. It may be opt-in, but its relevant host/bridge pieces must be real and reachable without proprietary unseen services. + +## 4. Ordered acceptance scenarios / release gates + +Each case is deterministic, runs against a **pinned Paperclip source revision**, includes a before/after expected state and records a native test or reproducible runner trace. A mock provider release catalog, test company and non-secret compatible adapter fixture may replace live paid model accounts. + +| ID | Input / decision | Required observable result | +| --- | --- | --- | +| `AC-01` External change | Official-model fixture announces a new successor used by an agent | One provenance-pinned case, source/time/affected agents, **hold** and **candidate** alternatives; stable dedup on repeated polling | +| `AC-02` Future/current coupling | Model option available but installed CLI version or account eligibility is unknown/incompatible | Case marks **unknown/blocked**; cannot claim ready-to-apply or execute the option | +| `AC-03` Actual constructor | Connect one real first-party company agent to the S4-specific decision port; feed same case under two controlled future scenarios | Agent-owned choice changes option receipt (hold vs stage); actor/principal, scope and reason are attributed; external decision logic remains developer-composable | +| `AC-04` Return into present capability | Authorized choice selects compatible candidate after required approval | Version-guarded future-use configuration change is staged; next **eligible** agent run uses expected resolution and returns a linked observation receipt; current run stays pinned | +| `AC-05` S5 reserved rights | Agent has S4 option-selection rights but not ultimate company policy or model-change approval rights | Without required approval, result stays pending/denied; no silent S5 transfer, new credential, grant, purchase or budget expansion | +| `AC-06` Wrong actor | Other company/agent/user attempts to submit or apply a case | Cross-company and unauthorized decisions fail closed; no state mutation and no leaked model/account data | +| `AC-07` Concurrency and revocation | Submitted against outdated agent config, removed account, expired signal or revoked delegated rights | Conflicting case rejects with reason; no change to protected config, reviewer selection or active sessions | +| `AC-08` Refusal/deferral | Configured actor chooses hold or authorized board rejects | Durable reason and suppression/snooze rule; no future-run change and no duplicate notifications for the same source revision | +| `AC-09` Negative S4 witness | Only notification, release notes, eval memory, plain job queue or human button is active | Test confirms **no autonomous constructor claim** from these components alone; labels stay `support/possible P`, never asserted `C` | +| `AC-10` Failure feedback | A staged model becomes unavailable at the next run or a canary fails | Failure is surfaced to S3/owner, with bounded stop/revert where provided; no silent repeated upgrade or lost decision provenance | + +**Native quality gates:** no credentials in fixtures; all new permissions map to existing role/company boundaries; source-verified compatibility checks; no control-plane bypass; robust idempotency/cancellation; audit with source and actor; unchanged ordinary agent/review/approval behavior. The first slice can defer sophisticated canary dashboards, ML ranking or many-provider polling, **not** the function-specific ownership/feedback path. + +## 5. Engineering sequence and evidence for Index re-review + +- **P0 — demand and dedup:** compare the full current first-party mode, issue #20848 and any competing implementation diff; show a current user task that manual settings cannot handle sufficiently well. If no credible user value, end `NO_USEFUL_CHANGE`. +- **P1 — smallest usable vertical slice:** import a trusted single-provider signal → persist two options and compatibility state → configure one first-party autonomous evaluator via S4 decision port → authorized future-use config stage → next-run actual-state receipt/feedback. Implement as a supported optional feature if that fits the original product better than a global controller. Tests `AC-01` through `AC-09` (plus safety aspects of `AC-10`) are mandatory for a `C` target. “Notification only” may be useful as a **product** contribution but cannot be described as a completed `C` constructor. +- **P2 — optional enhancement after demand:** live provider polling, better diff/cost projections, canary and rollback UX, multiple adapter backends, proactive retirement support; measure costs and avoid duplicate control surfaces. +- **Publication:** any actual product code requires the existing `upstream upgrade` functional-delta, native-test, verified fork, license/contributor/AI disclosure, fork-local review and separate external-publication gates. Plan-only has no permission to open a Paperclip issue/comment/PR or a public fork-local PR. +- **Reassessment gate:** only after code really ships at a newly pinned source ref, an **Index-owned fresh source-first review** may decide whether `S4=C` (or another state) is supported. The engineering tests prove a product feature; they are **not** an automatic grade or independent S4 semantic proof. +- **Cost hypothesis:** compare matched operator-run migration task against manual-native workflow with implementation/integration/testing, maintenance effort, actual future-run success, error and rollback safety. **Cost status: NOT_MEASURED**. + +## 6. Decisions still open + +- Is this desired as a first-party optional company feature or a plugin with a **genuinely first-party S4-specific host bridge**? A generic uninstalled plugin cannot independently establish `C`. +- What source is authoritative for model availability **and** actual adapter/account eligibility, and who may authorize each company-level configuration class? +- Is an autonomous evaluator a realistic product user need, or is board-only review sufficient (`P` candidate, not automatically `C`)? This must be resolved by source-native operator evidence rather than a target grade. +- Which single future-use setting can be changed safely without altering reviewer independence, current sessions, provider account access or budget policy? + +**Stop condition:** if any essential `C` witness (externally prospective input, structured options, developer-composable decisive actor, authorized first-party return or observed later-use feedback) cannot be made source-native and testable, record the unresolved condition and choose `NEEDS_EVIDENCE` or a smaller feature rather than calling a notification feature `S4=C`. From 727221cbababe9d84a1590fbab03910f47a85f0d Mon Sep 17 00:00:00 2001 From: alexruidan <41616537+xLagerFeuer@users.noreply.github.com> Date: Tue, 17 Nov 2026 21:54:23 +0300 Subject: [PATCH 2/6] docs(roadmap): bind Paperclip C target to implementation and acceptance conditions --- docs/examples/paperclip-roadmap-20261117.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/examples/paperclip-roadmap-20261117.md b/docs/examples/paperclip-roadmap-20261117.md index 08972bf..3f0c9cd 100644 --- a/docs/examples/paperclip-roadmap-20261117.md +++ b/docs/examples/paperclip-roadmap-20261117.md @@ -56,6 +56,13 @@ **P2 — integration guardrails only.** Any new S3/S4 constructor must respect existing S2 single-owner/blocker semantics, S3* independent review and board S5 reserved decisions; do not require six additional subsystems or force `C → C(P) → A(P)`. The optional parent variants require independent first-party closure and separate Index review after shipping. +### P0 proposed S4 constructor — implementation-ready acceptance conditions + +The specific **proposed first-party S4 constructor** is now written as a separate, reviewable [Paperclip S4=C construction and acceptance contract](paperclip-s4-constructor-acceptance-20261117.md). It is a **hypothesis and engineering target**, not a shipped feature or a changed Index grade. The contract pins the accepted evidence, explicit S4 decision/feedback owner, a five-port minimum design and ten falsifiable acceptance scenarios (`AC-01`–`AC-10`). + +**Required minimum before calling a future implementation a candidate `C`:** a source-attributed external/future model-change signal → durable comparison of `hold` versus `candidate` against actual current S3 capability → first-party **S4-specific** decision port into which a developer can compose an autonomous evaluator/agent with bounded authority → authorized **future-run-only** configuration/capability revision → receipt from subsequent actual agent operation returning success or denial into S3. Include a working actor-composition example, unauthorized/unknown-compatibility/rollback negative tests, first-party reachability and existing-simpler-native comparison. A release notification, model catalog, optional generic plugin hook or human-only approval **fails** the autonomous constructor witness. + +**Grade gate:** `C` requires subsequent first-party shipping and an independent source-pinned Index assessment under Skills; `P` remains a valid human-only S4 possibility if separately established. `C(P)` requires two independent mode witnesses and is not the target by default. Existing `S4=—` remains canonical. **Preimplementation test of materiality:** for each candidate, state actor, exact currently impossible/awkward task, best native workaround, measurable output, right owner, enforcement, trace of decision to later execution, and overlap. If a shipped path already closes the task, report `NO_USEFUL_CHANGE` for that idea. ## Implementation options From c6dbf60dce04d8c064cbdc1cd3f9d7cc51aa59e1 Mon Sep 17 00:00:00 2001 From: alexruidan <41616537+xLagerFeuer@users.noreply.github.com> Date: Tue, 17 Nov 2026 21:54:42 +0300 Subject: [PATCH 3/6] docs(protocol): require an implementable first-party C constructor contract --- docs/CAPABILITY_ROADMAP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/CAPABILITY_ROADMAP.md b/docs/CAPABILITY_ROADMAP.md index 1a8438d..9fd8bca 100644 --- a/docs/CAPABILITY_ROADMAP.md +++ b/docs/CAPABILITY_ROADMAP.md @@ -14,7 +14,7 @@ The normative [Profile](https://github.com/opensiro/vsm-harness-profile/blob/mai - **Assessment freshness advisory:** Compute age in calendar days at the observation date from the latest accepted successful Index semantic review (`reviewed_at`, or a later successfully supported `last_checked_at`; do not credit informal source inspection). If older than **30 days**, **recommend an Index-owned, source-pinned re-assessment before relying on the historical vector for architectural conclusions**. Materially changed current behavior can justify the recommendation sooner. Cite the exact canonical assessment, date, current source HEAD and any live reassessment issue/PR. This recommendation is **not** a periodic reassessment mandate, universal Index policy, automated queue write, grade change or roadmap block. If re-assessment is pending or not feasible, continue **plan-only with provisional claims**, old assessment explicitly historical, and source-native evidence controlling current functionality. An open or unmerged proposal is not accepted freshness. 2. **Native work census:** For relevant S1/S2/S3/S3*/S4/S5, inspect current shipped code; exact original issue and PR state/head/diff and maintainer decision; existing OpenSiro fork work; competing original alternatives. Distinguish `SHIPPED`, `OPEN_PR`, `ISSUE_ONLY`, `EXPERIMENT`, `EXTERNAL_GOVERNANCE` and `UNVERIFIED` as *report labels only*, not stored metadata enums. 3. **Function-specific residual gap:** Name real actor → trigger → decision/action → observable result; actual disturbance; decisive right and owner; enforcement/transport; feedback into subsequent operation. Write `current main → competing proposal → remaining task`, overlap/alternative, uncertainty. No conclusion from a low Index grade or an issue title alone. -4. **Composability-first option:** Favor supported first-party, function-specific constructors where maintainers need them; only a shipped/composable closure can establish `C` in a later Index assessment. `C(P)` and `A(P)` are optional, independently demonstrated modes **only for S3/S4/S5**, not a mandated grade progression. `P` alone is a valid intentional goal; S1/S2/S3* have no published parent mode. Always prefer a simpler native design when appropriate. +4. **Composability-first option:** Favor supported first-party, function-specific constructors where maintainers need them; only a shipped/composable closure can establish `C` in a later Index assessment. A `C` **implementation target** must carry a source-native constructor/acceptance contract: precise user counterfactual, environmental/operational stimulus, function-specific first-party decision/feedback port (not generic hooks), an explicitly composable autonomous decision actor and authority boundary, proposed option/state lifecycle, closure into subsequent operation, exact tests including rejection/absence and compatibility, and proof of distribution reachability. Without those details call the case `NEEDS_EVIDENCE`, not an implementation-ready `C` roadmap. `C(P)` and `A(P)` are optional, independently demonstrated modes **only for S3/S4/S5**, not a mandated grade progression. `P` alone is a valid intentional goal; S1/S2/S3* have no published parent mode. Always prefer a simpler native design when appropriate. 5. **Independent maintainer choices:** (a) original-native code/PR work, with existing Upgrade gates and separate independent contribution record per real improvement; (b) normative semantic feedback to Profile or separate Skills method/assessment improvement; (c) permitted experimental domain fork with declared boundary. Neither a spec issue nor a fork creates original maintainer obligations. 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. From 320a57a8b6888c6c4880c87f40120102bb8fb7f3 Mon Sep 17 00:00:00 2001 From: alexruidan <41616537+xLagerFeuer@users.noreply.github.com> Date: Tue, 17 Nov 2026 21:54:44 +0300 Subject: [PATCH 4/6] docs(protocol): require an implementable first-party C constructor contract --- PROTOCOL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/PROTOCOL.md b/PROTOCOL.md index cc812e2..d9bbb0d 100644 --- a/PROTOCOL.md +++ b/PROTOCOL.md @@ -29,7 +29,7 @@ Read [docs/FORK_METADATA.md](docs/FORK_METADATA.md) for the initial JSON contrac 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. 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. **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. 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 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. From e606ef820973f0f22bac7e632f2204ef36472a68 Mon Sep 17 00:00:00 2001 From: alexruidan <41616537+xLagerFeuer@users.noreply.github.com> Date: Tue, 17 Nov 2026 21:56:27 +0300 Subject: [PATCH 5/6] docs(roadmap): require acceptance contract in C-target receipts --- docs/CAPABILITY_ROADMAP.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/CAPABILITY_ROADMAP.md b/docs/CAPABILITY_ROADMAP.md index 9fd8bca..3f1ff21 100644 --- a/docs/CAPABILITY_ROADMAP.md +++ b/docs/CAPABILITY_ROADMAP.md @@ -30,12 +30,15 @@ A compact, **read-only Markdown report** in chat, or a dated **non-authoritative | Existing work | Original and fork issue/PR URLs, true open/merged status and head/diff evidence, shipped/proposed distinction | | VSM witness | Function, disturbance, real decision/feedback owner/right, enabling first-party primitives and return-to-operation | | Proposed capability | Actor/output and native alternative, meaningful constructor path, dependencies and small acceptance cases | +| Constructor target (when proposing `C`) | Function-specific first-party ports and distribution reachability; what a developer must compose (real autonomous decision actor/authority), option/state lifecycle, controlled return into future operation, negative cases and reproducible end-to-end acceptance. Explicitly distinguish proposed from shipped `C`. | | Optional paths | Product-native code, Profile or Skills feedback, permitted domain-specific fork | | Cost check | Paired native/VSM-informed task, all-in measures and observed values, else `NOT_MEASURED` | | Delivery | `PLAN_ONLY`, `NEEDS_EVIDENCE` or `NO_USEFUL_CHANGE` as narrative outcomes only; external issue marked `DRAFT — NOT PUBLISHED` | **Fail closed:** unknown source/ref/owner/diff or assessment freshness stays unverified. A >30-day historical assessment prompts a recommended re-review, not a hard stop, automatic Index write, or silent promotion of a pending reassessment. An Issue or open PR does not certify shipped capability, a planned `C` is not an Index `C`, and a maintained project policy is not automatic runtime S5. +For an implementation-oriented `C` target, see the [Paperclip S4=C proposed construction and acceptance contract](examples/paperclip-s4-constructor-acceptance-20261117.md) for a concrete (still plan-only) first-party interface/ownership/feedback design and falsifiable test matrix. The example demonstrates required specificity, not a changed Index grade or a mandatory VSM architecture. + ## Optional structural receipt check The source-native receipt stays **read-only documentation**, not a fork-local JSON state or an Index assessment. For a dated Markdown case note, run: From c6a00d9bfea1d87674630400d7ec98c8a9190734 Mon Sep 17 00:00:00 2001 From: alexruidan <41616537+xLagerFeuer@users.noreply.github.com> Date: Tue, 17 Nov 2026 21:57:48 +0300 Subject: [PATCH 6/6] docs(changelog): record C-target roadmap contract as unreleased --- CHANGELOG.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 09061ee..bb2f1cc 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 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. **Architecture-first Upstream roadmap (unreleased):** Add a named-source, plan-only contribution route for mapping assessment, native issues/PRs and proposed composable capabilities, with independent options for product code, Profile/Skills feedback and domain-specific forks. VSM-standardization and development-cost benefit remain hypotheses; no automatic assessment regrade, agent autonomy, new fork metadata enum, third-party publication, SemVer bump or Release.