Skip to content

hyperpolymath/standards

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

39 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Hyperpolymath Standards

MPL-2.0 Palimpsest

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 — AGPL-3.0-or-later with Palimpsest philosophical principles

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

Standards Ecosystem

Hub-Satellite Architecture

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.

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

Companion to META

ECOSYSTEM.scm

Primary

Ecosystem positioning, related projects

Companion to META

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

Palimpsest

Philosophical licensing overlay for consent-based digital interaction:

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:

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
├── 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

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

Standards Hub:

SCM Format Family (Satellites):

RSR/Rhodium:

Build & Licensing:

License

AGPL-3.0-or-later with Palimpsest philosophical overlay.

See LICENSE.txt 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.

Sponsor this project

Packages

No packages published

Contributors 3

  •  
  •  
  •