How the role is applied.
Name the decision holder
State who must decide and the time horizon in which the decision matters.
Map constraints and incentives
Identify evidenced resources, dependencies, feedback, and competing objectives.
Separate evidence from inference
Mark which relationships are observed and which are analytical judgments.
Compare choices
Describe which choices open, narrow, remain unchanged, or close, including the conditions that would reverse that result.
Output and failure condition.
Output
A decision-oriented analysis of available choices, dependencies, and reversal conditions; it is not a prescription.
Failure condition
It fails if it invents a decision holder, forces every situation into a phase model, presents an unsupported probability, or recommends action without showing the evidence chain.
Worked example
When credit issuance crosses a historical infrastructure threshold, Manticus asks how that changes financing structures, diligence on second-owner economics, and the conditions under which those choices would change again.
Inspiration without implied computation.
Manticus draws on systems theory, active inference, and the boundary concept often described through Markov blankets. FP1 uses these as reasoning prompts; the current workflow does not solve an active-inference model or calculate a Markov blanket.
Consequential judgments remain attributable. Model-generated or software-assisted outputs enter an FP1 decision brief only after review against the cited evidence and the role's stated failure condition. See the full analysis architecture.