docs: align release-facing docs with v1.1.0 posture

CHANGELOG.md

@@ -7,7 +7,7 @@ Released as the current Protocol-Commons version and active schema line.
 - Added the flat Commons schema family under `schemas/v1.1.0/commons`
 - Published self-contained request and receipt schemas for the 10 canonical Commons verbs
 - Removed shared `$ref` dependencies from the v1.1.0 Commons schema family
-- Standardized v1.1.0 receipts around a compact attestation-oriented structure
+- Standardized v1.1.0 receipts around a compact checksum-oriented structure
 - Documented v1.1.0 as the current release and active schema line
 - Retained v1.0.0 only as a historical legacy release for compatibility review and auditing
 - Clarified that HTTPS schema hosting and IPFS pinning are separate publication layers

CONTRIBUTING.md

@@ -44,13 +44,13 @@ If you change a schema or semantic contract, you must also:
 - Preserve immutability of published version directories unless the change is explicitly historical documentation only
 - Review `SCHEMAS.md` and `SPEC.md` for versioning implications
 - Update `CHANGELOG.md` when the externally visible contract changes
-- Update `RESOLUTION.md`, provenance, or checksum artifacts if the release process requires it
+- Update `RESOLUTION.md`, `manifest.json`, and checksum artifacts when the release process requires it
 
 ## Versioning Expectations
 
 - Treat published release lines as append-only history
 - Use a new version directory for semantic changes
-- Keep `v1.1.0` documented as the current in-repo line until a newer line is intentionally introduced
+- Keep `v1.1.0` documented as the current release and active schema line until a newer line is intentionally introduced
 
 ## Review Standard
 

README.md

@@ -24,9 +24,9 @@ The current release is **v1.1.0**. The active schema line is **`schemas/v1.1.0/c
 
 - **Current release:** `v1.1.0`
 - **Active schema line:** `schemas/v1.1.0/commons`
-- **Pinned canonical release after CID insertion:** `v1.1.0`
-- **Current IPFS publication state for v1.1.0:** `schemas_cid: PENDING` in `manifest.json`, meaning IPFS publication is tracked separately from the HTTPS-hosted schema line
-- **Historical release:** `v1.0.0` with CID `bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m`
+- **Pinned canonical release:** `v1.1.0` once its CID is recorded in `manifest.json`
+- **Historical release:** `v1.0.0` with published CID `bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m`
+- **IPFS publication tracking:** recorded in `manifest.json` separately from HTTPS schema hosting
 
 HTTPS hosting and IPFS pinning are separate distribution layers:
 
@@ -203,7 +203,7 @@ Example paths:
 - active release version
 - schema roots
 - example roots
-- IPFS publication state
+- IPFS publication record
 - historical release metadata
 
 `checksums.txt` records SHA-256 checksums for shipped schema artifacts.

RESOLUTION.md

@@ -17,7 +17,7 @@ It records:
 | Date | Version | Status | Summary | Approver |
 |------|---------|--------|---------|----------|
 | 2025-12-06 | 1.0.0 | Historical legacy release | Initial Protocol-Commons release with versioned schemas, shared primitives, and the original nested Commons layout. Historical CID: `bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m`. | Founding Steward |
-| 2026-03-18 | 1.1.0 | Current release and active schema line | Published the flat Commons schema family under `schemas/v1.1.0/commons`, simplified request and receipt contracts, and documented v1.1.0 as the active schema line. IPFS publication is tracked separately and remains `PENDING` in `manifest.json` until a CID is recorded. | Founding Steward |
+| 2026-03-18 | 1.1.0 | Current release and active schema line | Published the flat Commons schema family under `schemas/v1.1.0/commons`, simplified request and receipt contracts, and documented v1.1.0 as the active schema line. IPFS publication is tracked separately in `manifest.json` and can be recorded when a CID is published. | Founding Steward |
 
 ---
 

SCHEMAS.md

@@ -223,11 +223,8 @@ Current HTTPS schema root:
 https://commandlayer.org/schemas/v1.1.0/
 ```
 
-Manifest-tracked IPFS publication state for v1.1.0:
+Manifest-tracked IPFS publication for v1.1.0 is recorded in `manifest.json` when a CID is published.
 
-```text
-PENDING
-```
 
 Historical legacy CID record:
 

SECURITY.md

@@ -38,12 +38,12 @@ Breaking issues are prioritized.
 ## Integrity Rules
 
 - Versioned directories are **immutable** once published  
-- All schemas pinned to IPFS + checksummed  
-- Strict, reproducible CI validation  
-- Any change requires **a new version** — never hot patches
+- Schema artifacts are covered by checksum-based integrity records  
+- Release metadata and publication records are documented in the repository  
+- Any semantic change requires **a new version** — never hot patches
 
 These guarantees keep Commons safe to depend on long-term.
 
 ---
 
-Status: v1.0.0 retained as the historical pinned release • v1.1.0 documented as the current canonical in-repo line • verifiable semantics
+Status: v1.1.0 is the current release and active schema line • v1.0.0 is the historical legacy release • IPFS publication is tracked separately in documented release metadata

SECURITY_PROVENANCE.md

@@ -41,11 +41,11 @@ Current release state:
 
 - **Current release:** `v1.1.0`
 - **Active schema line:** `schemas/v1.1.0/commons`
-- **Manifest-tracked CID for v1.1.0:** `PENDING`
+- **CID recording for v1.1.0:** entered in `manifest.json` when the release is published to IPFS
 - **Historical legacy release:** `v1.0.0`
 - **Historical v1.0.0 CID:** `bafybeigvf6nkzws7dblos74dqqjkguwkrwn4a2c27ieygoxmgofyzdkz6m`
 
-IPFS publication is tracked separately from HTTPS hosting. The v1.1.0 HTTPS schema URLs can be live while the manifest still records `schemas_cid: PENDING` for the IPFS publication step.
+IPFS publication is tracked separately from HTTPS hosting. The v1.1.0 HTTPS schema URLs can be live before or after the repository records a CID for that release in `manifest.json`.
 
 ## Publication Layers