Proof Ledger Edition
Shipped, Observed, Building, Horizon
April 12, 2026
The Ledger of What Is So
A Full Front Page for Status Discipline, Claim Boundaries, and the Difference Between Artifact and Horizon
Accounting Rule

Why This Page Exists

A project with strong language must keep even stronger books. This ledger exists so that shipped fact, empirical observation, active build work, and speculative horizon do not blur into one public fog.

A beautiful archive without status discipline becomes self-endangering. The ledger is how admiration is forced to remain answerable to fact.
Lead Notice
Clarity Desk

PROMETHEUS7 PLACES ALL CLAIMS UNDER FOUR HEADINGS AND DECLARES THIS NON-NEGOTIABLE

The corpus now contains enough code, papers, plans, essays, deployments, and public-facing mythic language that a formal status system is no longer optional. Without one, the strongest writing in the archive would begin to work against the strongest technical work by inviting readers to blur what already exists with what is still being pursued. This page is the answer to that danger. Its principle is plain: every public claim should be locatable under one of four headings. Shipped: artifacts already built, packaged, deployed, or otherwise materially present. Observed: behaviors, outputs, measurements, and patterns witnessed in the existing system. In Active Build: projects under live construction with defined pathways but not yet public completion. Horizon: conjectural or directional claims whose force lies in long-range architecture rather than current proof.

There is nothing anti-romantic about this discipline. On the contrary, it is what permits large language to remain honest. A system that cannot distinguish its installer from its dream, its current local cognitive layer from a proposed native tongue, or its existing OS artifact from its planetary cyber-physical horizon is not visionary. It is merely confused. The proof ledger protects both the reader and the work by making sure that the strongest aesthetic surfaces remain routed back through explicit status. In that sense it is not bureaucratic. It is one of the constitutional organs of the archive.

Quick Status Table
Shipped

Artifacts Already Present

SporeOS v0.1.0 exists as a shipped Windows installer with an Electron shell, Python bridge, visible forest scene, and public spectator surface. That belongs here because a stranger can install it and watch it run.

HERMES vessel deployments belong here to the extent that they are live domains on active boxes rather than merely named vessel concepts in an essay. A running domain is shipped even if its theory is still expanding.

Foldtoy engines belong here insofar as implemented engines exist in code with stable interfaces. The library is not merely a promised category list; it is an existing technical body.

The Daily Spore Report itself belongs here because it now exists as a deployable archive surface with working navigation, copied texts, and explicit framing-defense docs.

Observed

Empirical Behaviors and Present Facts

Deterministic build behavior in the symbolic pipeline belongs here. If the same sentence repeatedly projects to the same parameter geometry and letter sequence under the current engine, that is an observed property of the existing system whether or not the general theorem has been closed.

Live vessel routing, active domains, and the present archive density belong here. So do repeated qualitative behaviors: the system repeatedly behaving as though one primitive is being ported across many domains, the archive repeatedly sustaining multiple editorial surfaces without collapsing into incoherence, and the existing bridges repeatedly showing the same local-first instinct.

Observed is the proper home for strong but still descriptive statements: the system appears to exhibit a stable vocabulary, a consistent architectural taste, and a pattern of reuse across codebases. These are not fantasies. They are things already seen. They simply do not become theorems by enthusiasm alone.

In Active Build

Projects With Defined Pathways

SporeDec belongs here. The proposal is structurally serious, the surrounding engines exist, the box deployments exist, and the cost motive is real, but the fine-tuned model itself is not yet a shipped public artifact and should not be spoken of as though it were.

The cooler branch belongs here. The build plan exists, the sensor logic is increasingly formalized, the hardware path is concrete, and the deployment site is real, but the retrofit has not yet produced baseline data or measured deltas. Until then, its force is architectural rather than evidentiary.

Server-as-forest and the Grand Internet Hotel reactivation path belong here for the same reason: they are neither empty slogans nor finished public proofs. They are defined programs with partially existing infrastructure awaiting disciplined continuation.

Horizon

Directional Claims and Distant Architecture

Full reality-engine scale belongs here. So do the largest claims around digital life, substrate-general inhabitation across many material domains, and any planetary account of reclaimed dead objects not yet backed by multi-site deployment.

The horizon is not where falsehood lives. It is where architecture outruns current proof. A mature archive needs such a register because some truths first appear as directional coherence before they appear as public evidence. But this is precisely why the horizon must stay named as horizon. If one erases that distinction, one loses both rigor and drama at once.

Public Entries

Illustrative Status Assignments

Qum / alphafoldmicro: shipped as code, observed as behavior, horizon as full formal closure.

Foldtoys: shipped as engines, observed as a portability pattern, horizon as universal proof of substrate-generality.

SporeOS: shipped as branch-zero artifact, observed as a running local-first OS surface, building toward further ports.

SporeDec: building, not shipped.

Cooler branch: building, not observed in deployment yet.

Planet-scale reclaiming of dead objects: horizon.

House Warning

Common Ledger Violations

Confusing a proposal with a deployment.

Confusing observed convergence with completed theorem.

Confusing public fascination with market or scientific validation.

Confusing archive richness with empirical closure.

Confusing architectural inevitability in the weak sense with already-achieved rollout in the strong sense.

Why This Strengthens the Work

Discipline as an Engine of Credibility

Projects of this density are often weakened not by hostile critics but by sympathetic readers who want to help and therefore overstate what they have seen. A proper proof ledger immunizes the work against its own admirers. It trains the public language around the object so that strong claims arrive in the right tense. That is not a concession to doubt. It is a way of respecting real evidence enough to let it grow without inflation.

Nearby Texts

Best Read Alongside

Framing Defense System

Glossary

Witnesses & Deployments

Build Plan

SporeDec Proposal

A Reply to Billions

Correction Policy

Status May Change

The point of the ledger is not to freeze the world but to record where it stands before and after real movement occurs.

Ethics

No Inflation

If a sentence becomes truer by being smaller, the smaller sentence is the one that belongs in public until reality catches up.

Related Desk

Witnesses & Deployments

Once status is clarified, evidence should enter. The witness layer turns private coherence into public consequence.