Skip to content

ROADMAP.adoc

Latest commit

 

History

History
265 lines (190 loc) · 10.4 KB

ROADMAP.adoc

File metadata and controls

265 lines (190 loc) · 10.4 KB
Raw

Hyperpolymath Standards Roadmap

Table of Contents

Development roadmap for the Hyperpolymath standards and specifications repository.

Current State (2026-05-28)

Core Standards — Complete

Component Description Status

Language Policy (CCCP)

Comprehensive allowed/banned language specification

Complete

License

MPL-2.0 (see LICENSE; licence/SPDX is owner-managed, Manual-Only)

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

ARG/FRG Language-Maturation Framework

Adoption Readiness Grades (adoption-readiness-grades/) + Foundations Readiness Grades (foundations-readiness-grades/); TRG/CRG per-language profile templates; aggregated into nextgen-languages dashboard

Complete (2026-05-28, PRs #229 + #232)

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 Specifications

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)

Planned Development

Phase A: Innervation Architecture (NEW — 2026-04)

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, @grade annotations 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

Phase B: Evidence & Observability

  • ❏ 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

Phase C: Ecosystem-Wide Visibility

  • ❏ 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

Phase D: Maturity

  • ❏ Full release terminology — Reserve "full release" for best-practice-complete projects

  • ❏ Mature-phase policy — When a project moves from stable to mature standing

  • ❏ Best-practice completion rubric — Proof rigor + testing depth + observability + telemetry + provenance

Conceptual Work

Palimpsest License Development

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

Language Policy Evolution

  • WebAssembly guidelines — WASM compilation targets and toolchains

  • Database preferences — VeriSimDB primary; SQLite, PostgreSQL where needed

  • Protocol specifications — Preferred serialization (MessagePack, Protobuf)

  • Testing frameworks — Approved testing tools per language

TypeScript → AffineScript Estate Migration (IN-FLIGHT 2026-05-28)

Multi-session estate-wide migration of TypeScript to AffineScript, parallel to the completed V→Zig sweep (2026-05-28) but at very different scale (~50-80 PRs across ~38 repos vs V→Zig’s 16-PR single session).

Campaign umbrella: #239

4-layer architecture

Layer Description Status

Layer 1 — Policy & enforcement

hypatia :typescript_detected rule + path_allow_prefixes (9 carve-out classes); standards .claude/CLAUDE.md exemption table; LANGUAGE-POLICY.adoc Banned TS row; language-policy.yml CI gate. Layer-1 PRs: hypatia#375, hypatia#378, standards#235, standards#238, reposystem#82.

Complete

Layer 2 — Stdlib binding capacity

AffineScript stdlib must cover the host surface each port needs. Exists today: Deno.affine (readTextFile/writeTextFile/readDirNames/path), json.affine v0.3 (Json sum type + Zig FFI parse), Vscode.affine (55 fns), VscodeLanguageClient.affine. Known gaps: recursive walk, regex, Set, general Map<K,V>, Date.toISOString, WebExt/WP-admin/Zotero APIs.

Partial (step 3 discharges as ports surface gaps)

Layer 3 — Physical file ports

~285 estate-authored .ts/.tsx files across 38 repos (post-carve-out). Unblocked: ~215 / ~30 repos. Plugin-host-blocked: ~70 / 5 repos. Each port is a non-trivial rewrite, not a shim swap.

In flight

Layer 4 — Parallel dependency: AS bindings top-50 roadmap

Plugin-host APIs (WebExtensions, WP-admin, Zotero, MailExt) must be bound in affinescript/stdlib/ before the corresponding plugin repos can migrate. Tracked separately at project_affinescript_bindings_top50_roadmap.

Multi-week parallel

Step ordering (value-per-effort)

Step Description Issue

①

SEED PORT — phronesis 54L VSCode extension to .affine (binding coverage confirmed)

#240

②

TAIL BATCH 1 — pure-logic small repos (≤3 files each)

#241

③

STDLIB FILL — discharge gaps surfaced by step 2

#242

④

TAIL BATCH 2 — 4-9 file mid-tier repos

#243

⑤

IDAPTIK DLC PORT — 52 files (VM/instruction core)

#244

⑥

PLUGIN-HOST BINDINGS — cross-ref AS top-50 roadmap

#245

⑦

PLUGIN REPOS — 5 repos / 70 files (post step 6)

#246

Dependency graph

step 1 (seed)
  └─→ step 2 (tail batch 1) ──→ step 3 (stdlib fill) ──→ step 4 (tail batch 2)
                                                          └─→ step 5 (idaptik)
step 6 (host bindings, parallel) ──→ step 7 (plugin repos)

Cross-references

  • GitHub Projects board: Hyperpolymath Master Roadmap — all 8 campaign issues (#239 umbrella + #240–#246 steps) added with Status/Gate/Priority/Owner fields configured

  • Memory tracker: project_estate_ts_to_affinescript_2026_05_28.md

  • AS bindings parallel: project_affinescript_bindings_top50_roadmap.md

  • V-lang precedent (completed 2026-05-28): project_estate_vlang_remediation_2026_05_28.md

Scope safety

Every per-repo PR runs the pre-PR ownership gate (gh repo view hyperpolymath/<repo> --json owner,isFork,parent → owner=hyperpolymath, isFork=false, parent=null). Upstream forks and archived repos are carve-outs in the hypatia rule and never touched.

Non-Goals

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