Update POLICY.md

Author: GsCommand

POLICY.md

@@ -1,150 +1,105 @@
 
-# Protocol Commons Policy
+# Protocol-Commons Policy
 
-This document defines the canonical rules for creating, validating, and publishing verb schemas in the CommandLayer Protocol Commons.
+This document defines the canonical rules for creating, validating, versioning, and publishing verb schemas in the CommandLayer Protocol Commons.
 
-The Protocol Commons provides the universal language foundation for all agents and autonomous workflows.
+The Commons is the universal grammar for autonomous agents.
 
 ---
 
-## 1. Canonical Rules
-
-All canonical verbs MUST:
-
-- Be lowercase, single-word identifiers  
-- Define both:
-  ```
-  <verb>.request.schema.json
-  <verb>.receipt.schema.json
-  ```
-- Validate under **strict Ajv** with:
-  - Draft 2020-12
-  - strict mode enabled
-  - no additionalProperties
-  - no union types beyond explicitly allowed structures
- ----
-- Use deterministic `$id` URLs:
-  ```
-  https://commandlayer.org/schemas/v1.0.0/commons/<verb>/requests/<verb>.request.schema.json
-  ```
-- Follow fixed directory structure:
-  ```
-  /schemas/v1.0.0/commons/<verb>/...
-  ```
-- Remain **immutable** once published
-
-Schemas MUST be domain-neutral and free of vendor-specific semantics.
+## 1. Verbs Must Remain Canonical
+
+- Single lowercase word  
+- One meaning; no semantic overload  
+- Domain-neutral  
+- Published only after governance review
+
+Common verbs **SHALL NOT** model:
+- Payments
+- Contracts / transfers
+- Authentication
+- Business logic
+
+Those belong in the _Commercial_ layer.
 
 ---
 
-## 2. Required Files Per Verb
+## 2. Required Artifacts Per Verb
 
-Each verb MUST contain:
+Each canonical verb MUST define:
 
 - `requests/<verb>.request.schema.json`
 - `receipts/<verb>.receipt.schema.json`
+
+And MUST ship:
+- 
 - `examples/valid/*.json`
 - `examples/invalid/*.json`
 
-Request + receipt schemas MUST reference:
-
-```
-schemas/v1.0.0/_shared/*.schema.json
-```
 
 ---
 
-## 3. ENS TXT Requirements
+## 3. JSON Schema Requirements
 
-All canonical verbs MUST have resolvable ENS TXT entries:
+- Draft **2020-12**
+- Ajv **strict mode**
+- `"additionalProperties": false` at top level
+- Deterministic `$id` and directory structure:
 
-```
-cl.verb=<verb>
-cl.version=1.0.0
+/schemas/v1.0.0/commons/<verb>/
 
-cl.entry=x402://<verbagent>.eth/<verb>/v1
 
-cl.schema.request=https://commandlayer.org/schemas/v1.0.0/commons/<verb>/requests/<verb>.request.schema.json
-cl.schema.receipt=https://commandlayer.org/schemas/v1.0.0/commons/<verb>/receipts/<verb>.receipt.schema.json
-
-cl.cid.schemas=<cid-schemas>
-cl.schemas.mirror.ipfs=https://ipfs.io/ipfs/<cid-schemas>
-
-cl.agentcard=https://commandlayer.org/agent-cards/agents/v1.0.0/commons/<verbagent>.eth.json
-cl.cid.agentcard=<cid-agentcard>
-cl.agentcard.mirror.ipfs=https://ipfs.io/ipfs/<cid-agentcard>/agents/<verbagent>.eth.json
+---
 
-cl.checksum.request=<sha256-request>
-cl.checksum.receipt=<sha256-receipt>
-cl.checksum.agentcard=<sha256-agentcard>
+## 4. x402 Alignment
 
-cl.owner=commandlayer.eth
+All requests:
+`x402.verb = <verb>`
+`x402.version = "1.0.0"`
 
-```
 
-ENS bindings are **critical protocol resources** and may only be modified through governance.
+All receipts:
+`x402.status = "ok" | "error"`
 
 ---
 
-## 4. Versioning Policy
-
-Version bumps follow:
+## 5. Immutability
 
-- **MAJOR** — Breaking changes to request/receipt shape, trace semantics, or $id structure  
-- **MINOR** — Additive fields that do not break interoperability  
-- **PATCH** — Documentation or example fixes  
-
-Once a directory is versioned (e.g., `v1.0.0`), it is **frozen forever**.
-
-Upgrades require a parallel directory:
-
-```
-/schemas/v1.1.0/commons/<verb>/...
-```
+Once published:
+- **No changes** in-place
+- Any update requires a new version directory  
+- New CID + new checksums  
+- ENS TXT updates  
 
 ---
 
-## 5. Integrity & Provenance
-
-All schema files MUST be represented in:
+## 6. Breaking Change Rules
 
-- `checksums.txt`
-- `SECURITY_PROVENANCE.md`
+### Requires MAJOR version bump:
+- Removing fields
+- Changing requiredness
+- New semantics for success/error
+- Trace model changes
 
-Every release MUST:
+### Requires MINOR:
+- Additive `input.*` or `result.*`
 
-- Update the IPFS CID  
-- Update checksums  
-- Update ENS TXT if applicable  
+### PATCH:
+- Example or documentation fixes
 
 ---
 
-## 6. Immutability Principle
+## 7. Governance Compliance
 
-The Protocol Commons operates under a strict immutability rule:
-
- No schema changes, once published in a versioned directory, may be altered in-place.
-
-All corrective or breaking changes MUST be handled via new versioned directories.
-
----
+Every change MUST:
+- Have an issue link
+- Be recorded in `RESOLUTION.md`
 
-## 7. Deprecation Policy
 
-Deprecated verbs or schemas MUST be:
 
-1. Logged in `RESOLUTION.md` (with rationale and timestamp)  
-2. Documented in `SPEC.md`  
-3. Preserved for backward compatibility  
 
-Removal is only permitted for verified security risks and MUST include a migration path.
 
-## Links
 
-- [SECURITY POLICY](./SECURITY.md) — responsible disclosure and vulnerability handling  
-- [RESOLUTION](./RESOLUTION.md) — governance and deprecation log  
-- [POLICY](./POLICY.md) — verbs and ENS binding rules  
-- [GOVERNANCE](./GOVERNANCE.md) — decision-making and multisig control