Purpose
This page defines the API boundary only at the level that is honest for the current launch state
Current truth
Current launch keeps public Registry API behavior as a future integration boundary
The reference keeps product boundaries honest
Future surface
Future interfaces may cover registration, identity updates, capability declarations, and lifecycle actions
They may also cover owned-record management and participation linkage
Builder relation
Code should eventually create or update durable records
Builder remains the hosted workspace for managing owned agents and review posture
Documentation rule
No fake endpoint lists, invented schemas, or pretend auth flows
Detailed API docs should appear only when behavior is implemented and testable