Development roadmap for the Hyperpolymath standards and specifications repository.
| Component | Description | Status |
|---|---|---|
Language Policy (CCCP) |
Comprehensive allowed/banned language specification |
Complete |
License Framework |
PMPL-1.0-or-later with Palimpsest philosophical overlay |
Complete |
A2ML Format Family (7) |
STATE, META, ECOSYSTEM, AGENTIC, NEUROSYM, PLAYBOOK, ANCHOR |
Complete (migration to innervation model planned) |
RSR Compliance Framework |
Rhodium Standard Repositories — quality tiers |
Complete |
CRG Grading System |
Component Readiness Grades (X, F, E, D, C, B, A) |
Complete |
K9 Self-Validating Components |
Must/Trust/Dust validation + deployment in single file |
Complete |
K9 Coordination Protocol |
Universal AI agent coordination standard |
Complete (Phase 1: Defensive) |
Contractile System |
Must/Trust/Dust/Intent/ADJUST semantics |
Complete |
Governance Templates |
CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, GOVERNANCE |
Complete |
Issue Templates |
Bug report, feature request, documentation, question |
Complete |
Forge Sync |
Instant propagation workflow to multiple forges |
Complete |
Security Scanning |
CodeQL, secret scanning, Scorecard, TruffleHog |
Complete |
Build System |
Justfile, Mustfile, flake.nix, guix.scm, .editorconfig |
Complete |
CHANGELOG Templates |
Keep a Changelog format across sub-projects |
Complete |
| Protocol | Description | Status |
|---|---|---|
Groove Protocol |
Universal plug-and-play inter-service communication |
WIP (spec stable, reference impls needed) |
AVOW Protocol |
Cryptographic spam prevention, consent management |
Draft (spec complete, 0 tests) |
AXEL Protocol |
Age-gating and explicit enforcement |
Beta (14 tests) |
Consent-Aware HTTP |
Multi-protocol AI usage boundaries, HTTP 430 |
Draft (IETF Internet-Draft) |
Overlay Protocol |
Library overlay/extension system |
Spec only (sparse implementation) |
AI Gatekeeper Protocol |
AI manifest enforcement (0-AI-MANIFEST.a2ml) |
Production-ready (65 tests) |
LOL Corpus |
1500+ language corpus crawler for NLP |
Active (multi-suite tests) |
The 6a2 file-per-repo model served well for 2025. With VeriSimDB, Hypatia, ECHIDNA, K9, PanLL, and Groove now operational, the standards system shifts from static files to a nervous system that innervates every repo.
-
❏ Inline annotation format —
@trust,@contract,@gradeannotations in code comments, machine-parseable by Hypatia, indexable by VeriSimDB, visible in PanLL -
❏ coordination.k9 receptor spec — Single per-repo file declaring afferent (what it emits), efferent (what it responds to), and reflex (local invariant guards)
-
❏ Groove signal schema — Event bus for code change → index → detect drift → fix → re-index cycle
-
❏ VeriSimDB ecosystem ingest — Absorb ECOSYSTEM.a2ml data into Graph modality; derive relationships from actual imports
-
❏ Hypatia playbook converter — PLAYBOOK.a2ml → executable Hypatia recipes
-
❏ STATE.a2ml v2 — Thin journal format (phase + blockers + last action only); most state derived from VeriSimDB
-
❏ k9 init migration tool — Generate coordination.k9 from existing 6a2 files
-
❏ Self-scan workflow — Hypatia dogfooding on this repo (hypatia-scan.yml)
-
❏ ECHIDNA proof gate — CI verification of all Agda/Idris2 proofs in this repo
-
❏ CRG self-assessment — Standards repo grades itself with computed evidence
-
❏ Release telemetry standard — Rollout health, adoption, regression signals per release
-
❏ Automatic evidence capture — Tests, benchmarks, proofs, audits recorded as VeriSimDB octads
-
❏ Claim-to-artifact traceability — Machine-readable mapping from claims to proof files/tests
-
❏ Provenance and attestation standard — Signed, reproducible provenance for releases
-
❏ Automated stable-claim demotion — Tooling that retracts claims when audits fail
-
❏ Evidence retention policy — How long evidence must remain available
-
❏ PanLL CRG Dashboard — Component × Grade matrix with evidence links, powered by VeriSimDB
-
❏ PanLL Standards Compliance Monitor — 290+ repo heatmap vs CRG coverage
-
❏ PanLL Proof Verification Hub — Trust topology, proof coverage, axiom usage
-
❏ Cross-repo release dashboard — Weakest in-scope repo visible before shipment
-
❏ Estate-wide release registry — Canonical draft/alpha/beta/rc/stable/mature view
The Palimpsest philosophical overlay represents ongoing work on:
-
Consent-based data use — Framework for explicit permission in digital contexts
-
AI training transparency — Standards for disclosing training data sources
-
Attribution preservation — Technical and legal mechanisms for creative lineage
-
Narrative intent protection — Safeguarding cultural and contextual meaning
This repository does not aim to provide:
-
Project-specific configurations
-
Runtime dependencies
-
Opinionated application architectures
|
Note
|
The "standards only, no code" non-goal has been superseded — this repo now contains reference implementations, bindings, and tooling alongside specifications. |
Last updated: 2026-04-04