What Decision Produces
The core output of a Decision engagement is a clear, evidence-grounded answer to the question: given what the market is signaling, what should we build, validate, or avoid? That answer is not a generic framework applied to your context. It is derived from your specific CoDomain frames — the direction labels, field sentiment reads, pattern analyses, and verdicts that CoDomain has already structured for the categories relevant to your product. Decision does not start from zero. It starts from your data.How It Connects to CoDomain
Your CoDomain frames are the entry point for every Decision engagement. Specifically, the verdict — Validate, Scale, Refine, or Pivot — defines the shape of the work.- Validate: Decision scopes a prioritized validation plan: what to test, in what sequence, against which signals, before committing major resources.
- Scale: Decision maps what scaling actually requires — where the category is structurally ready, where it is not, and what the operational and positioning implications are.
- Refine: Decision identifies what needs to change — in positioning, in the deployment pattern, or in the product scope — and builds a structured path forward.
- Pivot: Decision frames where the market signal does point, and what fit opportunities exist in adjacent categories CoDomain is tracking.
Key Outputs
A CoTerminal Decision engagement produces four structured outputs:Pattern-to-product fit assessment
Pattern-to-product fit assessment
A structured evaluation of how well your product concept, roadmap, or existing system maps to the deployment pattern CoDomain has analyzed. This is not a generic product-market fit score — it is grounded in the specific field sentiment, capital signals, and structural mechanisms CoDomain tracks for your category.
Structural blocker identification
Structural blocker identification
An explicit map of the blockers — capability gaps, procurement structure, governance requirements, or workflow fit issues — that CoDomain’s signal shows are slowing adoption in your category. Knowing which blockers are structural (and therefore predictable) versus situational changes how you sequence product and go-to-market work.
Positioning recommendation
Positioning recommendation
A positioning recommendation grounded in field sentiment data — not in what competitors are claiming. If your category is “capital ahead,” your positioning needs to account for a gap between vendor ambition and operator conviction. If it is “field ahead,” the opportunity to lead with practitioner language is real and specific.
Prioritized validation plan
Prioritized validation plan
When the CoDomain verdict is Validate or Refine, Decision produces a sequenced validation plan: the specific questions to answer before committing further resources, the signals that would confirm or contradict your current direction, and the threshold at which a re-read is warranted.
When to Engage
CoTerminal Decision is most valuable at three specific moments:- Before committing major resources to a new AI category or deployment pattern — when you have a CoDomain read but have not yet scoped engineering investment, go-to-market spend, or roadmap reallocation.
- When a CoDomain refresh produces a material direction change — if a category you are already building in shifts from “aligned” to “capital ahead,” the implications for your roadmap, positioning, and validation approach change. Decision structures that re-evaluation.
- When field sentiment and capital signals are significantly misaligned — either in your favor or against you. Significant divergence in either direction is a signal worth analyzing structurally before acting on instinct.
CoTerminal Integration
Once Decision produces a green-light or refine verdict, Integration scopes and executes the implementation.
Reading a CoDomain Frame
Understand how to interpret the direction, verdict, and signal read that inform a Decision engagement.