Hyperpolymath Standards

Organization-wide standards, specifications, and governance templates for the Hyperpolymath ecosystem.

Overview

This repository serves as the canonical source for policies, templates, and specifications governing all Hyperpolymath projects. It provides:

• Language Policy — Which languages and tools are permitted across the ecosystem

• SCM Format Family — 7 machine-readable project metadata formats (see SATELLITES.scm)

• Build System — Mustfile/justfile (no Makefiles)

• Governance Templates — Reusable CODE_OF_CONDUCT, CONTRIBUTING, and SECURITY documents

• Licensing Framework — PMPL-1.0-or-later with Palimpsest philosophical principles

• Enforcement — CI/CD workflows and pre-commit hooks

Standards Ecosystem

Monorepo Architecture

As of 2026-02-08, all SCM specification satellites have been absorbed into this monorepo as subdirectories. The previous hub-satellite architecture (with separate GitHub repos) has been consolidated here for easier maintenance and atomic cross-spec changes.

Each satellite retains its own README, spec documents, examples, and .machine_readable/ metadata. RSR boilerplate (LICENSE, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, MAINTAINERS) is inherited from the monorepo root.

Subdirectory	Former Repository	Content
meta-scm/	meta-scm	META.scm, STATE.scm, ECOSYSTEM.scm specs, ABNF, IANA registration
playbook-scm/	playbook-scm	PLAYBOOK.scm spec
agentic-scm/	agentic-scm	AGENTIC.scm spec, contractiles, Nickel configs
neurosym-scm/	neurosym-scm	NEUROSYM.scm spec, Nickel configs
anchor-scm/	anchor-scm	ANCHOR.scm spec, contractiles
state-scm/	state.scm	STATE.scm spec, Guile library, ABNF, IANA registration
ecosystem-scm/	ecosystem.scm	ECOSYSTEM.scm spec, ABNF, IANA considerations
standards-update/	standards-update	Standards update tooling and documentation

Satellite registry is still machine-readable in SATELLITES.scm.

For detailed repository structure requirements, see SCM-REPO-TEMPLATE.adoc.

SCM Format Family (7 Formats)

Every Hyperpolymath repository must include these machine-readable Scheme files in .machine_readable/:

File	Tier	Purpose	Specification
META.scm	Primary	Architecture decisions (ADRs), development practices	meta-scm
STATE.scm	Primary	Project state, phase, milestones, session history	state-scm
ECOSYSTEM.scm	Primary	Ecosystem positioning, related projects	state-scm
PLAYBOOK.scm	Execution	Executable plans, procedures, alerts	playbook-scm
AGENTIC.scm	Execution	AI agent operational gating, entropy budgets	agentic-scm
NEUROSYM.scm	Execution	Symbolic semantics, proof obligations	neurosym-scm
ANCHOR.scm	Intervention	Project recalibration/realignment	anchor-scm

Templates available in scm-templates/ directory.

Execution Pipeline

All implementations MUST respect this ordering (defined in SATELLITES.scm):

1. META validation      ← Constitutional authority check
2. AGENTIC gating       ← Operational safety
3. NEUROSYM semantics   ← Proof obligations
4. PLAYBOOK derivation  ← Build executable plan
5. Execution
6. ECOSYSTEM check      ← Integrity verification
7. STATE update         ← Record outcome

INTERVENTION: ANCHOR.scm can override any level

RSR (Rhodium Standard Repository)

The Rhodium Standard Repository specification defines compliance requirements:

Repository	Purpose
rhodium-standard-repositories	RSR specification and compliance criteria
git-rsr-certified	Universal RSR compliance engine
rsr-template-repo	Template repository for RSR compliance
rhodium-pipeline	CI/CD pipeline for RSR enforcement

Document Formats

• a2ml — Attested Markup Language (typed, verified documents) (application/vnd.a2ml, v0.6.0 draft)

• k9-svc — Self-validating components (embedded contracts + deployment logic)

• stateful-artefacts-for-gitforges — Metadata-driven documentation pipeline

Palimpsest

Philosophical licensing overlay for consent-based digital interaction:

• palimpsest-license — Core license framework

Principles:

• Consent-based digital interaction — Explicit permission for data use

• Transparent AI training practices — Opt-in rather than opt-out

• Preservation of metadata and attribution — Maintaining creative lineage

• Protection of narrative intent — Respecting cultural context

Mustfile Build System

All repositories use Mustfile/justfile instead of Makefiles:

• mustfile — Canonical build system

Required files:

• Mustfile — Mandatory checks definition

• justfile — Build recipes (Just)

• mustfile.toml — Configuration (optional)

Language Policy

The Hyperpolymath Language Policy defines the technology stack permitted across all projects:

Category	Allowed	Banned
Primary Languages	ReScript, Rust, Gleam	TypeScript, Go, Java/Kotlin, Python
Runtime	Deno	Node.js, npm, Bun, pnpm, yarn
Mobile	Tauri 2.0+, Dioxus	React Native, Flutter/Dart, Swift, Kotlin
Config	Nickel, Guile Scheme	—
Build	Mustfile, justfile	Makefiles
Special Purpose	Julia (batch), OCaml (AffineScript), Ada (safety-critical)	—

Rationale: Preference for FOSS tools with independent governance (no Big Tech dependencies), type safety, and Rust-first mobile development.

Note	Python is fully banned. The previous SaltStack exception has been removed.

Enforcement

CI/CD Workflows

Copy these workflows to .github/workflows/ in your repository:

• language-policy.yml — Blocks banned languages

• makefile-blocker.yml — Blocks any Makefile changes

• doc-format.yml — Enforces AsciiDoc documentation

Pre-commit Hook

Install the pre-commit hook for local enforcement:

cp hooks/pre-commit .git/hooks/pre-commit
chmod +x .git/hooks/pre-commit

The hook checks for:

• Banned file types (TypeScript, Go, Python, Java, Kotlin, Swift)

• Makefiles

• Missing SPDX headers

Documentation Policy

All documentation must be AsciiDoc (.adoc) except for GitHub-required files:

Must be .md (GitHub community health):

• SECURITY.md

• CONTRIBUTING.md (can redirect to .adoc)

• CODE_OF_CONDUCT.md

• CHANGELOG.md

Must be .adoc:

• README.adoc

• ARCHITECTURE.adoc

• ROADMAP.adoc

• PHILOSOPHY.adoc

• All other documentation

Other required formats:

• LICENSE.txt

• .github/FUNDING.yml

Repository Structure

standards/
├── .claude/
│   └── CLAUDE.md              # Language policy
├── .github/
│   ├── ISSUE_TEMPLATE/        # Bug, feature, docs, question templates
│   ├── workflows/             # CI/CD enforcement workflows
│   │   ├── language-policy.yml
│   │   ├── makefile-blocker.yml
│   │   ├── doc-format.yml
│   │   └── ...
│   ├── FUNDING.yml
│   └── dependabot.yml
├── hooks/                     # Git hooks
│   ├── pre-commit             # Language policy enforcement
│   └── validate-*.sh          # Validation scripts
├── scm-templates/             # SCM file templates
│   ├── STATE.scm.template
│   ├── META.scm.template
│   ├── ECOSYSTEM.scm.template
│   ├── AGENTIC.scm.template
│   ├── NEUROSYM.scm.template
│   ├── PLAYBOOK.scm.template
│   └── ANCHOR.scm.template
├── meta-scm/                  # META.scm specification (absorbed satellite)
│   ├── README.adoc
│   ├── spec/
│   └── examples/
├── playbook-scm/              # PLAYBOOK.scm specification
│   ├── README.adoc
│   ├── spec/
│   └── examples/
├── agentic-scm/               # AGENTIC.scm specification
│   ├── README.adoc
│   ├── spec/
│   ├── examples/
│   ├── contractiles/
│   └── ncl/
├── neurosym-scm/              # NEUROSYM.scm specification
│   ├── README.adoc
│   ├── spec/
│   ├── examples/
│   └── ncl/
├── anchor-scm/                # ANCHOR.scm specification
│   ├── README.adoc
│   ├── spec/
│   ├── examples/
│   └── contractiles/
├── state-scm/                 # STATE.scm specification
│   ├── README.adoc
│   ├── spec/
│   ├── examples/
│   └── lib/
├── ecosystem-scm/             # ECOSYSTEM.scm specification
│   ├── README.adoc
│   ├── spec/
│   └── docs/
├── standards-update/          # Standards update tooling
│   └── README.adoc
├── SATELLITES.scm             # Hub-satellite registry (machine-readable)
├── SCM-REPO-TEMPLATE.adoc     # Canonical structure for -scm repos
├── CODE_OF_CONDUCT.md         # Template
├── CONTRIBUTING.md            # Template
├── SECURITY.md                # Template
├── LICENSE.txt                # PMPL-1.0-or-later + Palimpsest
├── ROADMAP.adoc
└── README.adoc                # This file

Usage

For New Hyperpolymath Projects

1. Copy governance templates to your repository

2. Create .machine_readable/ with 6 SCM files from templates

3. Add Mustfile and justfile (from hyperpolymath/mustfile)

4. Add enforcement workflows to .github/workflows/

5. Install pre-commit hook

6. Add language policy to .claude/CLAUDE.md

For Contributors

• Read the Language Policy before proposing code

• No TypeScript, Go, Python, Java, Kotlin, Swift, or Makefiles

• All source files must have SPDX headers

• Follow the template in CONTRIBUTING.md for your project

Related Projects

Standards Monorepo (this repository):

• SATELLITES.scm — Machine-readable satellite registry

SCM Format Family (local subdirectories):

• meta-scm — META.scm, STATE.scm, ECOSYSTEM.scm (primary tier)

• playbook-scm — PLAYBOOK.scm (execution tier)

• agentic-scm — AGENTIC.scm (execution tier)

• neurosym-scm — NEUROSYM.scm (execution tier)

• anchor-scm — ANCHOR.scm (intervention tier)

• state-scm — STATE.scm (primary tier)

• ecosystem-scm — ECOSYSTEM.scm (primary tier)

• standards-update — Standards update tooling

RSR/Rhodium:

• rhodium-standard-repositories

• git-rsr-certified

• rsr-template-repo

• rhodium-pipeline

Build & Licensing:

• mustfile — Build system standard

• palimpsest-license — Licensing framework

License

PMPL-1.0-or-later with Palimpsest philosophical overlay.

See LICENSE for full terms.

Contributing

This is a standards repository. To propose changes:

1. Open a Discussion for major policy changes

2. Submit an Issue for template improvements

3. PRs welcome for typos, clarifications, and infrastructure fixes

---

Canonical standards for the Hyperpolymath ecosystem.

Architecture

See TOPOLOGY.md for a visual architecture map and completion dashboard.