A client asked us to build a regulated financial services estate on Technology DNA, with no off-the-shelf core system underneath it. This is the heaviest set of obligations we have carried. The client permits us to describe our engineering practice. The client withholds their name, their business model and their product design, and those items cover some of the most complex parts of the build. This page describes the part that transfers to any organisation with heavy obligations.
One division runs through the estate. Technology DNA supplies the machinery that every application inherits by contract, and the client's own rules sit on top as application software.
The DNA runs on engage.re, in production since December 2025. On the Technology Readiness Level scale used by Horizon Europe and Innovate UK, it sits at Level 9. It supplied the following on day one.
Read Technology DNA in full on the engage.re project page.
A regulator asks for orderly records, held for years, in a form that lets it reconstruct each stage of a transaction. This estate meets that by construction instead of by procedure.
Every material decision writes a decision record, and that record carries its reviewer, its rationale and its case linkage. Where software assists a decision, it records its version, its inputs and its outputs as signed events, so any assisted decision reproduces by replay. No adverse decision completes without a named human reviewer.
The estate audits read access at institutional volume. Staff access to a customer file is answerable per customer: when, who, and under which authority. Full detail is retained for writes, for denials and for sensitive scopes.
Every record class carries a declared retention class. The platform refuses deletion before expiry, and it records the release at expiry. A legal hold suspends deletion outside any schedule, under recorded authority. Accelerated-clock tests verify the enforcement logic, so a long-horizon rule proves itself now.
Connect with us about your project. Message on WhatsApp Replies within 24 hours
A regulated firm's permissions change shape as it moves through authorisation. This estate encodes that journey.
A stage record gates every service line in the server, and the operations team switches a service on at exactly the tier the regulator has approved. Where a stage carries a numeric constraint, the server enforces that constraint at the point of action and displays the remaining headroom.
A move up a tier is a ceremony rather than a setting. Two authorised officers must act separately, and they attach the authority document itself as evidence. The estate records every change with who, when, and under what authority.
One read-only screen then shows every service line, its current stage and mode, the evidence reference, the next milestone, the remaining headroom and the full transition history. The firm and its supervisors can see every live service line on one screen.
Figures that regulation moves are configuration rather than code. One value renders everywhere, so a change in the rules becomes a data change.
Switching a service on is half of readiness. The other half is switching it off mid-operation, with customers in the loop.
Each service line carries a service mode alongside its stage: open, closed to new business, run-off, or suspended. A reduction in service takes effect immediately on one authorised instruction, with the reason recorded. A restoration requires the full two-officer ceremony. A requirement to stop new business therefore takes effect, and produces its evidence, within minutes of receipt.
No mode at any stage can block one protected class of operation. That class covers a customer's access to their own money, their own records, their complaints and their rights. The software cannot cut a person off from what belongs to them.
Every reduction in service also opens a transition workbook. That workbook lists the customers in flight and applies recorded dispositions, each with its communication. The estate abandons nothing, and every disposition leaves a record.
Each obligation with operational content runs as enforced workflow instead of sitting in a procedures manual.
A regulator asks a firm to monitor and evidence the outcomes its customers receive, and to find any group receiving worse outcomes. This estate measures that from live records instead of assembling the figures from management reports.
Every figure computes from live records, segmented by product, by area and by vulnerability, and every figure drills to the exact records it counts. A deterministic test estate with known expected figures verifies the measurement machinery.
The board report composes from the same queries that the dashboards run, so an assessment is a dated reading of live data. A group faring worse becomes visible directly, because the platform counts every change exactly at every level of aggregation.
The estate registers its important business services with impact tolerances, and it generates dependency mapping from the platform's own architecture documentation. Scenario test results become records with owners and due dates. Incident management runs as a workflow, and a notifiable incident cannot close without a post-incident review.
Drills produce the recovery time and recovery point figures. Each figure states the deployment and load of its measurement, and it cites the drill run that produced it. Because the signed chain is the record, a restore verifies itself: the recovered store replays and matches.
The target deployment is a single-tenant instance of the graph in the client's own estate. The client's data sits under the client's keys, hosted where the client chooses, and no standing vendor administrative access exists. Sense Future signs and versions each engine release, and a published conformance suite proves a deployment correct.
The estate also deploys at any point in the authorisation journey. Stages and modes govern what a customer can reach, and the deployment itself governs nothing. A deployed system with every line switched off is a compliant, inert system.
Every capability carries named acceptance tests. Every phase closes with a proof suite and a signed report. The security properties re-prove themselves continuously in production.
We build this class of estate for organisations outside financial services, and the mechanisms carry across unchanged.
A stage record and a protected operation class are general mechanisms. So are an enforced register, a notice clock, a daily reconciliation, an accountability register and a scoped regulator capability. Your sector's rules supply their content.
A care provider, a school, a charity, a recruitment agency and a local authority all carry obligations of this shape. The record, custody, access, erasure, retention, audit and exit disciplines that consume compliance budgets are properties of the graph, and Sense Future maintains them once for every participant. Your own obligations then ride on top as application work.
We build that work at whatever weight your obligations need. Where we build it wrong, we fix it at no cost and with no time limit, and the contract says so.
React 18 · TypeScript · Vite · Node.js · engage.re Graph API · Key-based authentication with session timeout · Monorepo (pnpm workspaces)