Every architect has opened a system they did not build and asked the same question: why is it like this?
Why does the order service write to two databases? Why is there a nightly file transfer where an API would be the obvious choice? Why was the authentication exception granted, and was it ever meant to be permanent?
The answers existed once. They were in a design review eighteen months ago, in a risk the project accepted, in a decision three people made on a call. Then the project closed, the team moved on, and the system stayed. The reasoning did not stay with it.
This is the most common way architecture governance fails, and it has nothing to do with the quality of the reviews. The reviews were fine. They were attached to the wrong thing.
Projects Are Temporary. Applications Are Not.
Governance work is organised around projects because that is where change happens. A project proposes something, it is reviewed against your architecture directives, findings are raised and resolved, and the project completes.
But a project is a few months long. The application it delivers may run for ten or fifteen years, and will be touched by many projects in that time. Each of those projects starts by rediscovering what the last one knew.
Figure 1 — Three projects, one application. The governance record should belong to the long bar.
If the decisions, documents and open risks live on the projects, then after Project A closes they are in an archive nobody opens. Project B's team does not know that a high-severity finding was deferred, or that a deviation from the encryption directive was accepted for a reason that no longer holds.
The fix is not better project documentation. It is giving the application its own record, and making projects contribute to it.
What an Application Is in cajeX
Applications is a register of the IT applications in your landscape. It is not a portfolio-management tool. A portfolio tool asks what you have and what it costs. cajeX asks a governance question: what is this application held to, what was decided about it, and what is still open?
Each application carries the facts governance needs.
Sourcing
Custom-built, off-the-shelf, SaaS, or hybrid.Form factors
Web, mobile, desktop client, API, batch. As many as apply.Hosting
SaaS-hosted, cloud, on-premises, or hybrid.Lifecycle
Plan, build, operate, phase-out, retired.Criticality
How much the business depends on it.Data classification
From public through to regulated.Figure 2 — Three classification axes and three governance facets on every application.
These are not decoration. They decide which rules apply. An application handling regulated data, rated business-critical, is governed differently from an internal batch job, and cajeX uses these facets to work out which of your enabled frameworks are relevant to it. It shows its reasoning for every match, and lists the frameworks that did not match as well, so nothing is hidden. cajeX recommends; you decide.
You do not have to type the register in. On any project, the AI can read the description and document list and propose the applications that project builds or changes, already classified, each with a one-line reason. If a proposal matches an application you already have, cajeX offers to link the existing record rather than create a duplicate. Nothing is saved until you accept it. For a team with a year of project history already in cajeX, this is the fastest way to a first register.
How a Project Feeds the Application
A project links to the applications it touches, with a role that says what it does to each: builds, changes, integrates, or decommissions. That link is what gives the application its history. Open an application and its Projects tab lists every project that has touched it, and how.
Builds
The project creates the application
Changes
It alters an application that exists
Integrates
It connects to it without changing it
Decommissions
It retires the application
Figure 3 — The four roles a project can have towards an application.
From there, four things flow from the project to the application.
Decisions
Recorded on the applicationDeviations
Become tracked findingsOpen findings
Transfer at completionDocuments
Handed over, with reasonsFigure 4 — What a project leaves behind on the application it changed.
Decisions
Each application has a Decisions tab holding its architecture decision records. A decision captures the context, the choice and its consequences, numbered per application. Decisions are usually made during a project, so each one can name the project it came from. But it belongs to the application, because that is where the next team will look.
A decision starts as proposed. Once accepted it cannot be edited. If the decision changes later, you supersede it with a new one and the chain stays visible.
Deviations become findings
This is the part we care most about. While drafting a decision, you link it to the directives it touches and say how: it complies with the directive, or it deviates from it, with a justification you must write.
When you accept a decision that deviates, cajeX raises a finding on the application automatically. A deviation is then a tracked exception with an owner and a due date, visible on the application's risk register, rather than a paragraph in a document that reads as settled.
ADR-0007 accepts a nightly file transfer to the warehouse system in place of an event stream, until the warehouse platform is replaced.
Figure 5 — An accepted deviation, raised as a finding on the application so it is reviewed again.
If that decision is later superseded or deprecated, the findings it raised are flagged for another look. The exception does not quietly outlive its reason.
Findings that should not close with the project
Some findings describe the change. Others describe an enduring property of the application: technical debt, an accepted risk, a non-conformity nobody had time to fix. Those can be transferred to the application, with their full history.
To make this real, a project cannot be marked complete while it still has open findings. Each one has to be closed, rejected, deferred, or transferred. It is a small rule with a large effect: nothing is lost at the moment a project ends, which is exactly when things used to be lost.
Documents
When a project with linked applications completes, cajeX offers a document handover. Each document gets a destination: stay on the project, or move to an application. The AI can suggest where each belongs, with a reason per document. The rule of thumb is simple. A document that describes the change stays with the project. A document that describes the application as it now is, an architecture overview, a runbook, an interface catalogue, moves to the application.
The step can always be skipped, and nothing moves without your confirmation.
A Worked Example
A retailer runs an order management system. Two projects touch it in a year.
| Without an application record | With one | |
|---|---|---|
| Project A completes | Two findings deferred. A deviation noted in the design document. Project archived. | Two findings transferred to the application. The deviation is ADR-0007, with a finding against it. Architecture and runbook handed over. |
| Project B starts | The team reads the code and asks around. | The team opens the application: seven decisions, two open findings, the current architecture, and the frameworks that apply. |
| Project B is reviewed | The AI review flags the file transfer as a nonconformity again. | The review recognises ADR-0007 as a governed exception and refers to it instead of raising the same gap twice. |
| An auditor asks | Evidence is reconstructed from two project archives. | The application shows its decisions, its exceptions, and its open risks in one place. |
Figure 6 — The same two projects, with and without a durable record on the application.
The third row deserves a note. An application can be reviewed in its own right. Where a project review evaluates the documents of a change, an application review evaluates the application's current documented state: its living documents and its accepted decisions. A deviation already recorded in an accepted decision is treated as known, unless the documentation shows it has grown beyond what was agreed. By default the review covers the directives you have linked to the application, plus those of every framework that matches its facets, and the dialog shows where that scope came from before you start.
Run one after a handover, or every quarter, to check the documented state still holds.
The Honest Edges
Applications that connect to systems outside your governance, a partner's platform, a vendor system nobody in your organisation owns, need those connections recorded honestly. cajeX lets you register such a system as external: a stub that exists so the interface can be drawn, badged as external, carrying no governance data and never appearing in conformance views. It would be easy to pretend those systems are governed. It is more useful to show where your governance stops.
And this is not an enterprise architecture repository. If you already run one, cajeX sits beside it. We wrote about that division in why we built cajeX and what EA tools don't do: the EA tool holds the map; cajeX holds the rules, the reviews and the evidence.
Turning It On
Applications is off by default. A workspace owner or admin turns it on under Settings → Features → Applications, and the Applications screen appears for everyone in the workspace. It can be turned off again the same way; the data is kept.
If you turn it on with projects already in cajeX, start by generating applications from two or three completed projects and looking at what the AI proposes. The register that results is small, but it is the first version of an answer to the question every architect eventually asks of a system they did not build.
Why is it like this? Now the application can tell you.