🝧
The platform

"Accountable" — and here's exactly how.

Everywhere else on this site, we keep the language plain: an intelligence team for your business, accountable by design. This page is where "accountable" gets specific.

Everything we deliver runs on two things.

Your business memory — the organized record of what your company knows, kept usable and kept yours. And the operating system that runs on it — the governed platform that acts on that record. Internally we call that operating system DOMINION; mostly we call it what it is. It runs our company today — the strategy, the research, the operations, the page you're reading. We were our own first client.

The analysis we sell is only as trustworthy as the platform that produces it. You don't have to take our word for how the work gets done. This page is how you check.

Four controls that make "accountable" mean something.

Permission levels

Every action is classified before it happens: what an assistant may do on its own, what it does and then reports for verification, and what waits for approval. The levels are enforced by the operating system — not a policy the model might ignore — and you decide where the lines sit for your business.

Sign-off

Anything high-consequence — anything that spends money, commits you, or reaches a client — waits for your explicit yes, item by item. Your sign-off is recorded alongside the work it approved, so "who said go" is never a reconstruction.

Hard limits

Some actions are refused by design, no matter who asks or how the request is phrased. In real estate, our research assistant works from the criteria a buyer actually names and refuses demographic steering outright. In legal, the line is the unauthorized practice of law. Hard limits sit above the permission levels; they survive a clever prompt.

Receipts

Every action leaves a receipt on a tamper-evident, append-only record: what was done, when, and what it was based on. Editing a past entry is mechanically detected and blocked; corrections are visible new entries, never silent edits. "What did it do?" always has an answer you can show — to a partner, a broker, an examiner.

And the rules behind all four are change-managed, not just present. Every change to the governance runs a witnessed lifecycle, and the rule-set is sealed and checked daily against its baseline. The controls can't be quietly edited any more than the record can.
🝧

We don't quote stale counts.

These figures refresh from the live record before every publish.

409 actions on the record since April 2026, every one with a receipt, full chain verified
18 sealed rule files, matching baseline ce879a6
Most recent full-chain integrity verification: 2026-06-12

Refreshed before each publish

The same candor we hold internally — because it is the differentiation.

Hard blocking, highest-stakes first

Hard blocking covers the highest-stakes zone today: the governance rules themselves. Changes there are refused outright. Other restricted zones are checked daily and flagged rather than blocked at the moment of write. Full hard gating across every zone is on the roadmap.

Single-tenant today

Multi-tenant isolation is groundwork in progress, not shipped. We will not claim tenancy controls we haven't built.

Tamper-evident, not tamper-proof

The protection is detection, a witnessed chain, and history — not cryptographic hardware. Cryptographic signing is a roadmap item.

If a control isn't on this page, treat it as roadmap. We are built around the controls SOC 2 and ISO 42001 require — audit-ready by design, not certified yet; certification is on our roadmap. We say exactly where we are, and nothing more.

Ask us to walk you through the record.

The four controls above, run live, on the operating system that runs our own company.

Request a walkthrough
Take the collateral with you
  • Plain-English guide to your business memory Coming soon
  • Governance & compliance explainer — for the risk officer Coming soon