Principles and path
Public Wiki
EolSpace connects project state, important changes and decision history to grounds you can inspect.
In the intended process, you choose objects and observation limits. The cabinet shows how current the evidence is, a notification explains a change and links to the event, and a proposed next step does not replace human approval. Contributors prepare work, checks establish specific properties, CareProof preserves evidence limits, and TypeSafeAI metrology studies when assessments can be trusted; that integration is not yet implemented.
Local Records and a technical example are available today. The cabinet and Linux CLI belong to a closed pilot; Windows, Linux GUI, Android and iPhone each have a separate status. The seven pages below explain principles and dated history, not current product availability. Platform status ↗
Three States, Not Two
The system answers "holds," "broken," or "unset"-and the third answer is never collapsed into the first.
The Observer's Position
Where an observation was taken from is part of the answer. A projection that does not know where it stands publishes its own location as the state of the system.
Evidence Has an Address
Where a component runs and where it delivers evidence of its work are two different facts. Confusing them means reading an old copy as fresh truth.
An Empty Check Has Not Passed
The list of broken things is empty only if someone looked. "We saw nothing" and "there is nothing" are different statements.
A release and its evidence
The historical fifteen gates described the state on 26 August. Today the site follows a shorter, verifiable route from commit to live page.
How the parts work together
EolSpace connects intent, work, evidence, permission, outcome and versions. The surrounding roles stay distinct; the older Sun, planets and satellites model is historical.
The Path
The system grew gradually, and an honest history is worth more than a polished one: here is what broke, what it taught us, and why the current rules look the way they do.