Appendix A — MAGE Engineering Stacks

A.7 Context Delivery

A.7.1 The Capability

Put relevant engineering knowledge and obligations into the actor's context before the decision they must inform.

A.7.2 When This Stack Earns Its Keep

Reach for it when:

A.7.3 The Composition

The Context-Delivery stack: standing policy and a retrieved task slice compose into actor context that reaches the action; point-of-action reinforcement is a dashed enhancement Engineering knowledge — models, rules, decisions — feeds two solid load-bearing lanes. STANDING POLICY supplies compact policy that is always seen. TASK SLICE retrieves task-relevant context as needed. Both converge into ACTOR CONTEXT, which the actor carries into the ACTION. One enhancement attaches as a dashed, open-arrowed reinforcement: POINT-OF-ACTION reminders reassert obligations where useful. Context is a reasoning aid, not authority: critical decidable properties graduate out of briefing entirely and into deterministic controls. ENGINEERING KNOWLEDGE models · rules · decisions STANDING POLICY always seen TASK SLICE retrieved as needed ACTOR CONTEXT ACTION POINT-OF-ACTION reminder / deterministic gate load-bearing (required) enhancement (not required) Solid path: the load-bearing composition. Dashed attachment: a useful enhancement, not required. Context is a reasoning aid; critical decidable properties graduate into deterministic controls.
Figure A.7-1. The context-delivery composition. Engineering knowledge — models, rules, decisions — splits into a STANDING POLICY that is always seen and a TASK SLICE retrieved as needed; both feed the actor's context, which drives the action. A dashed POINT-OF-ACTION attachment reasserts important obligations at the moment of action, and for critical decidable obligations becomes a deterministic gate rather than a reminder. Solid path: the load-bearing composition. Dashed attachment: a useful enhancement, not required for the capability.

A.7.4 Constituent Moves

Table A.7-1.
MoveRole
STANDINGSupply compact policy that applies broadly.
SLICERetrieve the task-relevant model and engineering context.
DELIVERPut that context into the actor's reasoning horizon.
REINFORCE(strengthens) Reassert important obligations at the point of action where useful.
GATEFor critical decidable obligations, do not rely on delivery at all — enforce them.

A.7.5 Why These Travel Together

An actor cannot reason through knowledge it never sees. But loading the entire engineered environment into every context only moves the navigation problem downstream: now the actor must find the relevant fact in a wall of them. Context delivery therefore combines compact standing policy with task-specific retrieval.

Point-of-action reminders can reinforce obligations that still require judgment. Critical decidable obligations should instead become deterministic controls: context is a reasoning aid, not authority. Boot files, dynamic snippets, hooks, and nudges are current implementations; the portable pattern is standing policy, task-specific retrieval, and deterministic enforcement where warranted.

Mechanisms: standing context · dynamic context injection · point-of-action guidance

© James C. Davis, 2026–present