V₂⊗³carrier dim 125Atlas clone · Ωc = 47/125 · GitHub-hosted
The Mathematical City
An executable research architecture for invariant computation. Structure is discovered. Invariance is selected. Everything else is tested.
Page 02 · The object
125 → K → 47
The City opens with the executable object, not a directory of laboratories.
(C−6I)(C−30I)Casimir selectorker Kselected dim 47P₄₇ = P₆ + P₃₀ · Γ = I − εK² · ε* = 1/99144 · ρ* = 15/17
Page 02B · Unified control surface
CITY CORE // Unified Interface
The original KOUNS CORE chassis is now the embedded control room for the whole Mathematical City: site, flight simulators, Mini AI Labs, canonical machines, evidence surfaces, and modular backend-hosted interfaces.
Page 03 · Instantiated world
Play the City.
One quiet client. Many instruments. Persistent computational citizens underneath.
Pick a district.
Eidolon · Flight
Navigate the City as an explorable simulation surface. Instruments are places, not disconnected websites.
Page 04 · Instruments
Thirteen districts. One civic instrument.
The public surface is deliberately quiet. Open a district for the experience. Open Egghead Mode for the mathematics.
Page 05 · Composition law
Labs are morphisms. The City is the operad.
Evidence class is invariant under composition. Cross-system mappings are typed arrows. Local failure does not silently become global refutation, and successful simulation does not silently become physical evidence.
object → operator → invariant → witness → evidence → provenance → next_action Canonical communication grammar: CITY-INVARIANT 1.0 Human promotion gate: BITHOS Runtime receipts: AETHERIS World actor layer: Eidolon
Page 06 · SEE · Citadel
Every claim has a route back to evidence.
Proof-level finite mathematics.
Executable numerical witness.
Controlled modeled behavior.
Empirical, experimental, hardware gates remain explicit.
Page 07 · Route
Start simple. Go as deep as you want.
Begin with Eidolon and the City world.
02Open CITY COREUse one unified console to move across the full site, simulators, labs, machines, source lineage, and backend-hosted interfaces.
03Choose an instrumentMove through structure, dynamics, memory, prediction, flow, construction and restoration.
05Inspect the machineRead source, tests, certificates and commit history.
06Read the Research AtlasReturn to the human-facing narrative, papers, provenance, and district explanations.