We’re borrowing the cadence of Morpheus here; it’s not an actual quote, but the kind of line he’d deliver if he were teaching prompt engineering.
The code rains down the screen. A cursor blinks over a single word—PROMPT>.
Morpheus’ voice is calm: “The machine will render whatever probabilities you give it. Your job is not to hope for a good answer. Your job is to shape one."
You take a breath. This isn’t magic. It’s analysis.
Welcome to the Seventeenth Issue of Chiron
We’ve treated prompting as a craft throughout this series; today we formalize it as an analytic skill. You get a simple, repeatable framework that turns “talking to the model” into a disciplined workflow: specify the role, objective, inputs/outputs, constraints, and evaluation criteria. Then iterate with micro-IOA before anything touches a record.
This is Practical Interaction Skills in the Matrix arc: sober, auditable, ABA-fluent.
The PROMPT Framework (your one-page operator card)
When you build a prompt, set these six levers every time:
