capsule-identity

Why we included this project

On Astrid OS this capsule is where a persistent agent identity becomes an actual system prompt. It holds the agent's callsign, class, aura, signal, and core directives in capsule state, then merges those with working-directory and platform context each time a build request comes in. Before an identity exists, the generated prompt includes onboarding instructions, and the LLM can save what it settles on through the save_identity tool, which also writes spark.toml as a recovery copy. State is scoped to the calling principal and the session ID is echoed back for correlation, so the capsule fits an event-driven, multi-tenant agent runtime instead of standing alone. It is a deliberately narrow, protocol-bound component, so it mainly pays off for teams already on the Unicity capsule architecture rather than as a general prompt builder.