Planning and approvals

Cortex converts an objective into a plan tied to the session, workspace revision and available capabilities. The plan distinguishes observation from mutation and identifies steps that need user or policy approval.

Allowed actions are projected by the server for the current workflow state. Clients submit the exact run, revision, approval ID, plan hash and confirmation payload; they do not infer permission from the plan text.

When requirements or the workspace revision change, Cortex revises or replaces the plan. A stale approval cannot authorize a new plan.