Update POLICY.md

Author: GsCommand

POLICY.md

@@ -1,106 +1,106 @@
+# POLICY — Protocol-Commons
+CommandLayer Core Standards · Semantic Layer
 
-# Protocol-Commons Policy
+This document defines **publication rules** for Common verbs and schemas.
+`SPEC.md` remains the primary normative authority.
 
-This document defines the canonical rules for creating, validating, versioning, and publishing verb schemas in the CommandLayer Protocol Commons.
+---
 
-The Commons is the universal grammar for autonomous agents.
+## 1. Canonical Verb Requirements
 
----
+A canonical verb MUST:
 
-## 1. Verbs Must Remain Canonical
+- Be a **single lowercase word**
+- Have exactly **one** interpretation
+- Be **domain-neutral** and non-commercial
+- Be approved through governance review PRIOR to publication
 
-- Single lowercase word  
-- One meaning; no semantic overload  
-- Domain-neutral  
-- Published only after governance review
+Commons verbs SHALL NOT encode:
 
-Common verbs **SHALL NOT** model:
-- Payments
-- Contracts / transfers
-- Authentication
-- Business logic
+- Payments or finance
+- Authentication or identity proofing
+- Business-specific logic
 
-Those belong in the _Commercial_ layer.
+Those belong to **Commercial** standards.
 
 ---
 
 ## 2. Required Artifacts Per Verb
 
-Each canonical verb MUST define:
+Each verb MUST include:
 
 - `requests/<verb>.request.schema.json`
 - `receipts/<verb>.receipt.schema.json`
+- Valid + invalid example sets:
+
+`examples/valid/.json`
+`examples/invalid/.json`
 
-And MUST ship:
-- 
-- `examples/valid/*.json`
-- `examples/invalid/*.json`
+vbnet
+Copy code
+Schematics MUST reference shared primitives under:
 
+schemas/v1.0.0/_shared/
 
 ---
 
 ## 3. JSON Schema Requirements
 
 - Draft **2020-12**
-- Ajv **strict mode**
-- `"additionalProperties": false` at top level
-- Deterministic `$id` and directory structure:
+- Ajv **strict** validation
+- `"additionalProperties": false`
+- Deterministic `$id` structure:
 
-/schemas/v1.0.0/commons/<verb>/
+https://commandlayer.org/schemas/v1.0.0/commons/<verb>/requests/<verb>.request.schema.json
+https://commandlayer.org/schemas/v1.0.0/commons/<verb>/receipts/<verb>.receipt.schema.json
 
 
+Directory layout MUST NOT vary.
+
 ---
 
-## 4. x402 Alignment
+## 4. x402 Alignment (Normative)
+
+**All requests MUST define:**
 
-All requests:
-`x402.verb = <verb>`
-`x402.version = "1.0.0"`
+- x402.verb = <verb>
+- x402.version = "1.0.0"
 
 
-All receipts:
+**All receipts MUST define:**
+
 `x402.status = "ok" | "error"`
 
+Trace MUST echo `request.trace.requestId`.
+
 ---
 
 ## 5. Immutability
 
 Once published:
-- **No changes** in-place
-- Any update requires a new version directory  
-- New CID + new checksums  
-- ENS TXT updates  
-
----
-
-## 6. Breaking Change Rules
 
-### Requires MAJOR version bump:
-- Removing fields
-- Changing requiredness
-- New semantics for success/error
-- Trace model changes
+- No modification permitted in-place
+- Breaking change → new major version dir
+- Additive change → minor version dir
+- Example/docs fixes → patch version
 
-### Requires MINOR:
-- Additive `input.*` or `result.*`
+New versions MUST include:
 
-### PATCH:
-- Example or documentation fixes
+- Updated CIDs
+- Updated checksums
+- ENS TXT update where applicable
 
 ---
 
-## 7. Governance Compliance
+## 6. Governance Compliance
 
 Every change MUST:
+
 - Have an issue link
+- Pass CI validation
 - Be recorded in `RESOLUTION.md`
+- Be signed by governance maintainer
 
+---
 
-
-
-
-
-
-
-
-
+_Last updated: v1.0.0 — Stable-Lock_