Your whole back office on one data layer.

The people directory, money accounts, and the activity trail — the operational spine every other interface reads from, on the one database you own.

One record

The lead, the candidate, and the contact are one record.

Dana Ruiz is one people row with identifiers, tags, and a timeline. Sales reads her as a lead, Hiring reads her as a candidate, an integration syncs her in from Gmail — all pointed at the same row. Change her once, it's changed everywhere.

urn_resolve · one URN, every surface

Money on the same layer

The money lives next to the people it moves between.

Money accounts and their transactions are ordinary records on the same database as your directory — so a payment links straight to the person, the org, and the deal, with no export to reconcile.

a transaction IS a Golden Schema row

The auto-ledger

Every state change writes itself to the trail.

Move a candidate a stage, log a payment, apply a tag — each writes an activities row automatically. Operations isn't a system you update; it's a running ledger of what actually happened, per record and across the workspace.

every state change → an activities row

Section audits

Audit every function — and no agent grades its own fix.

An agentic audit inspects each business function read-only and emits severity-ranked findings. 'Fix with agent' opens a task that travels the same ship / verify gate — so a finding resolves only when a different agent verifies its fix task done. Never self-attested. Kill switch and single-in-flight guard hold at the spawn point.

resolves only when a different agent verifies the fix

The back office runs on the same data as everything else.

People, organizations, money, and activity are one canonical directory — so operations isn't a separate system to reconcile, it's a view of the same records sales and hiring already use.

Bring your whole business home.

Download Excellent and run your whole business on your own machine.