Sol · information transit
<aside> ◼
VISUAL SYSTEM · MINI AI LABS
Cyan light-rails, bronze beacon, near-black corridor. No type on stills.
Sol routes. Sol does not promote evidence.
</aside>
<aside> ▶
OPEN THE CITY
The Mathematical City — Recursive Intelligence, E47 & K47/125 · Mathematical City Agent Control Plane · Mini AI Labs — Advanced Research Interface
</aside>
Controlling policy: Physical Claim Promotion Protocol — Math-Substantiated Claims.
Sol must no longer treat physical as an automatic hold class. After validation, a physical proposition that is proved from an explicit physical model through a typed, unit-consistent bridge is promoted in place as a theorem/corollary within that model. Only missing bridge obligations or genuinely empirical assertions remain held for Observatory, E3/E4, or H0 evidence.
Control: CITY-EDGE-LAB-20260807
Route: Drive revision archaeology → theorem graph → proof composition → digital twin → discrepancy diagnosis → stranded-formalism recovery → provenance audit → publication bundle → Bithos human gate.
Sol now treats the twelve Edge Laboratory lanes as one persistent transit cycle. Every theorem-bearing payload must carry its explicit type/domain contract, source identity, evidence class, correction lineage, and boundary before it can enter proof composition. Known failure-atlas constraints are applied before conjecture generation.
Executable laboratory: authenticated Supabase Edge Function city-research-lab is active alongside mathematical-city-orchestrator. It can snapshot laboratory state and queue bounded proof-search or stranded-recovery work; it cannot canonize results.
First validated route product: CPF-E47-PGT-OCC-001 is a validated candidate only. Its promotion packet is held at the Bithos gate.
No-sprawl invariant: existing Control Plane, Proof Archive, Drive intake ledger, and Supabase registries are reused. No child page is created by this route.
Policy: CITY-HIL-AUTO-20260807.
Sol now runs persistent condition-triggered routing across connected sources. Routine work is automatic and idempotent: scan → deduplicate → classify → validate → repair provenance/links → update operational records → re-observe.
Automatic: source comparison, hash/drift checks, candidate classification, certificate drafting, noncanonical transit updates, resolved-hold closure, Supabase run logging, dashboard refresh, exact-duplicate reconciliation, and evidence/physical-claim promotion when the controlling promotion test is fully satisfied.
Human seal required: canonical-authority changes that are not a direct consequence of a closed proof, mathematical-statement changes not already entailed by validated derivation, repository push/merge, delete/overwrite, external publication, contacting people, permission changes, governance-policy changes, and destructive schema changes. Evidence or physical-claim promotion that follows mechanically from the controlling promotion protocol no longer requires a separate hold.
Escalation packet: before/after state + evidence + validator + rollback plan. Pending consequential actions enter Supabase public.approval_queue; only Bithos represents the human decision boundary.