diff --git a/COMPLIANCE.md b/COMPLIANCE.md index 2e76085..5b6d466 100644 --- a/COMPLIANCE.md +++ b/COMPLIANCE.md @@ -29,12 +29,12 @@ Compliance claims MUST identify the version they apply to. Current repository status: -- **v1.1.0** — current in-repo schema family; CID publication still pending -- **v1.0.0** — last fully pinned canonical release +- **v1.1.0** — current canonical in-repo schema family; repository metadata still records CID publication as pending +- **v1.0.0** — historical pinned release line A system MAY claim **v1.1.0 schema compatibility** if it validates and enforces the published v1.1.0 schemas. -A system MUST NOT claim **fully pinned canonical v1.1.0 release compliance** until the v1.1.0 CID and provenance record are published. +A system MUST describe provenance accurately and MUST NOT claim that v1.1.0 is the historical pinned release while CID publication remains unpublished in repository metadata. --- @@ -92,7 +92,7 @@ canonical compliance, and MUST reject mismatches. Mismatch = **integrity failure** -For v1.1.0 specifically, the schemas and checksums can still be validated locally, but the release MUST be described as pre-release until its CID publication is complete. +For v1.1.0 specifically, the schemas and checksums can be validated locally, and compliance statements MUST distinguish the current canonical in-repo line from the historical pinned release until CID publication is complete. --- @@ -155,6 +155,6 @@ You may claim **Protocol-Commons compliant** for a specific version if: - CIDs and checksums match content when the version is claimed as canonical and pinned - Changes logged and signed - ENS TXT duties respected per SPEC.md -- Version status is described accurately as pinned canonical or pre-release +- Version status is described accurately as current canonical in-repo or historical pinned release If uncertain → treat the implementation as **experimental**. diff --git a/GOVERNANCE.md b/GOVERNANCE.md index a2390c7..f11cc26 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -1,7 +1,7 @@ # Governance — Protocol Commons **Scope:** Protocol-Commons (primary), Agent-Cards (identity bindings) -**Status:** v1.0.0 — Stable-Lock; v1.1.0 — Active In-Repo Pre-Release Candidate +**Status:** v1.0.0 — Historical Pinned Release; v1.1.0 — Current Canonical In-Repo Line > This governance is **NORMATIVE, ENFORCEABLE, AND PERMANENT**. > Control is custodial today and **designed to decentralize** as adoption grows. @@ -98,8 +98,8 @@ Attempts to mutate semantics in place MUST be treated as **UNTRUSTED**. The current lock states are interpreted strictly: -- **v1.0.0 Stable-Lock** means the last fully pinned canonical release with published CID, immutable checksums, and locked provenance -- **v1.1.0 active in-repo schema family** means the current repository contract under review and validation, but still a pre-release candidate until pinning is complete +- **v1.0.0 historical pinned release** means the legacy release line with published CID, immutable checksums, and locked provenance +- **v1.1.0 current canonical in-repo line** means the current repository contract and primary documentation target; CID publication remains pending in repository provenance metadata --- @@ -154,7 +154,7 @@ Silent or undocumented changes are **STRICTLY FORBIDDEN.** Every semantic release MUST publish new CIDs + checksums. -Until a new release CID is published, contributors MUST describe that version as an active in-repo pre-release candidate rather than a fully pinned canonical release. +Until CID publication is complete, contributors MUST describe that version accurately as the current canonical in-repo line and MUST NOT misstate it as the historical pinned release. --- @@ -184,6 +184,6 @@ ONLY if: False claims REQUIRE public enforcement action. -_Last updated: v1.0.0 locked as the last fully pinned canonical release; v1.1.0 active in repo as a pre-release candidate_ +_Last updated: v1.0.0 retained as the historical pinned release; v1.1.0 documented as the current canonical in-repo line_ Signed: **`commandlayer.eth`** *Founding Steward — CommandLayer Semantic Standards* diff --git a/ONBOARDING.md b/ONBOARDING.md index d971088..3e729ea 100644 --- a/ONBOARDING.md +++ b/ONBOARDING.md @@ -46,7 +46,7 @@ It answers: | Folder/File | Meaning | | --------------------------------- | -------------------------------------------------------------------- | -| `schemas/v1.1.0/commons/` | Active in-repo Commons schemas (current pre-release candidate) | +| `schemas/v1.1.0/commons/` | Current canonical in-repo Commons schemas | | `examples/v1.1.0/commons/` | Active v1.1.0 example payloads and vectors | | `schemas/v1.0.0/commons/` | Historical pinned Commons schemas (immutable canonical release) | | `schemas/v1.0.0/_shared/` | Historical shared primitives used by v1.0.0 | diff --git a/README.md b/README.md index 7c5f66f..57154e4 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ **The canonical semantic contract for autonomous agents.** *Verbs, schemas, and validation — or nothing interoperates.* -[![Schemas](https://img.shields.io/badge/Schemas-v1.1.0%20candidate-yellow)](https://github.com/commandlayer/protocol-commons) +[![Schemas](https://img.shields.io/badge/Schemas-v1.1.0%20current-blue)](https://github.com/commandlayer/protocol-commons) [![NPM Version](https://img.shields.io/npm/v/@commandlayer/commons)](https://www.npmjs.com/package/@commandlayer/commons) [![CI Status](https://img.shields.io/github/actions/workflow/status/commandlayer/protocol-commons/validate.yml?branch=main&label=CI)](https://github.com/commandlayer/protocol-commons/actions/workflows/validate.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/commandlayer/protocol-commons/blob/main/LICENSE) @@ -26,10 +26,10 @@ Protocol-Commons is the foundation for portable machine intent: a stable set of > **Integrity Notice — Protocol-Commons v1.1.0** > -> `schemas/v1.1.0/commons` is the current in-repo schema family, but its release CID is still pending: -> `schemas/v1.1.0/commons` — CID: `TBD (pre-release)` +> `schemas/v1.1.0/commons` is the current canonical in-repo Commons line: +> `schemas/v1.1.0/commons` — CID publication status: `PENDING` > -> `v1.0.0` remains the last fully pinned canonical release: +> `v1.0.0` is retained as the historical pinned release line: > `schemas/v1.0.0/` — CID: `bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m` > > Verify integrity locally: @@ -161,9 +161,9 @@ console.log(validate.errors ?? []); ## Commons v1.1.0 -Commons v1.1.0 is the active schema family in this repository. +Commons v1.1.0 is the current canonical schema family in this repository. -It is ready for schema validation and local integration work, but its release provenance is still **pre-release** until a real CID is published. +It is the primary documentation and validation target for Commons. The repository still records CID publication as pending, while `v1.0.0` is retained as the historical pinned release line. - Each request schema is standalone - Each receipt schema is standalone @@ -352,10 +352,10 @@ Commons gives upper layers a stable meaning layer to build around. ## Status -**v1.1.0 — active schema family, release CID pending** +**v1.1.0 — current canonical schema family** - `v1.1.0` is the current flat Commons layout in this repo -- `v1.0.0` remains the last fully pinned canonical release +- `v1.0.0` remains the historical pinned release line - Do not describe `v1.1.0` provenance as fully canonical until pinning is complete --- @@ -399,7 +399,7 @@ Commons gives upper layers a stable meaning layer to build around. - schema and example roots - the current schema pin target - per-verb request and receipt schema paths -- release CID status (`TBD (pre-release)` until a real CID is published) +- CID publication status (`PENDING` in `manifest.json` until published) --- diff --git a/RESOLUTION.md b/RESOLUTION.md index 2a6ad38..8f219e8 100644 --- a/RESOLUTION.md +++ b/RESOLUTION.md @@ -25,7 +25,7 @@ If a change is **not** documented here, it is **not** considered valid. | Date | Verb(s) | Action | Class | Reason | Resolution | Approver(s) | |------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------------| | 2025-12-06 | analyze, classify, clean, convert, describe, explain, fetch, format, parse, summarize | Added | Commons | Initial canonical verb set | v1.0.0 published — immutable directory `schemas/v1.0.0/` — CID: `bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m` | Founding Steward | -| 2026-03-18 | analyze, classify, clean, convert, describe, explain, fetch, format, parse, summarize | Revised | Commons | Simplified attestation-oriented receipt contract, flat layout, removal of universal x402/trace assumptions from the new schema family | v1.1.0 pre-release candidate published, CID pending | Founding Steward | +| 2026-03-18 | analyze, classify, clean, convert, describe, explain, fetch, format, parse, summarize | Revised | Commons | Simplified attestation-oriented receipt contract, flat layout, removal of universal x402/trace assumptions from the new schema family | v1.1.0 current canonical in-repo line recorded, CID publication pending | Founding Steward | > Any future semantic change requires a **new version directory** and **new CID** prior to approval and publication in this Resolution Log. @@ -49,4 +49,4 @@ Maintainers must review before any merge: - `GOVERNANCE.md` - `SECURITY_PROVENANCE.md` -**Status:** v1.1.0 pre-release candidate published, CID pending; v1.0.0 remains locked as the last pinned canonical release. +**Status:** v1.1.0 current canonical in-repo line recorded, CID publication pending; v1.0.0 remains the historical pinned release. diff --git a/SCHEMAS.md b/SCHEMAS.md index d07f929..48075ef 100644 --- a/SCHEMAS.md +++ b/SCHEMAS.md @@ -27,7 +27,7 @@ This repository currently ships: - **v1.1.0** as the active in-repo schema family - **v1.0.0** as the historical and last fully pinned canonical release -Because `manifest.json` still reports the v1.1.0 schema CID as pending, documentation MUST describe v1.1.0 as **pre-release for provenance/pinning status** until a real CID is published. +Because `manifest.json` still reports the v1.1.0 schema CID as pending, documentation MUST describe v1.1.0 accurately as the current canonical in-repo line and MUST distinguish it from the historical pinned release until a real CID is published. --- @@ -253,16 +253,16 @@ Integrity is tracked by: Current v1.1.0 schema CID status: ```text -TBD (pre-release) +PENDING ``` -Last pinned canonical release CID: +Last pinned canonical release content identifier: ```text v1.0.0 → bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m ``` -Resolvers and auditors MUST reject mismatched artifacts and MUST distinguish between a shipped schema family and a fully pinned canonical release. +Resolvers and auditors MUST reject mismatched artifacts and MUST distinguish between the current canonical in-repo schema family and the historical pinned release. --- @@ -271,4 +271,4 @@ Resolvers and auditors MUST reject mismatched artifacts and MUST distinguish bet - dev@commandlayer.org - PGP 5016 D496 9F38 22B2 C5A2 FA40 99A2 6950 197D AB0A -**Status:** v1.1.0 active in-repo schema family with pending CID; v1.0.0 retained as the historical pinned canonical release. +**Status:** v1.1.0 current canonical in-repo schema family with pending CID publication metadata; v1.0.0 retained as the historical pinned release. diff --git a/SECURITY.md b/SECURITY.md index 74020cf..f85277d 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -46,4 +46,4 @@ These guarantees keep Commons safe to depend on long-term. --- -Status: v1.0.0 locked as the last fully pinned canonical release • v1.1.0 active as the current pre-release candidate • verifiable semantics +Status: v1.0.0 retained as the historical pinned release • v1.1.0 documented as the current canonical in-repo line • verifiable semantics diff --git a/SECURITY_PROVENANCE.md b/SECURITY_PROVENANCE.md index 5c1a22a..a751652 100644 --- a/SECURITY_PROVENANCE.md +++ b/SECURITY_PROVENANCE.md @@ -1,10 +1,10 @@ # Security Provenance — Protocol Commons **Scope:** Protocol-Commons -**Status:** v1.1.0 — Pre-Release Candidate; v1.0.0 remains the last pinned canonical release +**Status:** v1.1.0 — Current Canonical In-Repo Line; v1.0.0 remains the historical pinned release **This document is NORMATIVE and ENFORCEABLE.** Defines cryptographic provenance, integrity guarantees, and audit mechanisms -for published and release-candidate Protocol-Commons schemas. +for published and current in-repo Protocol-Commons schemas. --- @@ -26,13 +26,13 @@ Current canonical pinned release: **v1.0.0** Integrity sources: - **v1.0.0 CID:** `bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m` -- **v1.1.0 CID:** `TBD (pre-release; pinning not yet published)` +- **v1.1.0 CID:** `PENDING` (pinning not yet published) - `checksums.txt` — file-level hashes - CI strict validation (Ajv) - `RESOLUTION.md` — immutable lifecycle history - `manifest.json` — current package metadata and pin target state -Until a v1.1.0 CID is published and recorded, resolvers and auditors MUST treat v1.1.0 as a pre-release schema family rather than the last fully pinned canonical release. +Until a v1.1.0 CID is published and recorded, resolvers and auditors MUST treat v1.1.0 as the current canonical in-repo schema family rather than the historical pinned release. Any semantic update requires: - New `schemas/vX.Y.Z/` directory @@ -45,7 +45,7 @@ Auditors MUST verify: - HTTP and IPFS mirrors match exactly for pinned canonical releases - Checksums remain unchanged - Version directories are immutable -- A release is not described as fully canonical unless its CID publication is complete +- The current canonical in-repo line is not misdescribed as the historical pinned release before CID publication is complete --- @@ -60,7 +60,7 @@ Resolvers MUST reject any: - Unauthorized or missing TXT keys - Out-of-sync version binding -For v1.1.0 specifically, TXT/CID binding MUST NOT be represented as canonical until the release CID is published. +For v1.1.0 specifically, TXT/CID binding MUST NOT be represented as a published pinned release until CID publication is complete. --- @@ -75,4 +75,4 @@ Recovery requires **transparent governance** — never mutation in place. --- -**Status:** v1.1.0 is the current in-repo schema family and release candidate; v1.0.0 remains the last fully verifiable pinned canonical release. +**Status:** v1.1.0 is the current canonical in-repo schema family; v1.0.0 remains the historical fully verifiable pinned release. diff --git a/SPEC.md b/SPEC.md index d3d7171..e3b1832 100644 --- a/SPEC.md +++ b/SPEC.md @@ -25,17 +25,15 @@ Execution, payment, identity, and routing are the domain of other layers. This repository contains two materially different Commons schema families: -- **v1.1.0** — current in-repo schema family and active documentation target -- **v1.0.0** — legacy schema family and the last fully pinned canonical release +- **v1.1.0** — current canonical in-repo schema family and active documentation target +- **v1.0.0** — legacy schema family and historical pinned release -Because the v1.1.0 release CID is still unpublished, v1.1.0 MUST be treated as a **pre-release candidate for provenance purposes** even though its schema contracts are fully present in this repository. - -Implementers MUST distinguish between: +Repository metadata still records v1.1.0 CID publication as pending. Implementers MUST therefore distinguish between: 1. **Schema semantics** — what the v1.1.0 files require 2. **Release provenance status** — whether a version has completed CID publication and canonical pinning -This specification therefore documents the v1.1.0 contract explicitly while preserving v1.0.0 as the last pinned canonical release until v1.1.0 pinning is complete. +This specification documents the v1.1.0 contract as the current canonical line while preserving v1.0.0 as the historical pinned release until v1.1.0 pinning is complete. --- @@ -273,7 +271,7 @@ The current v1.1.0 schema family is identified by: - Package version: `1.1.0` - Manifest entry: `manifest.json` - File-level hashes: `checksums.txt` -- IPFS directory CID: `TBD (pre-release)` until a release CID is published +- IPFS directory CID: `PENDING` until CID publication is complete The last fully pinned canonical release is: @@ -285,7 +283,7 @@ Auditors and resolvers SHOULD: 1. Fetch the versioned schemas 2. Verify integrity locally 3. Treat mismatched artifacts as untrusted -4. Treat v1.1.0 as not yet fully pinned until its CID publication is complete +4. Treat v1.1.0 as the current canonical in-repo line, distinct from the historical pinned release, until CID publication is complete Integrity check command: @@ -304,9 +302,9 @@ An implementation supporting Commons v1.1.0 MUST: 3. Validate the flat receipt shape exactly as published 4. Treat published version directories as immutable 5. Preserve receipt trust semantics as hashes plus signatures, without inventing unsupported guarantees -6. Avoid representing v1.1.0 as the last fully pinned canonical release until CID publication is complete +6. Avoid representing v1.1.0 as the historical pinned release until CID publication is complete -A system supporting any canonical verb MAY claim **Commons-Compatible** for that version, but provenance claims MUST accurately reflect whether the relevant version is fully pinned or still pre-release. +A system supporting any canonical verb MAY claim **Commons-Compatible** for that version, but provenance claims MUST accurately reflect whether the relevant version is the current canonical in-repo line or the historical pinned release. --- @@ -319,7 +317,7 @@ If any of the following occur: - required conditional receipt fields are missing - published artifacts differ from expected checksums - published artifacts are mutated in place -- a pre-release version is misrepresented as fully pinned canonical provenance +- a current canonical in-repo version is misrepresented as the historical pinned release consumers MUST treat the artifact as untrusted and SHOULD reject it. @@ -344,5 +342,5 @@ Security escalation MUST follow repository policy. ## Status -**v1.1.0:** current schema family, documented here, CID still pending -**v1.0.0:** legacy schema family and last pinned canonical release +**v1.1.0:** current canonical schema family documented here; CID publication status remains pending in repository metadata +**v1.0.0:** legacy schema family and historical pinned release diff --git a/manifest.json b/manifest.json index 04b9f49..0d3f387 100644 --- a/manifest.json +++ b/manifest.json @@ -77,7 +77,7 @@ ], "latest_commons_root": "schemas/v1.1.0/commons", "pin_target": "schemas/v1.1.0/commons", - "status": "pre-release-candidate", + "status": "current-canonical-line", "historical_releases": [ { "version": "1.0.0", @@ -151,7 +151,7 @@ ], "active_release": { "version": "1.1.0", - "status": "pre-release-candidate", + "status": "current-canonical-line", "schemas_root": "schemas/v1.1.0", "commons_root": "schemas/v1.1.0/commons", "examples_root": "examples/v1.1.0",