Skip to content
Back to Blog
Product Updates

We Said We Would Build It: Conformance, From the Directive to the Application

Shi YanSeptember 8, 20267 min read

In June we published a short note called What we're building next: findings that prove your directives. It made one argument: a finding is not a defect in a project, it is a measurement of whether a rule is being followed. The data to show that already existed in cajeX. It had simply never been brought back to the rule it belonged to.

This is the follow-up. The loop is closed, and it now runs one step further than we described in June, out to the application that has to keep conforming after the project is gone.

If you are new to the idea of a directive, start with What Are Architecture Directives and come back.


The Question a Head of Architecture Actually Asks

Nobody responsible for architecture governance wants to know how many open findings there are. That number goes up when you review more, which makes it a measure of effort rather than of health.

The questions that matter are about rules:

  • Which of our directives are holding, and which are being broken repeatedly?
  • When did we last check?
  • Is a failure a one-off in one project, or the same gap in six?
  • For this application, running in production today, what does it have to conform to, and does it?

A flat findings list cannot answer any of these, however well it is filtered. Each one needs the finding to know its rule, and the rule to know its findings.

A findings list answers


  • What is wrong in this project?
  • Who owns it and when is it due?
  • How many are open?
conformance adds

Conformance answers


  • Is this rule being followed?
  • Where is it broken, and how often?
  • What must this application conform to?

Figure 1 — The same findings, read from the project and read from the rule.


What Shipped

Four things, in the order a finding travels.

Finding
Shows its directive
→
Directive
Shows its conformance
→
Dashboard
Ranks directives
→
Application
Shows what applies, and whether it holds

Figure 2 — Conformance at four levels, all read from the same findings.

On every finding: the rule it is about

Each finding now names the directive it maps to, in the list and on the detail, one click from the directive itself. Where the directive came from a framework, the finding carries the whole trail: framework, clause, directive. A reviewer looking at "customer data stored unencrypted in the staging bucket" sees at once that this is a non-conformity against your encryption-at-rest directive, which exists because of a specific clause in a specific regulation.

Nonconformity High severity

Customer exports are written to object storage without encryption at rest.

Figure 3 — A finding with its trail: the framework, the clause, and the directive it is evidence about.

On every directive: its own evidence

A directive shows a conformance status, worked out from the findings raised against it and the verdicts of the latest reviews: conformant, partially conformant, non-conformant, or not yet evaluated. Beside it sit the open findings by severity and the projects they touch.

The status is computed when you open the directive. It is not a stored number that something has to keep in step. We made that choice in June and have kept it everywhere since: a governance status that can drift from reality is worse than no status at all.

On the dashboard: where attention should go

Two views now sit on the main dashboard. Directive Conformance shows how the approved directive set divides across the four statuses. Top Directives by Open Findings names the rules that are collecting the most trouble.

The second one changes conversations. A directive with eleven open findings across seven projects is rarely seven teams being careless. More often the rule is unclear, or the paved road it assumes does not exist yet. That is a finding about your governance, and it is the one the architecture team can actually fix.

One project, one finding

A local slip. Fix it in the project and move on.

Many projects, one directive

A systemic gap. The rule, or the platform behind it, needs work.

No findings, never evaluated

Not conformance. Nobody has looked yet, and the status says so.

Figure 4 — Three patterns that look identical in a flat list and are obvious from the directive.

On the application: what must stay true

This is the step June did not promise. Projects end; the applications they change keep running, and keep having to conform. For workspaces that have turned on Applications (Settings → Features), each application now has a Conformance tab.

It shows the frameworks that apply to this application, from the ones your workspace has enabled, and it explains every match: this framework applies because the application's data classification is regulated, for example. Frameworks without a match are still listed, ranked lower. cajeX recommends and explains; the decision about what governs the application stays with you.

Below that are the directives you have linked to the application, each with its open findings and any recorded decision that complies with or knowingly deviates from it. A deviation accepted in an architecture decision record raises a finding on the application automatically, so an exception is a tracked item rather than a sentence in a document.

Once a project has handed its architecture over, the tab answers two further questions. How many elements of the architecture have a requirement attached, with the ones that have none named individually. And how the application's standing requirements are doing against their tests, where verified means every linked test actually passed.

BeforeNow
A findingSeverity, title, project, statusAlso its directive, and the framework clause behind it
A directiveA written ruleA rule with a live conformance status and its open findings
The dashboardCounts of findingsConformance across directives, and the directives in most trouble
An applicationA record of what existsWhat it must conform to, why, and whether it does

Figure 5 — What each level shows now that the loop is closed.


What We Have Not Built

June's note ended with trends over time: whether a control is getting better or worse. That is not here yet. Today you see the current state, computed fresh, and the history of each finding. A conformance trend per directive is the natural next step and it is the one we are asked for most.

We would rather say that plainly than let a dashboard imply more than it knows.


Why "Conformance"

The application tab was first called Posture. We renamed it. Posture is a security-vendor word and it described the wrong thing: the tab is mostly about what applies to an application and why, not a risk stance. Conformance is the word architects already use, and it covers both halves of the question, what must this conform to, and does it.

It is also the word that keeps the product honest. A posture can be asserted. Conformance has to be shown, against a named rule, with evidence you can open. For how the same idea plays out when several regulators ask at once, see one technology review as evidence for every regulator.

A finding was always evidence about a rule. The product now treats it that way at every level, from the single finding to the application that has to live with the result.

Ready to transform your architecture governance?

cajeX brings AI-powered reviews, knowledge management, and directive lifecycle management to your enterprise architecture team.