From a6b2a2e7d113670934c07b22f23d2ecb8741c1bb Mon Sep 17 00:00:00 2001 From: Greg Soucy Date: Fri, 20 Mar 2026 00:29:32 -0400 Subject: [PATCH] Clarify v1.1.0 HTTPS hosting status --- COMPLIANCE.md | 8 ++++---- GOVERNANCE.md | 6 +++--- README.md | 13 +++++++------ RESOLUTION.md | 4 ++-- SCHEMAS.md | 12 +++++++++--- SECURITY_PROVENANCE.md | 11 ++++++----- SPEC.md | 25 +++++++++++++------------ manifest.json | 8 ++++---- package.json | 2 +- 9 files changed, 49 insertions(+), 40 deletions(-) diff --git a/COMPLIANCE.md b/COMPLIANCE.md index 5b6d466..da4b886 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 canonical in-repo schema family; repository metadata still records CID publication as pending +- **v1.1.0** — current canonical HTTPS-hosted schema family; repository metadata still records IPFS 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 describe provenance accurately and MUST NOT claim that v1.1.0 is the historical pinned release while CID publication remains unpublished in repository metadata. +A system MUST describe provenance accurately and MUST NOT claim that v1.1.0 is the historical pinned release while IPFS 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 be validated locally, and compliance statements MUST distinguish the current canonical in-repo line from the historical pinned release until 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 HTTPS-hosted line from the historical pinned release until IPFS 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 current canonical in-repo or historical pinned release +- Version status is described accurately as current canonical HTTPS-hosted or historical pinned release If uncertain → treat the implementation as **experimental**. diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 5bf3215..bb6e312 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -99,7 +99,7 @@ Attempts to mutate semantics in place MUST be treated as **UNTRUSTED**. The current lock states are interpreted strictly: - **v1.0.0 historical pinned release** means the legacy release line with published CID, immutable checksums, and locked provenance -- **v1.1.0 current canonical working line** means the current repository contract and primary documentation target; CID publication remains pending in repository provenance metadata +- **v1.1.0 current canonical HTTPS-hosted line** means the current repository contract, primary documentation target, and live HTTPS schema namespace; IPFS 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 CID publication is complete, contributors MUST describe that version accurately as the current canonical working line and MUST NOT misstate it as the historical pinned release. +Until IPFS CID publication is complete, contributors MUST describe that version accurately as the current canonical HTTPS-hosted 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 retained as the historical pinned release; v1.1.0 documented as the current canonical working line_ +_Last updated: v1.0.0 retained as the historical pinned release; v1.1.0 documented as the current canonical HTTPS-hosted line_ Steward declaration (plain-text repository statement, not a cryptographic signature): **`commandlayer.eth`** *Founding Steward — CommandLayer Semantic Standards* diff --git a/README.md b/README.md index 72f25b2..d020073 100644 --- a/README.md +++ b/README.md @@ -12,8 +12,8 @@ > **Integrity Notice — Protocol-Commons v1.1.0** > -> `schemas/v1.1.0/commons` is the current canonical **working line in this repository**. -> Its publication metadata still says `schemas_cid: PENDING`, so this line is **not yet the externally pinned canonical release**. +> `schemas/v1.1.0/commons` is the current canonical schema family in this repository, and its HTTPS schema URLs are live under `https://commandlayer.org/schemas/v1.1.0/...`. +> Its metadata still says `schemas_cid: PENDING`, so v1.1.0 is **not yet the IPFS-pinned canonical release**. > > `v1.0.0` remains the last **externally pinned canonical release**: > `schemas/v1.0.0/` — CID: `bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m` @@ -182,7 +182,7 @@ console.log(validate.errors ?? []); Commons v1.1.0 is the current canonical schema family in this repository. -It is the primary documentation and validation target for Commons. The repository still records CID publication as pending, so `v1.1.0` should be treated as the active working line rather than the last externally pinned release. `v1.0.0` is retained as the historical pinned release line. +It is the primary documentation and validation target for Commons, and its canonical HTTPS `$id` URLs are live. The repository still records IPFS CID publication as pending, so `v1.1.0` should be treated as the current HTTPS-published schema family rather than the last IPFS-pinned release. `v1.0.0` is retained as the historical pinned release line. - Each request schema is standalone - Each receipt schema is standalone @@ -348,11 +348,11 @@ Commons gives upper layers a stable meaning layer to build around. ## Status -**v1.1.0 — current canonical working line** +**v1.1.0 — current canonical HTTPS-hosted schema line** - `v1.1.0` is the current flat Commons layout in this repo - `v1.0.0` remains the historical pinned release line -- Do not describe `v1.1.0` as externally pinned or historically locked until CID publication is complete +- Do not describe `v1.1.0` as IPFS-pinned or historically locked until CID publication is complete --- @@ -394,9 +394,10 @@ 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 +- HTTPS hosting status (live for `https://commandlayer.org/schemas/v1.1.0/...`) - CID publication status (`PENDING` in `manifest.json` until published) -Treat `schemas_cid: PENDING` as an explicit signal that the v1.1.0 line is still awaiting external publication/provenance, even though it is the repo's current schema target. +Treat `schemas_cid: PENDING` as an explicit signal that IPFS provenance for v1.1.0 is still awaiting publication, even though the v1.1.0 HTTPS schema identifiers are already live and this is the repo's current schema target. --- diff --git a/RESOLUTION.md b/RESOLUTION.md index 8f219e8..9f82b20 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 current canonical in-repo line recorded, CID publication 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 canonical HTTPS schema hosting live; IPFS 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 current canonical in-repo line recorded, CID publication pending; v1.0.0 remains the historical pinned release. +**Status:** v1.1.0 canonical HTTPS schema hosting is live, IPFS CID publication remains pending; v1.0.0 remains the historical pinned release. diff --git a/SCHEMAS.md b/SCHEMAS.md index 48075ef..9c49bfb 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 accurately as the current canonical in-repo line and MUST distinguish it from the historical pinned release 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 HTTPS-hosted schema line and MUST distinguish it from the historical pinned release until a real CID is published. --- @@ -250,6 +250,12 @@ Integrity is tracked by: - `checksums.txt` - `manifest.json` +Current v1.1.0 canonical HTTPS schema root: + +```text +https://commandlayer.org/schemas/v1.1.0/ +``` + Current v1.1.0 schema CID status: ```text @@ -262,7 +268,7 @@ Last pinned canonical release content identifier: v1.0.0 → bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m ``` -Resolvers and auditors MUST reject mismatched artifacts and MUST distinguish between the current canonical in-repo schema family and the historical pinned release. +Resolvers and auditors MUST reject mismatched artifacts and MUST distinguish between the current canonical HTTPS-hosted schema family and the historical pinned release. --- @@ -271,4 +277,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 current canonical in-repo schema family with pending CID publication metadata; v1.0.0 retained as the historical pinned release. +**Status:** v1.1.0 current canonical HTTPS-hosted schema family with pending CID publication metadata; v1.0.0 retained as the historical pinned release. diff --git a/SECURITY_PROVENANCE.md b/SECURITY_PROVENANCE.md index a751652..915fc1a 100644 --- a/SECURITY_PROVENANCE.md +++ b/SECURITY_PROVENANCE.md @@ -26,13 +26,14 @@ Current canonical pinned release: **v1.0.0** Integrity sources: - **v1.0.0 CID:** `bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m` -- **v1.1.0 CID:** `PENDING` (pinning not yet published) +- **v1.1.0 HTTPS canonical root:** `https://commandlayer.org/schemas/v1.1.0/` (live) +- **v1.1.0 CID:** `PENDING` (IPFS 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 the current canonical in-repo schema family rather than the historical pinned release. +Until a v1.1.0 CID is published and recorded, resolvers and auditors MUST treat v1.1.0 as the current canonical HTTPS-hosted schema family rather than the historical pinned release. Any semantic update requires: - New `schemas/vX.Y.Z/` directory @@ -42,10 +43,10 @@ Any semantic update requires: **No silent edits. No exceptions.** Auditors MUST verify: -- HTTP and IPFS mirrors match exactly for pinned canonical releases +- HTTPS and IPFS mirrors match exactly for pinned canonical releases - Checksums remain unchanged - Version directories are immutable -- The current canonical in-repo line is not misdescribed as the historical pinned release before CID publication is complete +- The current canonical HTTPS-hosted line is not misdescribed as the historical pinned release before CID publication is complete --- @@ -75,4 +76,4 @@ Recovery requires **transparent governance** — never mutation in place. --- -**Status:** v1.1.0 is the current canonical in-repo schema family; v1.0.0 remains the historical fully verifiable pinned release. +**Status:** v1.1.0 is the current canonical HTTPS-hosted schema family with pending IPFS CID publication; v1.0.0 remains the historical fully verifiable pinned release. diff --git a/SPEC.md b/SPEC.md index 8bcce8d..d78e32e 100644 --- a/SPEC.md +++ b/SPEC.md @@ -25,15 +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 canonical in-repo schema family and active documentation target +- **v1.1.0** — current canonical schema family, active documentation target, and live HTTPS-hosted identifier set - **v1.0.0** — legacy schema family and historical pinned release -Repository metadata still records v1.1.0 CID publication as pending. Implementers MUST therefore distinguish between: +Repository metadata still records v1.1.0 IPFS 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 +1. **Schema semantics and canonical HTTPS identifiers** — what the v1.1.0 files require and where their `$id` values resolve +2. **Release provenance status** — whether a version has completed IPFS CID publication and canonical pinning -This specification documents the v1.1.0 contract as the current canonical working line while preserving v1.0.0 as the historical pinned release until v1.1.0 pinning is complete. +This specification documents the v1.1.0 contract as the current canonical schema family while preserving v1.0.0 as the historical pinned release until v1.1.0 IPFS pinning is complete. --- @@ -209,7 +209,7 @@ schemas/v1.0.0/commons//receipts/.receipt.schema.json Every v1.1.0 schema MUST use the canonical HTTPS `$id` namespace under this pattern. -Those `$id` values are stable schema identifiers inside the repository and validation tooling. They SHOULD resolve over live HTTPS once publication/hosting is completed, but live HTTPS resolution is not yet guaranteed by current v1.1.0 repository provenance metadata. +Those `$id` values are stable canonical schema identifiers. For v1.1.0 they MUST match the live HTTPS-hosted schema namespace and MUST resolve at the published HTTPS locations. This HTTPS hosting state is distinct from any separate IPFS CID publication record. ### Request @@ -274,7 +274,8 @@ 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: `PENDING` until CID publication is complete +- Canonical HTTPS schema host: `https://commandlayer.org/schemas/v1.1.0/` +- IPFS directory CID: `PENDING` until IPFS CID publication is complete The last fully pinned canonical release is: @@ -286,7 +287,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 the current canonical working line, distinct from the historical pinned release, until CID publication is complete +4. Treat v1.1.0 HTTPS identifiers as live canonical schema references, while treating IPFS provenance for v1.1.0 as pending until a CID is published Integrity check command: @@ -305,9 +306,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 historical pinned release until CID publication is complete +6. Avoid representing v1.1.0 as the historical pinned release until its IPFS 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 the current canonical working line or the historical pinned 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 HTTPS-hosted schema family or the historical pinned release. --- @@ -320,7 +321,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 current canonical in-repo version is misrepresented as the historical pinned release +- a current canonical HTTPS-hosted version is misrepresented as the historical pinned release consumers MUST treat the artifact as untrusted and SHOULD reject it. @@ -345,5 +346,5 @@ Security escalation MUST follow repository policy. ## Status -**v1.1.0:** current canonical schema family documented here; CID publication status remains pending in repository metadata +**v1.1.0:** current canonical schema family documented here; HTTPS hosting is live and IPFS CID publication remains pending in repository metadata **v1.0.0:** legacy schema family and historical pinned release diff --git a/manifest.json b/manifest.json index 8106103..a430289 100644 --- a/manifest.json +++ b/manifest.json @@ -2,7 +2,7 @@ "name": "@commandlayer/commons", "version": "1.1.0", "package_version": "1.1.0", - "description": "Commons verb + schema package metadata for the active v1.1.0 working line; external CID publication is still pending.", + "description": "Commons verb + schema package metadata for the active v1.1.0 canonical HTTPS-hosted schema line; IPFS CID publication is still pending.", "owner": "commandlayer.eth", "contact": "dev@commandlayer.org", "license": "MIT", @@ -77,7 +77,7 @@ ], "latest_commons_root": "schemas/v1.1.0/commons", "pin_target": "schemas/v1.1.0/commons", - "status": "current-working-line", + "status": "current-canonical-https-hosted", "historical_releases": [ { "version": "1.0.0", @@ -151,12 +151,12 @@ ], "active_release": { "version": "1.1.0", - "status": "current-working-line", + "status": "current-canonical-https-hosted", "schemas_root": "schemas/v1.1.0", "commons_root": "schemas/v1.1.0/commons", "examples_root": "examples/v1.1.0", "schemas_cid": "PENDING", - "pin_status": "pending-publication" + "pin_status": "https-published-ipfs-pending" }, "pinned_canonical_release": { "version": "1.0.0", diff --git a/package.json b/package.json index 4969294..0e8590c 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "@commandlayer/commons", "version": "1.1.0", - "description": "Canonical Commons verbs and strict JSON Schemas for autonomous agents \u2014 active v1.1.0 working line, historical pinned v1.0.0 release, and cross-runtime interoperability.", + "description": "Canonical Commons verbs and strict JSON Schemas for autonomous agents \u2014 active v1.1.0 HTTPS-hosted schema line, historical pinned v1.0.0 release, and cross-runtime interoperability.", "private": false, "type": "module", "license": "MIT",