Specifications
Registry of PAG documents — organized like an RFC editor, with immutable FINAL texts and public drafts.
Specification states
DRAFT → PROPOSED → FINAL
↘ EXPERIMENTAL (may not advance)
FINAL → OBSOLETE/SUPERSEDED (successor PAG)DRAFT: author submits; community feedback; expires after 6 months without activity.
PROPOSED: minimum 30-day review; blocking concerns resolved; maintainer vote.
FINAL: immutable text; permanent PAG number; production use; changes via new PAG or errata.
EXPERIMENTAL: novel approaches; not for production by default.
OBSOLETE / SUPERSEDED: replaced by a newer PAG; archive retained.
Categories
- COMPUTE
- Task scheduling, resource verification, orchestration
- CORE
- Runtime, core protocols, fundamental primitives
- GOVERNANCE
- Community processes; how proposals advance
- INFORMATIONAL
- Tutorials, guides, historical docs (not normative)
- MESH
- Networking, topology, discovery, routing
- SECURITY
- Attestation, cryptographic verification, hardware proofs
- TOKENOMICS
- Reward models, incentive structures (framework, not dogmatic)
Active specifications
| ID | Title | Status | Version | Published | Category |
|---|---|---|---|---|---|
| PAG-001 | Core Runtime Specification | FINAL | 1.0 | 2026-05-01 | CORE |
| PAG-002 | MESH Protocol Definition (forthcoming) | PROPOSED | 0.2 | — | MESH |
| PAG-003 | COMPUTE Orchestration Model (forthcoming) | DRAFT | 0.1 | — | COMPUTE |
| PAG-004 | Proof-of-Physical-Work Verification (forthcoming) | EXPERIMENTAL | 0.1 | — | SECURITY |
Errata for FINAL specs are listed under specs/errata in the repository. Normative changes after FINAL always arrive as a new PAG or an errata note — never silent edits to published files.