Run. Prove. Verify.
A system runs. It produces evidence of what it did. Anyone can check that evidence later. That is the entire idea — the rest is engineering.
It runs
A request arrives. An AI system processes it and produces a result — a document, a decision, a number, a page.
It proves
Alongside the result, the system records a small piece of evidence about what happened. That evidence is anchored publicly.
You check
Later, anyone — auditor, regulator, customer, journalist — can look up the evidence and confirm the result matches. No special access, no vendor login.

Six nodes. One promise: the result and its evidence travel together.
Deliberately generic. No extraction methods, no chain names, no internal component names — the mechanism is intentionally out of scope for this page.
- 01Request or taskAI system processes it
- 02AI system processes itResult delivered
- 03AI system processes itEvidence recorded
- 04Evidence recordedAnchored publicly
- 05Anchored publiclyAnyone can verify later
- 06Result deliveredAnyone can verify later
A single request, end to end.
The AI-controlled homepage records itself.
When you talk to the concierge and the site changes, that change is an event. It carries the same evidence as any other run. You can see what changed and when.
- 01User types a request in the chat panel
- 02Concierge interprets the request
- 03Site canvas updates: layout, copy, or color
- 04Change is recorded as an event
- 05Anyone can check what changed and when
The concierge is a designed pattern, shown here as a capability walkthrough. Live product status is disclosed on the demo page itself.