Documentation
The cajeX user guide, chapter by chapter. It is the same guide the in-app assistant answers from.
Using cajeX
- Welcome to cajeXcajeX is an architecture governance platform. It helps your team turn unstructured architectural knowledge — standards documents, policy PDFs, whitepapers, Confluence pages — into approved directives, then applies those…
- Getting startedcajeX supports several ways to sign in, in this order of…
- DashboardThe Dashboard is your workspace's governance scorecard at a glance: counts of what is active and what is overdue, how findings are trending, how your directives are holding up, and what is on the calendar. It is the…
- Knowledge BaseThe Knowledge Base (KB) is where your raw architectural material lives: standards, policies, whitepapers, reference architectures, internal best-practice notes. Put in anything an architect would consider authoritative…
- DirectivesDirectives are the centre of cajeX. A directive is one approved rule: short, specific, and checkable. The AI applies your approved directives when it reviews a project or an application, and every finding points back to…
- ProjectsA project is anything you'd take to architecture review — a service proposal, an integration design, a data pipeline, a platform change. Projects in cajeX hold the proposal artefacts (text, diagrams, attachments),…
- AI ReviewAI Review is the cajeX AI Co-Worker applied to a governed subject. It comes in two flavors that share one engine: Project AI Review (this chapter) reads a project's artefacts — the documents of a change — while…
- Sessions and CalendarA session is a scheduled, structured architecture review. Each session is built from a workflow template — Governance Standard, Agile Sprint, or Minimal Review — that defines the phases, the participants, and the gates…
- FindingsA finding records that something about a project or an application does, or does not, follow one of your rules. Findings come from three…
- DocumentsDocuments is your workspace's file browser across everything. Each file uploaded to a project, an application, a session, a finding or a knowledge base entry is listed here, so you can find it without remembering where…
- ReportsReports turns your governance record into something you can hand to someone: a report card for a project, and a clause-by-clause compliance report for a framework. Both are built from the live findings, directives and…
- ProfileYour profile holds your account details and your personal preferences: how cajeX looks, which language and time zone it uses, and which emails it sends you. Open it from your initials at the top right of the…
- FrameworksFrameworks are the published standards your governance program is measured against — ISO 27001, SOC 2, NIST CSF, and hundreds of others. The Frameworks screen is the catalogue: it lets you browse the available…
- ApplicationsProjects come and go — the applications they build or change live on. The Applications screen (an optional feature — see Availability below) is a registry of the IT applications in your landscape: what each one is, how…
- DiagramsDraw and maintain architecture diagrams inside cajeX, stored as project documents instead of screenshots on someone's laptop. Diagrams (see Availability below) use the built-in draw.io editor, self-hosted by cajeX so…
- Custom FrameworksThe Frameworks catalogue is cajeX's curated set of published standards — ISO 27001, SOC 2, NIST CSF, and hundreds of others. Custom Frameworks (an optional feature — see Availability below) is different: it's a way to…
- RequirementsA requirement is what a solution has to do. Requirements are where a project stops being a description of work and becomes something a supplier can be held to, and something a design can be judged…
- DesignThe Design tab on a project holds the candidate solutions you are evaluating — a vendor's proposal, another vendor's, or building it yourself — and the architecture views that describe each…
- Tests and verificationA requirement says what the solution must do. A test is how you prove it…
- Evidence (beta)Evidence reads the systems an application runs on and records what it found against its directives, for a person to decide on. Four rules…
Running a workspace
- Workspace AdminThis chapter covers everything in the Settings area that a workspace admin can do. Owners can do all of this and the items in the next chapter; reviewers and members can see most of these tabs in read-only…
- Workspace OwnerThere is exactly one Owner per workspace. The Owner can do everything an Admin can do (see the previous chapter) and three more things, all of which are load-bearing: getting them wrong is costly to recover from. This…