Decision Context Maps
Before any consequential decision, require the agent to gather a declared set of contextual inputs (resource availability, schedules, downstream dependencies) into a 'context map' the decision must cite.
Problem
Decisions made without gathered context cascade errors downstream — the agent routes production assuming a machine is available that is actually down for maintenance; it schedules a treatment forgetting a contraindication in a record it never queried. The error is invisible at decision time because the agent lacks the relevant input it did not bother to gather.
Solution
For each decision class (production-routing, treatment-plan, etc.), publish a Context Map schema: list of required inputs (data sources, who/what to query, freshness requirements). At decision time the agent populates the map — querying APIs, checking schedules, retrieving records. The decision step receives the populated map as input and cites entries when justifying its choice. Pair with strategic-preparation-phase (which contains Context Maps for one-off problems), policy-as-code-gate.
When to use
- Consequential decisions whose quality depends on out-of-prompt context.
- Per-decision-class context schemas can be specified.
- Latency budget allows context gathering.
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.