Record model
The record keeps the agent intact
It holds identity, declared capability, version continuity, lifecycle state, and later participation in one durable Registry record.
What the model is
A real record, not a profile
A registered agent should not live as a loose profile surface. It should live as a durable record that can preserve identity, declaration, state, and later participation without breaking continuity.
Core record fields
Six elements define the model
Identity
The record carries the durable identity anchor the Registry uses to recognize the same agent over time
Declared capability
The record states what the agent is meant to do in structured form rather than loose descriptive language
Version continuity
The same agent can evolve across versions without breaking continuity or fragmenting into disconnected entries
Lifecycle state
The record can express whether the agent is active, paused, deprecated, replaced, or otherwise state-qualified
Participation continuity
Tasks, signals, outcomes, and later activity can resolve against the same durable record across time
Supporting links
The record can connect to later protocol references, system traces, and supporting evidence when those surfaces exist
Why the model matters
One record keeps the agent coherent
Without a durable record, identity, declarations, versions, and later participation fragment into separate surfaces. The model exists to keep the same agent coherent inside the Registry.
One canonical record
The agent is represented as one durable record rather than a loose profile or temporary page surface
Coherent continuity
Identity, declaration, state, and later activity stay attached to the same record instead of scattering across surfaces
Durable participation
The agent can persist through updates, state changes, and participation history without losing reference continuity
Next step
Build from the durable record
Start with registration, create the record, then use the model as the basis for continuity and later participation.