All capabilities Proof it stayed in bounds · grounded plan

It builds against your real systems, not an imagined one.

It plans from your actual filesystem and refuses to invent a path, a file, or a dependency that isn’t really there. The plan is checked against reality before it runs.

How the plan stays honest

Each planned step references things resolved through the location surface — real paths, real files. A reference that can’t be resolved is a halt, not an assumption.

No imagined dependencies. If a step needs something that isn’t present, the agent surfaces that rather than pretending it exists.

How location is resolved, never assumed
Causal recordcau·e5f6a7b8
produced_byplanner.resolve
referenced/srv/app/config.yaml
decisionpath_not_found
halt — refusing to assume it exists

Invariant Every path, file, and dependency is resolved against what actually exists. Nothing is assumed into being.

Go deeper — location & grounding

How the location surface resolves where things are, so no path is ever invented or assumed.

Read the doctrine