Collective Runtime and the AgentPlat mission lifecycle

A mission needs more than a sequence of model calls

A multi-role objective needs a plan, eligible participants and a way to explain what happened when work diverges from the plan. A list of successful responses does not identify who owned the next step or why a recovery occurred.

The Collective Runtime overview connects mission intent to planning, team formation, assignment and execution, with evidence-backed recovery feeding the loop. Applications can begin locally and add durability or peer coordination as required.

Lifecycle states make operating conditions explicit

The mission lifecycle reference includes states such as proposed, admitted, planned, executing, recovering, completed, cancelled and failed. Transitions are policy-bound and retain evidence.

In an illustrative analysis mission, a plan may be ready while execution is still awaiting an eligible assignment. An operator should see that distinction. A generic “running” indicator can hide whether the system is computing, waiting for authority or recovering from a rejected transition.

A control proposal does not install itself

Proposals to replan or adapt the team remain advisory until the application installs the appropriate fenced transition. Preserve the predecessor and trigger so the change can be explained later.

For example, an agent may suggest replacing an unavailable specialist. The suggestion describes a possible response. The actual replacement needs the current eligibility and lifecycle checks. Recording both the proposal and installed transition lets an operator distinguish a rejected idea from an action that changed the mission.

Choose the control profile deliberately

The reference-integrated profile requires named control gates, including observation, partition, strategy, approval, inference, effect and forensics. Its construction rejects a missing required phase.

This creates an explicit integration contract, not a certification of every handler. Your handlers must implement their responsibilities. A function that always approves is still your application's policy choice, even if it satisfies the structural requirement to supply the phase.

Evaluate one complete mission cycle

• Record the admitted objective and initial plan.
• Inspect the team and assignment used for execution.
• Trigger a bounded failure or recovery condition.
• Follow the predecessor evidence to the installed transition.
• Inspect the final outcome and the controls applied before effects.

The governed runtime facade documents receipts and durable lifecycle operations. Use the exact version-specific integration rather than inferring restart safety from an in-memory demonstration.