Module view 

PlanningView — the budgeted, agent-facing projection for one planning call.

Runtime state can be rich. PlanningView must be small. Planners receive this budgeted projection, not the full runtime state, so prompts stay under token budgets and the same context contract works across planner implementations.

Principle: store broadly, select narrowly.

Memory / knowledge / event refs are typed here but populated only by later PRs (memory store + memory-aware selection). PR1a only fills screen, elements, adapter_facts, adapter_actions, capabilities, blockers, anomalies, evidence, omitted_counts, selection_rationale.

Structs

AdapterActionRef

Adapter-backed action currently available to a planner.

AdapterFactRef

Reference to an adapter-backed fact relevant to the goal.

AnomalyRef

Reference to an anomaly the runtime flagged that the planner should see.

Blocker

First-class blocker that should not be lost to compression.

CapabilityRef

Reference to a capability the runtime currently has wired up.

EventRef

Reference to a recent event the planner should be aware of.

EvidenceRef

Reference to evidence that explains why selection picked something.

KnowledgeRef

Reference to a knowledge record selected for this view.

MemoryRef

Reference to a memory record selected for this view.

OmittedCounts

Counts of items the builder filtered out to fit the budget.

PlanningBudget

Caller-provided ceilings for one planning view.

PlanningElement

Compressed element representation for the planner.

PlanningElementState

State flags that matter for planning. Strict subset of ElementState.

PlanningScreen

Compact screen-level summary written by perception.

PlanningView

Compact, budgeted projection of CEL state for one planner call.

RunProgress

How much of the run budget the planner has consumed so far.