Skip to content

Commit 63152c8

Browse files
authored
Update SECURITY_PROVENANCE.md
1 parent 8770330 commit 63152c8

1 file changed

Lines changed: 61 additions & 33 deletions

File tree

SECURITY_PROVENANCE.md

Lines changed: 61 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -1,56 +1,84 @@
1+
# Security & Provenance — Protocol-Commons
12

2-
# Security Provenance
3+
This file defines ownership, disclosure rules, version integrity,
4+
and cryptographic provenance for the Commons.
35

4-
**Version:** v1.0.0
5-
**Scope:** `schemas/v1.0.0` (commons verbs + `_shared`)
6-
**Owner:** `commandlayer.eth`
6+
---
77

8-
## IPFS
8+
## Ownership & Contact
99

10-
- **Schemas CID (v1.0.0):** ``
11-
- **Directory Layout:**
12-
- `commons/` — canonical verb request/receipt schemas
13-
- `_shared/` — x402, trace, and receipt base primitives
10+
- **Owner:** commandlayer.eth
11+
- **Security Contact:** dev@commandlayer.org
12+
- **PGP Fingerprint:** 5016 D496 9F38 22B2 C5A2 FA40 99A2 6950 197D AB0A
1413

15-
This CID represents the **immutable v1.0.0 release** of the Protocol Commons schema tree.
16-
Any modification requires a **new version folder** (e.g., `v1.0.1`) and a **new CID** published in this document.
14+
---
1715

18-
## Checksums
16+
## Vulnerability Disclosure
1917

20-
All file-level integrity is verified using **SHA-256** digests stored in the repository’s `checksums.txt`.
18+
Report security issues privately:
2119

22-
Any change to files under `schemas/v1.0.0` MUST trigger:
20+
**Email: dev@commandlayer.org**
21+
22+
**Use PGP for sensitive reports**
2323

24-
1. Regeneration of `checksums.txt`
25-
2. A new tagged release (e.g., `commons-v1.0.1`)
26-
3. A new IPFS pin + CID
27-
4. An update to this provenance document
24+
We will:
25+
- Acknowledge valid issues within **72 hours**
26+
- Provide mitigation plan within **10 business days**
2827

29-
## ENS / Resolution Rules
28+
---
29+
30+
## Provenance
31+
32+
### Current Release: v1.0.0
33+
34+
- **Schemas CID:** `bafybeieoynknzalaojwpzjzjy77kpnfe4kla5io7jbfnmyu7w7vyvuljpq`
35+
- Integrity: via `checksums.txt` (SHA-256)
36+
- All schemas validated under strict mode CI
37+
38+
### Any change requires:
39+
- New version directory
40+
- New CID
41+
- Updated checksums
42+
- Logged in `RESOLUTION.md`
43+
44+
---
45+
46+
## ENS TXT Responsibilities
47+
48+
Commons controls ONLY:
49+
```
50+
cl.verb
51+
cl.version
52+
cl.schema.request
53+
cl.schema.receipt
54+
cl.cid.schemas
55+
cl.schemas.mirror.ipfs
56+
```
57+
58+
Updates MUST be signed + logged.
59+
60+
---
61+
62+
## Immutability Guarantee
63+
64+
Once published:
65+
- No schema changes in-place
66+
- No silent mutability
67+
- Breaks require new version
68+
69+
---
70+
71+
Status: **Security-Critical, Stable**
3072

31-
**ENS Name:** `commandlayer.eth`
3273

33-
Each verb **MUST** expose ENS TXT records including:
3474

35-
- cl.verb — the canonical machine verb this agent implements
36-
- cl.version — the semantic version of the verb specification this agent follows
3775

38-
- cl.entry — the x402-style execution entrypoint for this capability
3976

40-
- cl.schema.request — the HTTPS location of the official request schema
41-
- cl.schema.receipt — the HTTPS location of the official receipt schema
4277

43-
- cl.cid.schemas — the IPFS CID for the full schema bundle this capability belongs to
4478

45-
- cl.checksum.request — the integrity hash for the request schema
46-
- cl.checksum.receipt — the integrity hash for the receipt schema
4779

48-
- cl.agentcard — the public AgentCard describing metadata, identity, and capabilities
49-
- cl.manifest — the manifest file that indexes and describes the entire release
5080

51-
- cl.owner — the ENS or organizational owner responsible for this verb definition
5281

5382

54-
**Any modification to `ENS TXT` layout, `CID binding`, or `verb metadata` MUST be logged in `RESOLUTION.md` and approved under governance**.
5583

5684

0 commit comments

Comments
 (0)