Architecture Governance Platform

Log the routine decisions. Convene for the ones that matter.

A small, self-hosted system of record for architecture decisions - one place to write them down, request review on the ones that need it, and run standing ceremonies. Nothing to configure before it's useful; nothing to outgrow later. Built for a practice that's newly re-formed or still expanding, before its ways of working have settled into a fixed taxonomy - Business Areas, Domains, and Initiatives are all self-service, declared as the practice discovers it needs them.

Nine ways to write something down

ADR

One decision, recorded - the default unit. Log it and move on.

Principle

A standing rule the team would otherwise keep re-deriving from memory.

Reference Architecture

The shape of a solved problem, generalized for reuse.

HLD

The direction before the detail - a lighter design that earns sign-off before a full Solution Design is written.

Solution Design

What a new initiative actually brings to ARB - context, C4 diagrams, decisions cited rather than restated.

System

A catalog entry for a system this organization owns or depends on.

Integration

One integration point between two systems - protocol, data exchanged, criticality - the single place documenting it.

Data Model

Field-level data definitions and mappings - given their own home instead of buried in an HLD's numbered sections.

Target State

A short, living "where we're heading" statement for one Domain.

Review, sized to what's at stake

Not every choice needs an ARB slot. Draft it, and if it's routine, an ADR review is enough. If it's significant, cross-cutting, or precedent-setting, request Design Authority, ARB, or InfoSec alongside it - several can run in parallel. CAB signs off the deployment window; it never re-litigates the design.

And underneath all of it

  • Cross-artifact citation - link a design to the NFR Principles it complies with, and see every design that cites a principle back
  • An Integrations page indexes every Integration artifact and the two Systems it connects - still a flat list, never a dependency graph
  • Export a bundle of an artifact and everything linked to it as a zip - re-importable elsewhere, matched by title, never silently granting "approved"
  • Archive an artifact to declutter the default view - purely cosmetic, independent of status, reversible any time; admins control whether archived artifacts are hidden by default, live, under Platform Settings
  • Recurring ceremonies with real, auto-generated agendas - move one occurrence without disturbing the pattern
  • A full audit trail and keyword search across every artifact
  • Nothing is ever silently rewritten - every edit is a new version, and what was approved stays exactly what it was