Skip to content
Back to Blog
Product Updates

Applications That Say What Needs Attention, and Who May See Them

Shi YanOctober 22, 20269 min read

An application register has two ways of failing, and neither is dramatic.

The first is that it goes quietly out of date. Nobody decides to stop maintaining it. An interface still points at a system that was retired in the spring. A decision record still says "accepted" for a design that was replaced. The architecture document was last reviewed two years ago. Each entry looks fine on its own. Together they mean the register describes a landscape that no longer exists, and people stop trusting it.

The second is that it shows too much. Some applications are sensitive by their nature: a system under acquisition due diligence, a fraud-detection platform, a programme not yet announced. If recording such an application means the whole workspace can read its findings and its architecture, the people responsible will simply not record it. The register then has holes exactly where governance matters most.

In July we introduced Applications as the durable home for what a project leaves behind. This post covers two additions that deal with those two failures.


Part One: Confidential Applications

A project in cajeX could already be confidential. An application now can be too, and the rule is the same and deliberately strict.

A confidential application is visible only to its team: its managers and members. That includes everything under it, its documents, requirements, designs, findings, decisions and reviews. Workspace owners and admins who are not on the team do not see it either.

Owner
Accountable for the application. Always a manager. Chosen from the workspace's members.
Managers
Add and remove people, change the owner, set confidentiality.
Members
Work on the application and see everything under it.

Figure 1 — An application's team. For a confidential application, nobody outside it can see in.

That last point surprises people, so it is worth explaining. In many tools "confidential" means hidden from ordinary users and visible to administrators. That is convenient and it defeats the purpose. The person running the workspace is rarely the person who should read a due-diligence finding. Confidential in cajeX means the team, and only the team.

Confidentiality has to hold everywhere

Hiding an application from a list is the easy part. The real work is every other place its contents could surface.

What someone outside the team seesWhy it matters
The Applications listNothingA name alone can be the secret
A project that links to it"A confidential application"The link is real and honest; the identity is withheld
SearchNo results from it, including documents attached to its findingsSearch is the commonest accidental leak
The assistantNo mention, even when asked about the workspace in generalThe assistant sees only what the person asking may see
The audit logA placeholder in place of names and textWho did what and when stays; what it was about does not
Counts and totalsNot includedA tab that says "3" when you can see 2 tells you something

Figure 2 — Six places a confidential application could leak, and what each shows instead.

We found and fixed gaps of exactly this kind in confidential projects while building it, and applied one access rule to both. A confidentiality feature is only as good as its least obvious surface.

Handover does not widen access by accident

The risky moment is when a project completes. A confidential project hands its documents, requirements and people to an application. If that application is public, confidential material has just become visible to the workspace.

So the handover asks first. When a confidential project hands over to a public application, you choose: make the application confidential too, or promote the material as public and confirm that you mean it. Nothing becomes visible to the whole workspace without that choice.

Completing a project now hands over its people as well: the application owner, and which of the project's managers and members join the application's team. An application generated from a confidential project is created confidential, with the project's team.

If you do not manage the application you are handing over to, the changes to its owner, team and confidentiality go to its managers as a request. They accept or decline each line. One team cannot rearrange another team's application by closing a project.

Project completes
Confidential, with its team
→
cajeX checks
Is the application public?
→
You choose
Make it confidential, or confirm public
→
Managers decide
If it is not your application

Figure 3 — A handover never makes confidential material public as a side effect.


Part Two: Needs Attention

Now the other failure: the register that goes stale.

Each application's Overview has a Needs attention section. It appears only when something needs fixing, and it lists three kinds of drift. None of them needs an integration or a scanner. They are all things the register already knows and had not been saying.

Lifecycle mismatch

An interface to an application that is being phased out or is already retired.

Out-of-date decision

A decision record still marked accepted after the design it records was replaced.

Stale document

A living document due, or past due, for review.

Figure 4 — Three kinds of drift, each visible from data the register already holds.

An interface to something that is going away

Take a billing application with an interface to a customer-master system. The customer-master system moves to phase-out. Nothing about the billing application changed, and yet it now has a problem: it depends on something with an end date.

Both applications now say so, whichever way the data flows. If a project is already decommissioning the retiring system, the item names that project instead of asking you to act, because the work is in hand and the useful information is who has it.

A confidential application or project you cannot see is never named in one of these items.

A decision that outlived its design

Decision records are valuable because they are stable: once accepted, they cannot be edited. The cost of that stability is that a decision can go on saying "accepted" long after the design it describes has been superseded.

Needs attention lists such a decision, names the design that replaced the one it records, and says what is no longer in the architecture. Marking the decision superseded or deprecated clears the item. The record stays in the chain; it just stops claiming to be current.

A document nobody has looked at

An application's documents can now say what kind they are: architecture, runbook, API specification, readme, changelog, or other. Each kind has a review interval that reflects how quickly it goes wrong.

Changelog
30 days
API specification
60 days
Runbook, readme
90 days
Architecture
120 days

Figure 5 — Review intervals by document kind. An API specification goes stale faster than an architecture overview.

A document due or past due appears under Needs attention. Marking it reviewed, or uploading a new version, clears it.

The intervals are short on purpose. A runbook that was right three months ago and has not been looked at since is exactly the document that fails you during an incident.

These are not findings

We made one deliberate choice here. A Needs attention item is not a finding. It has no severity, no owner and no due date, and it cannot be dismissed.

A finding is evidence about a rule: a directive was checked and something did not conform. Housekeeping is a different thing, and mixing the two would bury real nonconformities under reminders to review a readme. So an item stays until the thing it describes is fixed, and then it goes away by itself. There is nothing to triage.

The Applications list carries a count, so you can see which applications need attention without opening each one.


Why These Two Belong Together

They look unrelated. One is about access, the other about freshness. What they share is that both decide whether the register can be relied on.

A register people work around


  • Sensitive applications left out
  • Interfaces to retired systems
  • Decisions that no longer describe anything
  • Documents nobody has opened in a year
becomes

A register people rely on


  • Sensitive applications recorded, seen only by their team
  • Lifecycle mismatches named on both sides
  • Superseded decisions flagged
  • Review dates that mean something

Figure 6 — What it takes for an application register to stay worth opening.

A register that omits the sensitive systems cannot answer a question about the whole landscape. A register that is silently out of date gives confident wrong answers. Either way, people go back to asking a colleague, and the governance record becomes something maintained for auditors rather than used by architects.


Getting Started

Both features are part of Applications, which a workspace owner or admin turns on under Settings → Features.

To make an application confidential, a manager uses the lock in its header. Check the Team section first: once it is confidential, only the people listed there can open it.

Needs attention needs no setup. Open an application that has been in the register for a while and look at its Overview. If the section is not there, nothing has drifted. If it is, the first item is usually a document nobody has reviewed since the project that wrote it closed.

For the rest of what an application holds, see the product overview.

Ready to transform your architecture governance?

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