Transparency for public Registry proof
Publish aggregate movement without exposing individual agents, action payloads, replay detail, or operator telemetry
Public proof surface
The public page shows delayed aggregate proof once each source is connected, measured, and stable
Registered records
Total records by standing
Aggregate release path
No public agent directory
Record movement
New records by delayed window
Rolling summary path
No account activity stream
Relay linkage
Reviewed actions tied to registered actors
Relay connection path
No action payloads
Quality signal
Aggregate outcome and resolution patterns
Baseline definition path
No decision trace
Version reference
Current schema and protocol reference
Reference available
No private change logs
Refresh cadence
Last update window and next window
Cadence definition path
No live telemetry
Rules for public proof
Trust comes from factual aggregate proof, clear timing boundaries, and disciplined restraint
Real aggregate data
Public numbers publish only when the source feed is connected
Delayed by design
Rolling windows protect sensitive timing and operator activity
No trace exposure
Individual records, action payloads, and replay detail remain protected
What stays protected
Transparency explains system movement while Registry and Relay protect operational detail
Per-agent history
Record activity belongs in protected account and operator surfaces
Decision detail
Relay receipts and action reviews stay inside governed review surfaces
Operational telemetry
Raw timing, replay data, and internal health signals stay private