Get started

The CLI

Source

Everything an operator does to the record is a command, run from a checkout with the environment sourced. There is no admin UI, and that is a property of the design rather than a gap.

Why the record is operated and not administered

Every write that changes what the record says is an act with a person behind it, made through a role that holds the privilege. Every UPDATE grant in this database is column-level and there are two in aperture: the collector marks a trigger fired, and the console records a ruling on a decision. Neither witness nor aperture grants DELETE at all.

So there is no endpoint that could quietly accept a decision. The one endpoint that accepts one is /console/rule, it does nothing quietly, and it cannot touch a decision's outcome, thresholds, inputs, reason or brief, because those columns are not in its grant. Everything else about the register is entered at a prompt, as the owning role, which is what the rest of this page is.

The families

FamilyCountWhat it touches
`witness:*`5The record: seeding, collecting, replaying, signing, publishing rates
`event:add`1The market log
`sku:*`4The discovery queue
`aperture:*`24Workloads, evidence, triggers, decisions, compound pipelines, audit packs, fallback chains and rules
`org:*`, `auth:*`4Which orgs exist and who may read /console
`org:key:*`2Who may land a reading over the network
`db:*`2Migrations
`scripts/`5Mirrors and tooling

Shared conventions

A dry run writes nothing. --dry-run where offered, and several commands report rather than write unless given --yes.

A verify recomputes. --verify on the signing and rate commands recomputes every row ever published and reports disagreement rather than trusting.

Refusals name the row. A command that cannot do what it was asked says which input it refused and why, rather than doing part of the job.

Nothing invents data. A command with a missing credential or an unreachable source fails and says so. It does not fall back to a plausible number.