Skip to main content
ECM™ 01 / 06

Enterprise Coherence Model

The integrating governance layer, above TOGAF, COBIT, SAFe and ISO 27001, that makes transformation outcomes measurable, board-reportable and causally traceable.

Problem addressed

Large enterprises fail because they absorb change without structural discipline. Every acquisition, cloud migration and AI programme adds complexity: structural entropy. The dominant frameworks (TOGAF, ITIL, SAFe, ISO 27001, COBIT) each optimise their own domain and leave the coherence of the whole unmeasured. The standard reporting instruments of most CIOs do not give the board the structural visibility that material oversight of technology risk requires.

Framework structure

Five interdependent layers, each with a coherence metric, a governance owner, a board KPI and a RAG threshold calibrated for sector and strategic phase. An inter-layer causality model and four feedback loops, including F4, the AI Complexity Engine, connect the layers into a system. The scorecard is reported to the board quarterly and gives the five layer statuses without a composite score.

Value delivered

A five-layer scorecard the board can read, a causality analysis that identifies the primary intervention point, and a four-phase roadmap, from the Entropy Baseline Diagnostic (6 to 8 weeks) to the quarterly board reporting cycle.

Primary audience

Board, CFO, CIO, CTO, Chief Architect, CISO, General Counsel

Documents provided on request

  • White paper v6.10 (EN, FR)
  • ECM Diagnostic Tool v6.3
  • ECM web app v2.3
  • Write to the author to obtain them

Related frameworks

VEGA™ (the IVS modifies CRS in C1), TDG™ (Red debt items feed AEI in C2), PLCF™ (the DXi feeds AEI), CORE™ (competency requirements), LEGATE™ (the ELS feeds CCR in C4)

Illustrative case

EuropaCo, a European industrial group (composite case): all five layers Red at baseline. At month 18, 34 platforms retired, integration patterns consolidated from 47 to 19, three layers Green and two Amber.

PLCF™ 02 / 06

Product Lifecycle Closure Framework

The deliberate, governed closure of products: detect decay, run retirement as a go-to-market event, make the cost of retention visible.

Problem addressed

Organisations have sophisticated disciplines for the inception, build and growth of products, and with rare exceptions no equivalent discipline for their closure. Technical debt compounds silently, applications in functional decay keep consuming support, licensing and compliance overhead, and the cost of maintenance crowds out investment in innovation.

Framework structure

Three interlocking instruments. The Product Decay Index (DXi) scores each product on five weighted dimensions and places it in the GREEN, AMBER, RED or BLACK band. Chargeback Mechanics activates at AMBER (DXi ≥ 3.6). The GTM Sunset Playbook opens at RED (DXi ≥ 6.0) and runs a four-phase sunset protocol, each phase with its exit criteria.

Value delivered

A quantified, repeatable end-of-life signal, a sunset programme that treats customers, data and regulatory obligations with the rigour of a launch, and a cost of debt made attributable to the business units that retain it.

Primary audience

Board or governance committee, CTO, DPO, business units

Documents provided on request

  • White paper Governing the End v2.12 (EN, FR)
  • DXi Diagnostic Tool v2.4
  • Write to the author to obtain them

Related frameworks

ECM™ (the DXi feeds AEI in C2), TDG™ (the Write-Off regime triggers sunset), VEGA™ (vendor exit), CORE™ (closure competency), LEGATE™ (governed retirement of agents)

Illustrative case

A global professional services firm (composite case), 340 applications: at month 18, five applications retired through the full playbook, annual run cost reduced by €2.1 million, run share of the IT budget down from 87% to 81%.

VEGA™ 03 / 06

Vendor & Enterprise Governance Architecture

Vendor portfolio design is an enterprise architecture decision.

Problem addressed

Organisations manage vendor portfolios as commercial inventories. Their composition determines the integration topology, the security surface, the distribution of critical knowledge and the resilience of the technology estate, and none of these properties is visible to procurement governance. Vendor-embedded AI adds model dependency and exposure under the EU AI Act.

Framework structure

A four-level maturity model: Fragmented, Rationalised, Architected, Resilient. Four axes scored out of 100 points (Architecture Coverage 30, Governance Depth 25, Regulatory Alignment 25, AI & Sovereignty Compliance 20) produce the Integrated Vendor Score (IVS): below 40, Level 1; 85 and above, Level 4.

Value delivered

A board-reportable IVS that feeds CRS in ECM™ layer C1, and architecture artefacts (dependency map, concentration risk register, jurisdiction profiles, exit protocols) that DORA, NIS2 and the EU AI Act now require.

Primary audience

Chief Architect, CISO, Head of Procurement Technology, CIO, board

Documents provided on request

  • White paper v2.8 (EN, FR)
  • VEGA IVS Diagnostic Tool v3.1
  • Write to the author to obtain them

Related frameworks

ECM™ (the IVS feeds CRS in C1), TDG™ (externally carried debt), CORE™ (competency dependencies), PLCF™ (vendor exit), LEGATE™ (classification of the harness vendor)

Illustrative case

A global scientific and medical information group (anonymised case), twelve countries: over 150 vendors reduced to 2 strategic partners and 8 specialists, 47 integration patterns reduced to 12 API interfaces, more than $10M in savings over 24 months.

TDG™ 04 / 06

Technical Debt Governance

A framework for enterprise-scale arbitration: technical debt remediation treated as a capital allocation decision.

Problem addressed

Technical debt has accumulated at enterprise scale for three decades without resolution: static analysis tools measure it, programme offices defer it, risk registers ignore it. Normalisation of deviance, the progressive redefinition of acceptable risk thresholds, sustains the accumulation, and incentives reward the addition of components and penalise their removal.

Framework structure

Three axes, Visibility, Arbitration and Regulation, produce three artefacts: the Systemic Debt Inventory (SDI), the Regime Assignment Register (RAR) and the Technical Risk Register (TRR). Debt is classified by three grains and four types: Foundational, Integration, Emerging Technology and AI-Generated Code. Each systemic item receives a regime, Remediate, Contain or Write-Off, or the Suspended Remediate state.

Value delivered

A Technical Risk Register for the audit committee in which each item carries a Principal Estimate, a Velocity Drag assessment, a Maturity Date and a named accountable owner: technical debt becomes a governed board commitment.

Primary audience

Enterprise Architecture Board, CTO / CFO joint committee, audit committee, board risk committee

Documents provided on request

  • White paper v2.11 (EN, FR)
  • TDG Diagnostic Instrument v2.1
  • Write to the author to obtain them

Related frameworks

ECM™ (AEI in C2, CRS in C1), PLCF™ (Write-Off triggers sunset), VEGA™ (externally carried debt), CORE™ (remediation capacity), LEGATE™ (agents deployed before their governance)

Illustrative case

Meridian Financial Services, a European financial institution subject to DORA (composite case): 23 systemic debt items inventoried. At month 12, the identity and access management remediation is complete and the DORA examination finding closed; the core banking middleware, in Suspended Remediate, has its capital case approved for the following year.

CORE™ 05 / 06

Competency and Organisational Resilience Equilibrium

Governing technology competency as depreciating capital.

Problem addressed

Most organisations treat technology competency as a stable resource whose value is assumed until it is unavoidably absent. It depreciates at market velocity, while its governance, owned by Human Resources, runs at annual rhythms. The risk register carries no entry for this exposure, and capital allocation decisions make no provision for it.

Framework structure

Three axes, Visibility, Arbitration and Regulation, produce the Competency Portfolio Inventory (CPI), the Treatment Assignment Register (TAR) and the Competency Risk Register (CRR). The taxonomy distinguishes three grains (individual, squad, portfolio) and one non-depreciating class, human judgment competencies. Each competency above the governance threshold receives a regime: Build, Source or Retire.

Value delivered

A Competency Risk Register for the board, alongside the financial and technical risk registers, that expresses exposure in capital terms: RAG status, quantified exposure and treatment owners.

Primary audience

Board, audit and risk committee, CTO, CHRO, programme sponsors

Documents provided on request

  • White paper v2.12 (EN, FR)
  • CORE Integrating Instrument v3.5
  • Write to the author to obtain them

Related frameworks

ECM™ (architecture mandates), TDG™ (debt treatment capacity), VEGA™ (vendor dependencies), PLCF™ (closure competency), LEGATE™ (competency of the people who supervise agents)

Illustrative case

Ardent Manufacturing Group, a European industrial conglomerate (composite case), €120 million transformation programme: four Critical Strategic Competencies Red. At month 18, two of the three delayed workstreams had recovered to within 5% of their original timeline.

LEGATE™ 06 / 06

Legitimacy Governance for Agent Task Execution

Governing the delegated action of autonomous AI agents, and the ageing of that delegation. An adaptation of the agent harness pattern.

Problem addressed

Autonomous AI agents now act inside enterprise systems: they pay, delete, send and deploy. The agent harness answers how an agent acts. It leaves three governance questions open: who authorised the delegation, who answers for its effects, and how long the authorisation remains valid. Delegation ages through permission creep, migration of oversight, model substitution and orphaned agents.

Framework structure

LEGATE™ takes up the agent harness pattern documented by LangChain, Anthropic, Microsoft, Salesforce and OpenAI and adapts it into a governance instrument, without adding any runtime component. Five components: Mandate, Boundary, Gates, Evidence, Interruption and Retirement. The unit of governance is the action class, ranked by autonomy level (A1 to A4, adapted from the AWS scoping matrix) and by reversibility class (R1 to R3, the framework's own construction).

Value delivered

A single board-reportable ratio, the Execution Legitimacy Score (ELS): the share of action classes in production that pass all five components, reported with five drift indicators. A single irreversible action class failing its human gate is enough to make the ELS Red.

Primary audience

Executive who owns operational risk, technology function operating the harness, audit or risk committee

Documents provided on request

  • White paper v1.2 (EN, FR)
  • Write to the author to obtain them

Related frameworks

VEGA™ (classification of the harness vendor), ECM™ (the ELS feeds CCR in C4), TDG™ (Type E and Type A debt), CORE™ (competency requirements), PLCF™ (governed retirement of agents)

Illustrative case

A European insurer (composite case), 31 agents and 18 action classes: ELS of 0.50, Red, at inventory. At month 6, 7 agents retired through governed closure, no R3 class left without a gate, ELS of 0.94, Amber under the DORA calibration.

Governance corpus

Each framework addresses one dimension of technology governance. The documents listed below are the versions current in October 2026.

LEGATE™

Legitimacy Governance for Agent Task Execution

Version 1.2  ·  Updated October 2026

An adaptation of the agent harness pattern: legitimacy of the action delegated to AI agents, measured by the Execution Legitimacy Score (ELS).

Documentation →

The documents are available on request. Write to the author

Would you like to read a framework in full ?

The whitepaper of each framework is provided by the author on request.

Write to the author