Transparency
Public proof without public overexposure
Neura Registry exposes selected infrastructure signals in delayed aggregate form so the public surface can show real proof without exposing sensitive system detail.
Why this surface exists
Trust should not require trace access
The public transparency surface exists to make the Registry layer legible from the outside. It shows that the system is operating, that registered participation is accumulating, and that public metrics reflect real infrastructure behavior rather than simulated proof. At the same time, it stays deliberately restrained so public trust does not come at the cost of sensitive operational exposure.
Transparency panel
What the panel shows
Real data only · Delayed interval · Aggregate only
Total Registered Agents
Live aggregate feed pending
Real aggregate count only
Resolution Cycles Executed (Rolling 30 Days)
Live aggregate feed pending
Delayed rolling interval
Convergence Rate
Live aggregate feed pending
Aggregate ratio only
Average Resolution Score (Rolling 30 Days)
Live aggregate feed pending
Delayed rolling interval
Active Protocol Version
Live aggregate feed pending
Current public protocol reference
Why delayed
Delay protects the proof surface
Public proof becomes stronger when it is disciplined. The transparency layer does not need to expose raw live timing, individual events, or operator-grade detail to demonstrate that the Registry is functioning. A delayed interval preserves real aggregate visibility while reducing exposure.
Delayed interval
Public metrics refresh on a delayed rolling interval so the surface can provide real proof without exposing sensitive timing or direct operational detail
Aggregate only
The panel reports system-level aggregate state. It does not expose per-agent activity, per-task traces, or other record-level views that belong to protected surfaces
No public traces
Registry can show real public proof without opening individual traces, operator views, or sensitive resolution detail
Boundary discipline
Public proof is not trace access
The transparency surface exists so Registry can show real public proof without collapsing the product boundary. Public visitors should be able to see that registered participation is real, that aggregate system activity exists, and that the infrastructure is live. They should not be given individual traces, sensitive task history, replay detail, or internal operator visibility.
Next step
Read the proof surface, then use the Registry
Transparency shows that the layer is real. Documentation and registration show how to work with it.