A design system, and the Compliance OS it enables.
Charter is a design system: the atoms, molecules, and patterns drawn from a deep audit of the current Compliance Hub and a bold re-imagining of its tools and mechanisms. It is the vocabulary the Compliance OS would be built from.
How Charter came to be
A design system derived from the existing product, and a larger idea about where it leads.
We audited the Hub.
A full audit and inventory of the current Compliance Hub — every tool, document library, workflow, and alert. The aim was to catalog the real jobs, data, and surfaces: what members use, and what the platform already implies but doesn't deliver.
We reduced it to atoms, molecules, and patterns.
We organized what we found with an atomic model. Repeated elements are atoms — status, button, citation. Atoms combine into molecules — impact card, evidence chip, finding. Molecules combine into patterns — workflow runner, review queue, dashboard. The result is a small, reusable vocabulary.
The vocabulary covers more than a website.
That vocabulary is Charter. With one consistent language for status, evidence, workflows, citations, and permissions, the components compose into more than web pages — they compose into the surfaces an operating system would require. The rest of this page outlines that.
How it composes
Every screen in a compliance platform is a composition of these four levels, from a single control to a full surface.
Status, button, badge, citation, input, avatar.
Impact card, evidence chip, finding, confidence bar.
Workflow runner, review queue, dashboard, radar.
Today, Program home, Manager portfolio, exam binder.
Composed consistently and far enough, the same vocabulary covers what an operating system for banking compliance would require. One possible shape follows.
The operating system it could enable
If Charter were composed all the way up, this is one shape it could take: a regulatory-data kernel at the base, services and apps above it, agents throughout, and the people it serves on top.
Who it could serve
Roles a platform built on this vocabulary could support.
A single view of the institution's posture, risk, and evidence — board- and exam-ready.
Runs multiple member banks from one interface — the model behind CA staff augmentation.
Day-to-day work, guided step by step, with evidence captured as they go.
Publishes regulatory updates, tools, and templates to member banks directly, as rules change.
Drafts, gathers evidence, and monitors changes across the platform — cited, measured, and deferring to a human.
The boundary where regulatory information becomes legal advice; escalation and review.
What becomes possible
Capabilities a coherent platform could support.
Continuous monitoring
Track regulatory changes centrally and route only what applies to each bank.
Agentic workflows
Agents draft, gather evidence, and prepare filings; people review and decide.
Expertise at the speed of change
CA guidance and tools reach member banks as rules change, not on a quarterly cycle.
Multi-bank command
Run portfolios of institutions from one consistent interface.
Always exam-ready
Audit trail and evidence assembled continuously, so exam prep is ongoing rather than an event.
An ecosystem
A shared foundation for additional compliance apps, from CA and trusted partners.
Charter is the design system. A comprehensive OS for banking compliance is the vision it enables.
Built once and shared across the institution, Compliance Alliance, its agents, and counsel — so a small compliance team can operate like a larger one.