Platform
The same jobs can be shared across propositions without running on the same machinery. Platform shows where that work actually converges in execution.
DTA uses a governed, computable model of the organisation to connect the work it must do with value, skills, authority, participants, decisions and evidence, so a change can be interrogated before you commit to it.
Your organisation already has systems of record for customers, money, people, technology, risk and work. What it lacks is a governed model of how those things constitute the organisation.
This is the chain the Transformation Intelligence page describes and the Accountable Bank is built on. Arrive from either and you will recognise it.
Shared work ≠ shared machinery ≠ shared consequence.
Several propositions can require the same job and fulfil it through different participants and services. Where that work converges onto one service is a fact about execution. What is harmed when that service stops is a fact about consequence. Platform shows the first two. Resilience shows the third. They need not agree, and where they disagree is the finding, not a defect.
That is the question a bank rarely gets to ask cleanly: what should be built once and shared, what should stay separate, and where a single service has quietly become the thing every proposition depends on.
One governed model, and six operations over it.
Derive the work. From customer need and proposition to the jobs the organisation must perform.
Select the participant. Human, agent, service, software or supplier, chosen after the job, its skills and its authority are understood.
Establish authority. Traceable to its source, bounded, and never confused with access.
Project the consequences. Which move, which hold, and which the organisation cannot establish.
Reconstruct from the intended outcome. Keep the genuine constraints; challenge inherited roles, systems, processes and boundaries rather than carrying them forward by default.
Show the evidence, including where the answer is absent.
One model. Many questions.
Architecture asks what depends on what. Value asks which outcomes justify the change. Capability asks what skills the work requires. Accountability asks who must answer for the consequence. They are not separate models. They are different questions asked of the same organisation. Each door on this site is one of those questions; follow it and you arrive at the same organisation, asked something different.
Not one database with many dashboards. Data asks what the work must know. Platform asks where it converges. Resilience asks what is harmed. Each is an authorised projection of the same governed Records, and they are allowed to disagree.
DTA uses this model as its instrument. It is not a product you have to buy.
Start with the organisation. Automate one job, and watch the consequences propagate.
Some things move. Some remain. Some the organisation cannot establish. The platform does not invent the missing answer.
This is the shape of the bank's Change page: apply a decision and the organisation is worked out again from the result, consequence by consequence, each one decomposed to the named organisational contributors behind it. Projections can disagree, and the disagreement is kept rather than averaged away.
An illustrative bank on synthetic data, built on the same model. Three ways in.
Customer need, then proposition, then jobs, then the organisation those jobs require. Follow one need into the bank and see the work it forces, what is shared, and who remains accountable.
Make a decision and see which organisational consequences move, hold or cannot be established, and why, down to the named contributors.
Platform, Data and Resilience. Different questions asked of the same organisation: where the work converges, what it must know, and what is harmed when something stops.
Inside the bank, the Platform lens is where this page's question is answered against an organisation you can interrogate. The Observatory asks a different question, what is changing outside the organisation, and its propositions are tested in the same model.
Open foundations
Underneath sit governed classes of Record. MTDR is one open recording grammar for one class, consequential decisions, and the Value Record is published beside it. Authority, obligation and inheritance are recorded as classes of their own. Client records and the open standards survive without us. Read what a decision record is, and is not.
We will show you what your existing models cannot tell you about its consequences.