Entry condition: Two full DQ® cycles confirmed.
DQ®
must be embedded before DE® is deployed
0
live and generated outputs
0
engine capabilities, all subordinate to human accountability
0
exceptions to the sequence requirement
the approach
Human accountability leads. Technology supports. Structure does not emerge from technology.
The hierarchy is not a preference. It is the decision governance architecture. An organisation that leads with the DE®, before its decision logic has been proven manually, is automating the wrong process at scale.
Governance leads
DR® and DQ® prove the logic. DE® codifies what already works.
Accountability is human
DE® amplifies decision architecture. It does not replace the named decision owner.
Volume justifies deployment
DE® is deployed when the same proven decision class® recurs at a frequency that makes manual execution a genuine bottleneck.
What DE® is
Not just an AI platform. The proven architecture at scale.
DE® is not a separately branded product. It is not positioned as AI-led governance. It is not offered as a standalone technology solution. It is the natural evolution of DQ® when manual structuring becomes a bottleneck due to decision volume, pattern complexity, or portfolio scale.
The hierarchy rule governs every DE® deployment without exception. Technology supports structure. Structure does not emerge from technology. The engine accelerates what is already proven and embedded. It does not lead, replace, or override human accountability at any point.
What it is not
A separately branded AI product or platform
What it is not
An alternative to DR® and DQ® for organisations that have not completed both
What it is not
A replacement for named human accountability at any decision point
What it is
The AI-native infrastructure for proven decision logic at scale
What it does
Amplifies the governance architecture already embedded through DQ®
What it requires
Two full DQ® cycles confirmed before DE® deployment begins
What DE® produces
Four outputs. Two live. Two generated.
DE® produces four outputs across every deployment. The first two are live: the engine runs continuously and the sponsor has visibility without manual effort between formal review points. The second two are generated: at each decision cycle, the engine produces a formal governance record. Human accountability is maintained at every output point across all four. The output architecture is discussed under NDA.
Live operational outputs
01
The sponsor has continuous visibility of the governance standing of every decision in the governed class, without manual effort between formal review points. The engine runs. The standard does not lapse between cycles.
02
A formal, time-stamped record confirming that active governance oversight was in place at every point in the operating cycle. The record is not produced retrospectively. It is continuous.
Generated governance records
03
At each decision cycle, the engine produces a structured governance record of the decision as made: what the engine flagged, what the sponsor decided, and the documented basis for that decision. The record is tamper-evident.
04
Across the portfolio and over time, the engine produces a comparative record showing how the governance standard has been applied across decisions. The record is board-ready and regulatory-defensible.
The engine provides structured data at every output point. It does not decide. Human accountability is named, active, and documented at every decision cycle across all four outputs.
Deployment conditions
Technology supports structure. Structure does not emerge from technology.
DE® is deployed only when the conditions for automated governance are confirmed. The conditions are not aspirational. Each one is verified before deployment begins. The sequence is not a preference. It is a structural constraint.
Stay manual when
01
The decision is strategic or politically nuanced
02
Data flows are inconsistent or unstable
03
Organisational trust in the governance logic is still forming
04
Decision volume is low and manual structuring is not a bottleneck
05
Context changes too frequently for model calibration
Deploy DE® when
01
The decision is operational, high-frequency, and recurring
02
Data flows are stable, structured, and consistently available
03
The governance logic is proven and consistently applied through DQ®
04
The same decision type recurs monthly or weekly across the portfolio
05
Context is sufficiently stable for model calibration and maintenance
DE® deployment requires two full DQ® cycles confirmed. The governance logic must be proven and consistently applied before it is encoded into automated architecture. This is not a recommendation. It is the entry condition.
The institutional shift
What changes after DE®.
The architecture is not the constraint after DQ®. The manual effort required to operate it at volume is. DE® removes that constraint without removing human accountability. The governance standard does not change. The effort required to maintain it does.
Before DE®
Manual data assembly required at each decision cycle
Governance record produced quarterly, not continuously, and only on request
Drift detection depends on the formal review cycle
Portfolio-scale comparison requires significant manual effort
Audit trail is assembled manually and retrospectively, without a continuous record
After DE®
Data assembly is automated. Governance visibility is continuous.
Governance record is generated at each decision cycle, no manual effort
Drift is detected and flagged before it produces an outcome
Portfolio-scale comparison is available at any point in the cycle
Audit trail is tamper-evident, time-stamped, and continuously maintained
Sponsor profile
DE® is for the organisation where the governance works and the volume demands automation.
The DE® sponsor has completed DR® and operated DQ® across at least two full annual cycles. The governance logic is proven and embedded. The manual effort required to operate it at the volume the organisation now requires has become a bottleneck. DE® removes that bottleneck.
The sponsor does not change at DE®. The same individual who held DR® and DQ® holds DE®. The accountability structure does not change. The engine operates within it.
Deployment qualification criteria
01
DR® has been completed and the full governance instrument suite received at close-out.
02
DQ® has been operated for a minimum of two full annual cycles with confirmed governance records at each quarterly review.
03
The manual effort required to operate the governance architecture has been formally identified as a volume bottleneck.
04
Data flows are stable, structured, and consistently available for automated ingestion.
05
The sponsor holds the same budget authority and personal accountability that qualified them for DR® and DQ®.
When DE® is not the right conversation
01
DE® is not the right conversation for an operator that has not completed at least two full DQ® annual cycles with DecIQ®.
02
DE® is not the right conversation where the operator's data flows are inconsistent, unstructured, or disconnected across operating units.
03
DE® is not the right conversation where the governance logic has not been proven and is not producing consistent, documented outputs under live conditions.
04
DE® is not the right conversation where decision volume is low enough that manual operation of the governance architecture is not a genuine bottleneck.
05
DE® is not the right conversation where the primary interest is technology capability: the engine amplifies governance logic that already works, it does not create it.
Commercial terms
DE® is a premium module or enterprise licence deployed selectively. It is priced as a deployment and operation fee. Commercial terms and structure are discussed directly with the founding team and only with sponsors who have completed two full DQ® cycles. No DE® commercial conversation begins before that condition is met. Terms are engagement-specific. There are no standard packages.
DE® is the final stage. The conversation starts at DR®.
DE® is not the entry point and it is not discussed before DR® and DQ® are confirmed. If you are at DE®, the conversation is already well underway. If you are not yet at DR®, that is where it starts.
Engage