Mission uses agents to perform controlled engineering work. The canonical journal for an Agent execution must be explicit, inspectable, and daemon-owned; it must not depend on adding a broad prompt and hoping the agent discovers the correct artifacts. The term context is reserved for the Agent’s model-facing context window and is not the canonical name for AgentExecution-owned state.

An Agent execution journal records the ordered inputs, artifact references, Entity references, instructions, observations, decisions, and effects for one execution. When the execution is Mission-scoped or task-scoped, those references commonly include Mission artifacts. Agent-session artifacts are first-class Mission artifacts produced by or attached to an Agent execution, such as transcript summaries, extracted test output, patch summaries, or generated implementation notes. Mission Control surfaces may display those artifacts through canonical Entity relationships without changing their Entity identity.

Raw Agent execution logs are not Mission artifacts by default. They are daemon-owned audit material retained with daemon runtime state, and with the Mission record/state store when the execution is Mission-scoped. If a transcript summary, test output, patch note, or implementation note becomes useful to a Mission, the daemon or operator promotes that curated material into a separate Agent-session artifact that may reference or extract from the log.

Agent execution journal ordering is durable Agent execution state. The order of inputs, artifact references, instructions, observations, decisions, and effects is part of the execution’s working state and audit trail, so the daemon owns and persists that order with the Agent execution journal.

Changes to the Agent execution journal become canonical when accepted by the daemon. An Agent execution is indeterministic and may ignore, misunderstand, or fail to structurally acknowledge a delivered message, so runtime delivery must never be treated as proof that the Agent execution applied the journaled change. If Mission also sends a message to the Agent adapter, that delivery is best-effort instruction and audit evidence, not the source of journal truth.

When an Agent-session artifact becomes useful beyond the session that produced it, Mission keeps the same canonical Mission artifact and records the necessary Entity relationship. Promotion is a relationship change, not a content copy into a new artifact. A future copy operation would need explicit lineage semantics and should not be the default.

This keeps agent behavior auditable and controllable: prompts can explain intent, but the Agent execution journal is the canonical ordered record of what the daemon accepted, what the agent observed, and what effects the execution caused.