Public ledger · unauthenticated

StoneAI governs StoneAI

We sell a decision record: sealed, signed, and chained. It would be convenient to keep our own operator actions off the record. We don't.

StoneAI runs as its own tenant. The operator actions that change the platform — suspending or restoring a customer account, changing a plan's price or limits, configuring a payment processor — go through the same self-governance path, and each one is written to StoneAI's own hash-chained audit ledger: the same ledger design our customers get, where the database refuses edits and deletions. For payment processors, only the names of the fields that changed are recorded — never a credential value.

What is enforced today

Two modes, set by the operator. We state which does what, precisely.

ModeBehaviour
log (default)The action runs immediately, then is recorded on the ledger. This is a record, not a gate: it proves what was done, not that it was approved first.
strictThe action raises a real decree and waits. It runs only after an Ed25519-signed approval verifies against the decree's content hash. Limitation: a queued action is held in memory, so a service restart discards it and it must be issued again.

In strict mode the approval is signed by StoneAI's server-held key for its own tenant, on behalf of the named approver.

The self-governance ledger

Live from GET /v1/governance/public — no login. Shows the most recent 100 entries on StoneAI's own ledger, unfiltered. That ledger also carries platform health alerts, so they appear here too.

Loading…