← Back to PG Protocol Architecture
Spiralweb contains many protocols developed over multiple years.
Not all are operational. Not all are public. Not all are structured.
This document defines how protocols are classified and activated.
1. Protocol Classes
- Constitutional — Governance spine (PG-PROT-000 → 003).
- Operational — Deployable field protocols (e.g. PG-RAPID cases).
- Structured — JSON / bundle-level machine protocols.
- Draft — Conceptual or exploratory drafts.
- Artistic / Exploratory — Research or narrative prototypes.
- Archived — Historical record; not active.
2. Status States
- Active — Publicly deployable.
- Deployable — Structurally complete, awaiting activation.
- Structured — Machine-formatted but not active.
- Draft — Under development.
- Archived — Historical.
- Deprecated — No longer valid.
3. Minimum Criteria for Active Status
An operational protocol must include:
- Executive Briefing
- Topic Matrix
- Protocol Map
- Roadmap
- Risks & Mitigations
- Governance Constraints
- 13-Field Integration
Without these components, a protocol cannot be marked Active.
4. Registry Logic
All protocols under /protocols/ are part of the archive.
Only those explicitly referenced within Café Sofia governance pages
are considered within the active civic layer.
Classification precedes activation.
Activation precedes deployment.
Deployment requires verification.
5. Structural Principle
- No protocol is assumed valid without classification.
- No activation without documentation.
- No deployment without governance anchoring.
- No growth without correction loops.
This registry prevents overclaiming, drift, and structural confusion.