Permanent identity, replaceable harnesses

If role, scope, memory, and work history exist only inside one model session, changing compute can silently create a new worker. The business then loses continuity and cannot reliably attribute decisions or performance.

The Buzz design uses a stable identity record as the anchor for the agent's name, business, team, supervisor, owned outcome, scope, permissions, skills, proof obligations, scorecard, and version history. ACP-compatible harnesses can be assigned to that record without becoming the record.

• The same identity and role remain addressable after a harness change.
• Permissions and memory boundaries do not expand during the change.
• Work history and proof references remain attached to the identity.
• The candidate package passes failure tests and independent inspection.
• Export, import, rollback, and version readback are captured as evidence.

ATLAS is the intended Business Builder Lead and the first internal identity record. The public site deliberately omits keys, model history, runtime counts, and certification claims. A signed native response, delegated job, proof object, independent verdict, and snapshot import round trip remain the acceptance chain.