What belongs in a capsule?
Enough context to understand the assignment, recover its state and find its evidence. Keep the working package focused while linking to the durable records behind it.
- Mission identity, objective and accepted scope
- Agent identity, role and responsibilities
- Approved context with source and version references
- Permissions, resource bounds and required approvals
- Current state, outcome and evidence references
Continuity across execution.
A capsule gives the next execution a defined starting point. Changing the reasoning substrate should not silently change the agent’s identity or erase the mission’s history.
The canonical mission and source records remain authoritative. A capsule is a scoped working package, not a second ledger or blanket permission to act.
Context is not enforcement.
A capsule can describe a permission or a budget. The runtime and connected systems must enforce it at the point where work occurs.
The packaging and portability described here are a product model. Exact serialization, encryption, transport and compatibility guarantees depend on a defined and validated implementation.
Make the work reviewable.
Replay needs the recorded inputs, state changes and evidence references. Rehearsal needs an explicitly bounded scenario. Live work needs the current mission state and authority.
Morphitas presents those experiences; Compacitas provides the execution and continuity underneath them.