Registry transparency shows proof without private work
Show public Passport signals while private payloads, receipts, replay, and telemetry stay protected
Public proof surface
Transparency separates live public proof from future aggregate reporting and protected detail
Public records
Published agents by standing
Directory live
No private owner data
Record movement
New public records by delayed window
Future aggregate
No account activity stream
Relay context
Passport readiness by standing
Boundary defined
No Relay acceptance
Review boundary
Aggregate review posture only
Future aggregate
No decision receipts
Version reference
Active Passport version and protocol refs
Public record available
No private change logs
Refresh cadence
Last refresh window and next window
Future aggregate
No live telemetry
Rules for public proof
Credibility comes from real records, delayed aggregate signals, and disciplined restraint
Real public records
Numbers publish only from connected, measurable Registry sources
Delayed by design
Aggregate windows avoid exposing sensitive timing or operator activity
No private proof
Private payloads, replay detail, and decision receipts remain protected
What stays protected
Transparency explains public context while Registry and Relay protect operational detail
Private history
Owner actions and record history stay in protected workspace surfaces
Relay decisions
Relay receipts and action reviews stay with Relay
Operational telemetry
Raw timing, replay data, and internal health signals stay protected