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 — AGPL-3.0-or-later with Palimpsest philosophical principles
-
Enforcement — CI/CD workflows and pre-commit hooks
This repository is the hub for the SCM Format Family. All specification repos are satellites registered in SATELLITES.scm.
For detailed repository structure requirements, see SCM-REPO-TEMPLATE.adoc.
Every Hyperpolymath repository must include these machine-readable Scheme files in .machine_readable/:
| File | Tier | Purpose | Specification |
|---|---|---|---|
|
Primary |
Architecture decisions (ADRs), development practices |
|
|
Primary |
Project state, phase, milestones, session history |
Companion to META |
|
Primary |
Ecosystem positioning, related projects |
Companion to META |
|
Execution |
Executable plans, procedures, alerts |
|
|
Execution |
AI agent operational gating, entropy budgets |
|
|
Execution |
Symbolic semantics, proof obligations |
|
|
Intervention |
Project recalibration/realignment |
Templates available in scm-templates/ directory.
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 levelThe Rhodium Standard Repository specification defines compliance requirements:
| Repository | Purpose |
|---|---|
RSR specification and compliance criteria |
|
Universal RSR compliance engine |
|
Template repository for RSR compliance |
|
CI/CD pipeline for RSR enforcement |
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
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. |
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
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
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
├── 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 # AGPL-3.0-or-later + Palimpsest
├── ROADMAP.adoc
└── README.adoc # This file-
Copy governance templates to your repository
-
Create
.machine_readable/with 6 SCM files from templates -
Add
Mustfileandjustfile(from hyperpolymath/mustfile) -
Add enforcement workflows to
.github/workflows/ -
Install pre-commit hook
-
Add language policy to
.claude/CLAUDE.md
-
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.mdfor your project
Standards Hub:
-
standards — This repository (hub)
-
SATELLITES.scm — Machine-readable satellite registry
SCM Format Family (Satellites):
-
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)
RSR/Rhodium:
Build & Licensing:
-
mustfile — Build system standard
-
palimpsest-licence — Licensing framework
AGPL-3.0-or-later with Palimpsest philosophical overlay.
See LICENSE.txt for full terms.