One-Minute Example
A platform team asks:
Should we buy, fine-tune, or build an agent stack for our product?
The discussion can mix architecture, vendor comparison, safety, evidence, budget responsibility, user value and implementation planning before the team has established what it is comparing.
A first pass with FPF can make the following distinctions explicit:
- project objects: distinguish the product, the agent stack, and the team or toolchain involved in changing them;
- architecture flow: which candidate and selected structures address the problem pressure, and how expected and actual structures compare;
- comparison frame: which alternatives are in the candidate set;
- evaluation characteristics: cost, latency, controllability, safety, maintainability, time to first use, and other project-specific characteristics;
- evidence gaps: which missing evidence can change whether commitment is justified;
- current decision state: whether the team is choosing now, keeping a selected set, making a project architecture decision, or doing more discovery;
- work and feedback: which method and readiness conditions are needed, what Work was performed, and what evidence supports realization of the selected structures;
- reader reliance: what engineering, management, and assurance readers may responsibly rely on.
These questions can also guide a factory modernization, laboratory protocol, construction design change, supply-chain decision, safety case or research program. They help keep reasoning reviewable and reusable while preserving its meaning in different presentations.