Skip to content

Latest commit

 

History

182 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Overview

The clade-index is the central registry for the entire hyperpolymath ecosystem. It provides a VeriSimDB-backed taxonomy of 200+ repositories organised into 12 clades, with a pointer authority system for tracking data ownership, and VCL queries for dashboards, drift detection, and work tracking.

Map and territory: This registry is the map — queryable, presentable, always clean. Repositories are the territory. Editing the map never damages the territory.

Clade Taxonomy

Code Clade Description

fv

Formal Verification & Proofs

Provable correctness, reversibility, dependent types

nl

Nextgen Languages

Compilers, runtimes, language tooling

rm

Repo Management & Tooling

Scaffolding, graph analysis, bot orchestration

gv

Governance & Standards

Licensing, compliance, policy enforcement

db

Databases

Database engines, query languages

ap

Applications

End-user apps, web, desktop, services

ix

Infrastructure & Cloud

Containers, deployment, sysadmin

dx

Developer Ecosystem

Dev tools, editor integrations, bindings

pt

Protocols & Interop

Internet standards, protocol implementations

ax

AI & Neurosymbolic

ML, neural proof synthesis, AI governance

gm

Games & Interactive

Game engines, interactive experiences

sc

Security

Scanning, vulnerability management, access control

Structure

chora-registry/
├── 0-AI-MANIFEST.deed           # AI agent entry point (pointer-only)
├── chora-registry_chora.deed    # This repo's deed: identity, clade, agentic, ...
├── .machine_readable/           # descriptiles/STATE.deed (status), contractiles
├── verisim/
│   ├── config.a2ml              # VeriSimDB instance config
│   ├── schema/                  # VCL schemas (7 entity types)
│   │   ├── repo.vcl             # Repository octad
│   │   ├── clade.vcl            # Clade definition
│   │   ├── todo.vcl             # Work items
│   │   ├── observation.vcl      # Bot/agent findings
│   │   ├── feedback.vcl         # External feedback
│   │   ├── lineage.vcl          # Inflate/deflate history
│   │   └── forge-identity.vcl   # PK/FK forge mapping
│   ├── seed/                    # Initial data
│   │   ├── clades.a2ml          # 12 clade definitions
│   │   ├── chora-registry_praxis.deed  # the repo register (seed deed)
│   │   └── forges.a2ml          # Forge account definitions
│   └── queries/                 # Pre-built VCL queries
│       ├── dashboard.vcl        # Ecosystem overview
│       ├── stale.vcl            # Inactive repos
│       ├── orphans.vcl          # Unclassified repos
│       ├── drift.vcl            # State divergence
│       ├── bot-findings.vcl     # Unacknowledged bot observations
│       ├── blocked.vcl          # Blocked work items
│       ├── cross-clade-deps.vcl # Cross-boundary dependencies
│       └── feedback-status.vcl  # Feedback resolution tracking
├── sync/                        # Sync tooling (Phase 2)
└── views/                       # Generated outputs (not committed)

The three .a2ml files left under verisim/ are registry data that wait for their own mapping specs. Every other .a2ml file was retired on 2026-11-14 (docs/history/A2ML-REMOVED.adoc).

Portal Architecture

hyperpolymath.github.io          Cloudflare Worker         VeriSimDB (VPS)
(ReScript/WASM)            -->   (API Gateway)       -->   (Rust + Elixir)
                                                              |
Public read --------------------------------------------------> KV snapshot
LLM query  ------------------- API key ---------------------> Read-only
Contributor ------------------ OAuth -----------------------> Scoped access
Bot writes ------------------- Signed JWT ------------------> Write observations

Identity Model

Every repo has:

  • Primary key: GitHub (gh:hyperpolymath/{name})

  • Foreign keys: GitLab, Bitbucket, Codeberg, SourceHut mirrors

  • UUID: uuid is the deterministic UUIDv5 of github.com/{owner}/{name} in the @url namespace, as /v1 has always served it. uuid_v8 is the ADR-008 profile C UUIDv8 of the same name in the gv-clade-index domain, the id a deed writes as #u8"gv-clade-index:github.com/{owner}/{name}". It is added beside uuid because /v1 is additive-only (docs/decisions/0004-api-versioning.adoc); /v2 makes it the uuid.

  • Clade: Primary (1) + secondary (0+)

  • Lineage: standalone, monorepo, monorepo-child, inflated, deflated, hub, satellite

Pointer Authority

Every cached value in VeriSimDB declares its canonical source:

  • pointer — value lives in the repo (VeriSimDB caches
    drift-detects)

  • local — VeriSimDB owns it (TODOs, bot observations)

  • derived — computed from other values (clade health scores)

Clade placements

A repo’s clade placement is an identity fact in its own chora deed (<repo>_chora.deed, the (clade …) clause), checked against this registry’s scheme clade-12, which is authoritative (owner ruling W10). The old clade-hygiene.a2ml contractile, which required every repo to carry a CLADE.a2ml, was retired with A2ML (docs/history/A2ML-REMOVED.adoc).

Implementation Phases

Phase Deliverable Status

0

Clade taxonomy, repo seed, VCL schema

Complete

1

Deploy CLADE.a2ml to all 200 repos

Withdrawn (A2ML retired; see the release runbook)

2

VeriSimDB instance on VPS

Pending

3

Cloudflare Worker API (hardened, tested, CI-gated)

In progress (~60%)

4

ReScript/typed-WASM portal

Pending

5

LLM query endpoint

Pending

6

Bot write endpoints

Pending

7

Contributor OAuth

Pending

8

Repo lockdown

Pending

Rollout operations — timelines, dependencies, ownership and go/no-go gates for each phase — live in docs/governance/RELEASE-RUNBOOK.adoc; this table is the summary, the runbook is the procedure, and ROADMAP.adoc tracks progress. The lifecycle status is .machine_readable/descriptiles/STATE.deed.

License

MPL-2