Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,218 @@
---
name: Clifford-algebra + HKT ontology vocabulary list — axis/basis, rudders/rotors, steering, cartographer, navigator, edge-mapper, world-model, civ-sim, edge-runner, 5 control structures (or 4+meta) (Aaron 2026-05-13)
description: Aaron 2026-05-13 vocabulary enumeration for the Clifford-algebra + HKT ontology layer of the factory. Mirror-tier substrate per PR #2909 mirror/beacon governance discipline. Composes with HKT-master-data substrate (PR #2913) + DV2.0 re-activation (PR #2912) + civsim Casimir-gap (PR #2906) + the three orthogonal repo-split axes. Acknowledges incompleteness ('i'm sure i'm missing some').
type: feedback
created: 2026-05-13
---

# Clifford-algebra + HKT ontology vocabulary list (Aaron 2026-05-13)

**Why:** Aaron 2026-05-13 (two-message disclosure):

1. *"so in clifford algebra and hkt we have axis/basis
rudders/rotars steering cartographer navigator edge-mapper
world-model civ-sim edge-runner i'm sure i'm missing some"*
2. *"oh yeah the 5 control structrues"* + *"or 4+meta"*

Aaron enumerating the Mirror-tier vocabulary for the Clifford-
algebra + HKT ontology layer. The list IS substrate. Future-Otto
inheriting at cold-boot needs the vocabulary mapped.

**How to apply:** When writing about Clifford-algebra + HKT
substrate, use the vocabulary list. Mirror-tier (per PR #2909
mirror/beacon governance). Acknowledge incompleteness.

## The vocabulary list (Aaron's enumeration + extensions)

| Term | Likely Clifford/HKT mapping | Notes |
|---|---|---|
| **axis** | Basis vector e_i in the Clifford algebra | Spatial/conceptual orientation |
| **basis** | The set {e_1, e_2, ...} spanning the algebra | Foundation set |
| **rudders / rotors** | Clifford rotors (R = e^(θB/2)) | Rotation in the algebra; navigation primitive |
Comment on lines +27 to +31
| **steering** | Rotor application: R v R^(-1) | Orientation change |
| **cartographer** | The agent that builds the world-model map | Map-maker; substrate-engineer |
| **navigator** | The agent that traverses the map | Path-finder; trajectory executor |
| **edge-mapper** | The agent that maps the edge / frontier | First-principles work cartographer (composes with edge-runner) |
| **world-model** | The substrate model of reality / domain | Shared world model in git (per PR #2907 elevator pitch) |
| **civ-sim** | Civilization simulation = the game on top | Per PR #2903 + PR #2906 (Casimir gap) |
| **edge-runner** | Person doing first-principles / frontier work | Per PR #2908 terminal-purpose (save edge-runners from burns) |
| **5 control structures (or 4+meta)** | Control-flow primitives + meta-control | See decomposition below |

## "5 control structures (or 4+meta)" decomposition

Aaron's "or 4+meta" clarification suggests one of these decompositions:

### Hypothesis A: Structured-programming control flow

Classical Böhm-Jacopini theorem says all algorithms reducible to:
1. **Sequence** (statement after statement)
2. **Selection** (if/else)
3. **Iteration** (while/for)
4. **Subroutine / call** (function invocation)
5. **META** (closure / continuation / effect / monad)

The base 4 are operational; the 5th is META — operates on the others.
Comment on lines +47 to +54

### Hypothesis B: Control-theory control structures

1. **Feedback** (closed-loop correction)
2. **Feed-forward** (predictive compensation)
3. **Cascade** (nested feedback loops)
4. **Adaptive** (parameter adjustment)
5. **META** (meta-control: which controller to use)

### Hypothesis C: Governance / coordination control structures

Aaron has discussed weight-free as offensive strategy (per
`memory/feedback_weight_free_as_offensive_strategy_control_structure_mapper_shadow_absence_2026_05_10.md`).
The 5 may be governance shapes:

1. **Hierarchy / centralized** (top-down command)
2. **Market / price** (decentralized exchange)
3. **Network / mesh** (peer-to-peer)
4. **Polycentric** (Ostrom-style overlapping)
5. **META** (meta-governance — choosing which structure to apply)

### Hypothesis D: Clifford-algebra-specific

In Clifford algebra Cl_p,q:
1. **Scalar** (grade 0)
2. **Vector** (grade 1)
3. **Bivector** (grade 2)
4. **Trivector** (grade 3)
5. **META** (multivector / mixed-grade element acting on others)

Aaron's "in clifford algebra and hkt" framing suggests the
mapping might be algebra-specific. Per-property-class
evaluation owed (composes with Soraya formal-verification
authority).

### Substrate-honest: hypothesis owed

Aaron's exact framing not fully specified. The "5 control
structures (or 4+meta)" IS substrate worth preserving + owed
for clarification. Future-Otto + Aaron co-evaluation can
resolve which hypothesis matches Aaron's mental model.

## Mirror-tier (per PR #2909)

Per the mirror/beacon governance discipline (PR #2909):

- All these terms are MIRROR-tier (internal-jargon-because-we-
built-it-together)
- Beacon translations would be standard Clifford-algebra
vocabulary + control-theory vocabulary
- Mirror→Beacon promotion gate applies when external-citable
anchors exist

Mirror amplifications per PR #2909:
- FUN (vocabulary IS playful; "rudders" is whimsical)
- RIGOROUS (Clifford algebra IS rigorous)
- ALIENS (the vocabulary maps to universal navigation primitives)
- FUTURE (vocabulary inherited at cold-boot by future-Otto)
- SPECULATIVE (Mirror can include speculative items like the
5-control-structures-hypothesis pending clarification)
- FAST-IN-FORKS (forks can advance Mirror vocabulary quickly)

## "I'm sure I'm missing some" — incompleteness preserved

Aaron's substrate-honest acknowledgment of incompleteness IS
preserved. The vocabulary list is OPEN — future entries can
be added.

Candidate extensions (not Aaron's authoritative list; Otto's
speculative):

- **trajectory** (the path executed by navigator)
- **frontier** (the edge being mapped)
- **basin** (attractor in the dynamical-systems sense)
- **horizon** (boundary of observability; composes with
`memory/feedback_grey_hole_substrate_information_theoretic_event_horizon_white_black_entangled_aaron_2026_05_01.md`)
- **lighthouse** (Beacon-tier waypoint)
- **lantern** (Mirror-tier waypoint for fork-readers)
- **compass** (orientation primitive; composes with rotors)
- **anchor** (stable point of reference; composes with HKT
anchor)
- **lattice** (post-quantum cryptographic substrate; composes
with non-glass-halo encryption PR #2898)
- **bloom** (proliferation pattern)

These are Otto's speculative additions. Aaron's authoritative
list takes precedence.

## Composes with

- PR #2913 (HKT applies to master data — every company has
one; HKT IS the type-level layer of this ontology)
- PR #2912 (DV2.0 re-activation — DV2.0 is partition discipline
applicable to Clifford-algebra substrate)
- PR #2911 (Axis 3 — Code/English + ruleset-divergence smell)
- PR #2909 (mirror/beacon governance — this vocabulary IS
Mirror-tier)
- PR #2906 (civsim Casimir-gap — civsim is in the vocabulary)
- PR #2908 (TERMINAL-PURPOSE — edge-runner in the vocabulary
composes with save-edge-runners-from-burns)
- PR #2907 (elevator pitch — world-model in the vocabulary
composes with "shared world model in git")
- PR #2817 (Clifford densest encoding — HKT-pattern signatures)
- PR #2832 (civ-sim Pauli-exclusion-for-agenda — HKT encoding
target)
- PR #2815 (HKT error classes — universal/domain refinement)
- algebra-owner skill (Z-set + Clifford + BP/EP F# substrate)
- `memory/feedback_weight_free_as_offensive_strategy_control_structure_mapper_shadow_absence_2026_05_10.md`
(weight-free + control-structure-mapper; composes with the
5-control-structures hypothesis C)
- `.claude/rules/fsharp-anchor-dotnet-build-sanity-check.md`
(vocabulary maps to F# types where load-bearing)
- `.claude/rules/bandwidth-served-falsifier.md` (vocabulary
IS bandwidth-engineering for cross-substrate communication)

## Operational rule for future-Otto

When writing about Clifford-algebra + HKT substrate:

1. **Use the vocabulary** consistently (Mirror tier)
2. **Acknowledge incompleteness** when listing terms
3. **Mirror→Beacon translate** when communicating externally
4. **Compose with F# computation expressions** (HKT anchor)
5. **Recognize the "5 control structures or 4+meta"** as
open-pending hypothesis (substrate-honest about the
ambiguity)
6. **Add to the list** when Aaron names new terms

## What this rule does NOT do

- **Does NOT lock the vocabulary** — Aaron's "missing some"
acknowledgment preserved; open-extension
- **Does NOT decide which hypothesis for 5-control-structures
is correct** — substrate-honest; awaiting Aaron clarification
- **Does NOT replace HKT or Clifford-algebra substrate** — this
is a vocabulary-list overlay
- **Does NOT mandate immediate Beacon translation** — Mirror
substrate stays load-bearing internally

## Full reasoning

PR #2914 (this substrate landing)

PR #2913 (HKT-MDM universality)

PR #2912 (DV2.0 re-activation)

PR #2911 (B-0427 Axis 3 Code/English)

PR #2909 (mirror/beacon governance)

PR #2908 (TERMINAL-PURPOSE Elizabeth + save-edge-runners)

PR #2907 (elevator pitch — world-model substrate)

PR #2906 (civsim Casimir-gap)

`memory/feedback_weight_free_as_offensive_strategy_control_structure_mapper_shadow_absence_2026_05_10.md`
(control-structure-mapper substrate; composes with hypothesis C)

`memory/feedback_skills_as_carved_sentences_knowledge_in_docs_datavault_2_0_pattern_aaron_2026_05_03.md`
(DV2.0 + HKT pattern composition)

algebra-owner skill (Z-set + Clifford + BP/EP F# substrate)
Loading