A public map of separated proof planes.
The architecture is designed so source, validation, runtime, signal, evidence, and public proof do not collapse into one unsupported claim.
Public inspection layer
System overview
Each plane owns a different class of truth. Promotion requires movement through gates, not presentation alone.
01
Source exists and can be reviewed.
Source does not prove runtime.
02
A bounded validation path passed.
Validation does not prove signal.
03
Runtime state needs separate evidence.
Website rendering is not proof.
04
Signal state needs observed evidence.
Promotion requires evidence.
05
Evidence must be preserved and linked.
Public claims require promotion.
06
Only explicitly promoted claims belong here.
The ceiling remains bounded.
Promotion model
A public claim cannot inherit proof from a different plane. Each plane has its own can-prove and cannot-prove boundary.
Truth Surface Control Board
These controls highlight matching lanes and conveyor gates. They do not promote proof. Website rendering remains reviewer routing only.
source
Where does the work enter the system?
validation
Did controlled fixtures exercise the behavior?
runtime
Did the system execute in a lab or runtime environment?
signal
Was an event, match, or correlation observed?
evidence
What receipt supports the reviewer decision?
public-proof
What can the public page safely route to?
Filter inactive · all surfaces shown.
Controls
The website can host stable data attributes for scanners, but enforcement still lives in repositories, workflows, and promotion gates.
