E Evidence & demonstrations
Evidence, with its boundaries.
Each demonstration should explain exactly what the viewer can and cannot conclude.
How evidence is published
A demonstration is published only after technical review and disclosure approval. Each one shows one specific task, states its implementation and evaluation status, names its environment and sets out what was not tested.
A recorded demonstration does not require a public application endpoint.
Nothing cleared yet.
Implementation evidence is not yet public. No demonstration has been cleared for publication, so none is shown: there are no screenshots, videos or results on this page, and nothing here should be read as a working system.
The closest published material is the Cocoon of Love architecture concept, shown as a proposed reference workflow and labelled as not verified implementation.
What each record will contain
The structure of a demonstration record. No records have been published yet.
- Demonstrates
- One specific task.
- Implementation
- The confirmed state: Concept, In development, Working prototype or Operational.
- Evaluation
- Not evaluated, Internally tested or Independently evaluated.
- Environment
- Sandbox or bounded pilot.
- Limitation
- The explicit untested boundary.
- Record
- Component name, version, date, result, reviewer and disclosure approval.
- Media
- An actual screenshot or approved video still, with captions, transcript, version and date.
Notes and boundaries
Each record will link a technical note describing the method, observation and limitation behind it. No technical notes are public yet.
Any future interactive demonstration would run in a separate sandbox, with explicit access and no unrestricted internal data.
Ask what exists.
Researchers, grant reviewers and institutions can ask about the current state of the work.
Contact the architects