Decision Intelligence.
Target System Analysis, BowTie Analysis, and Key Node Analysis. Finds leverage, vulnerabilities, and opportunity windows before action is taken.
- TYPICAL CADENCE
- On-request; scenario-triggered
- TYPICAL SOURCE COUNT
- 1,500–4,000
- TYPICAL OUTPUT LENGTH
- 2,500–5,000 words + diagrams
- TYPICAL CONFIDENCE REGISTER
- Mixed: structural (high) + timing (moderate)
// QUESTION CLASS
What can be done?
Decision is the AI engine that produces deterrent and response options for systematic targeting solutions. Not in the kinetic sense, unless the customer is authorized for that, but in the analytic sense: identifying the prioritized components, interdependencies, and event windows where intervention by any means would force the system to reconstitute, reorganize, or collapse. Target System Analysis (TSA) is rooted in doctrine (JP 3-60) and supports the legal parameters defined in policy standards (CJCSI-3370). It creates a collaborative IC contribution for action arms (CJCSI-3162) while increasing the decision space for Sensitive Target Approval and Review (CJCSI-3122). Now enabled by an AI pipeline that includes tradecraft models from FVEY partners' TSA methodology, adapted for the human-enabled, AI-empowered solution the customer needs. For commercial customers this might be the critical path of a supply chain. For national-security customers it might be the decision-making architecture of a counterpart. The shape of the system analysis is consistent; the application is not. The engine's distinctive output is the BowTie Diagram: a formal mapping with deterrent options on one side, the event horizon at the center, and response options on the other. BowTie is a methodology used in engineering and adapted for intelligence analysis. It is the single most useful visual for communicating where things can go wrong, what happens when they do, and the opportunities to deter or respond.
// ANATOMY
A Decision report contains:
A Decision report contains a Target System Analysis (TSA) that defines how a complex adaptive system works and provides a prioritized list of critical vulnerabilities. This enables action arms and decision-makers with a clear understanding of leverage, plus a prioritized list of change options to consider. The system may strain to re-achieve homeostasis, be forced to reorganize, or eventually collapse under sustained pressure on the right nodes. A TSA is structured around a system, not a narrative. The reader is trying to identify leverage points where change creates stress that expends energy, capital, or social trust. The Critical Vulnerability mapping is the first thing the reader sees; everything else is commentary on specific parts of it. The BowTie Analysis guides the reader to event horizons that may need to be deterred or responded to. The Decision engine identifies leverage points and their constraints. It does not tell a customer what action to take. That is the customer's authority, not the analyst's responsibility. A report that says "you should do X" has stopped being analysis and started becoming advocacy. This distinction is strictly adhered to within IC standards for actionable products. Our analysis is always descriptive, not prescriptive.
// TRADECRAFT
Clarity, accuracy, and precision: easily understood, correct, and detailed.
The mapping is the claim; the mapping is sourced.
Targeting studies earn their weight by being honest about uncertainty in the recommendation supporting change options (deterrence to response), not in the mapping of target system components. Every node, every edge, every dependency in the Target System Map is sourced specifically. A reader who disagrees with the analysis should be able to identify which source is questionable or which inference could be flawed. No edges without citations.
ICD 206 · Full source attributionBowTie Analysis is a formal methodology.
BowTie Analysis is used in engineering (petrochemical, aviation, medical) and adopted by parts of the IC for threat-consequence analysis. We use the formal structure to present change options to our customers for their decision: left side = deterrent opportunities, center = event horizon, right side = response opportunities. BowTie is not decorative. The response opportunities are named and their current state (effective, degraded, absent) is assessed.
BowTie Methodology · Engineering / IC adoptionRecommendations are analytic judgments to enable operational decision space.
The Decision engine identifies leverage points and their constraints. It does not tell a customer what action to take. That is the customer's authority, not the analyst's responsibility. A report that says "you should do X" has stopped being analysis and started becoming advocacy. This distinction is strictly adhered to within IC standards for actionable products. To do otherwise would politicize intelligence and must be avoided to maintain analytic tradecraft. Our analysis is always descriptive, not prescriptive.
ICD 203 · Objectivity + IndependenceOften paired with: Baseline (the system-map foundation), Analytical (pressure-tests critical-node claims).
// OTHER ENGINES