What we hold ourselves to, and what holds us to it.
A value with no mechanism is a poster. Each one below names the thing that holds it in place — a test, a lint rule, a published stage — because we ask customers to trust a record we keep, and a request like that asks something of our own first.
Values
01
The truth has a date on it
A claim about where we stand means something only with the day attached. So we publish the stage each piece of work has reached, and the date it reached it. When the stage moves, the date moves with it.
What holds it
Our certification strip carries a stage label per framework, and a test fails the build if a badge ever claims bare compliance.02
The record is the product
Customers hand us the account of what their systems did, and one day someone will read that account back to them under pressure. It has to hold. We keep our own by the standard we ask them to trust.
What holds it
Every decision the platform makes is written down before it is acted on, including the decisions it makes about itself.03
Clarity is owed
Someone reading their own record is usually reading it on a difficult day. The words should carry them through it, with no glossary and no translator in the room.
What holds it
One file maps every internal term to its plain word, a lint rule fails the build when jargon reaches a customer-facing screen, and a second test holds the sentence patterns.04
Composure is part of the evidence
Our surfaces borrow the grammar of public accountability: flat, plain, unhurried. Work that will be read under scrutiny should look like it expects to be.
What holds it
The public site is held to WCAG 2.1 AA, and every route is checked for contrast and structure on every change.05
The discipline is the credential
We go looking for our own defects on a schedule, before anyone thinks to ask. What that search turns up is what makes the record worth keeping.
What holds it
Dependencies and secrets are scanned on every change, every build ships a signed bill of materials and signed provenance, and infrastructure changes pass a policy gate before merge.
How we say things
Our writing follows federal plain-language practice: short common words, active voice, one idea to a sentence, and the mechanism named. These are the working rules, each with the phrasing we use and the phrasing it replaces.
| Rule | We write | Not |
|---|---|---|
| Name the mechanism | Checks each event against rules you write in plain words. | Powerful, intelligent oversight for the modern enterprise. |
| Use the plain word | logbook · rule pack · steadiness grade · held for a person | ledger · canon · determinism grade · HITL |
| State the stage | SOC 2 Type I — readiness complete, no report issued. | Enterprise-grade, fully compliant and secure. |
| Let the claim stand alone | The platform gates the action while it is still in flight. | This is not just observability — it is real governance. |
| One idea to a sentence | An event arrives, the rules weigh it, the response fires, and the logbook records it. | Our end-to-end platform orchestrates comprehensive event governance at enterprise scale. |
| Never name the vendor behind a function | Payment processing is temporarily unavailable. | Our Stripe integration is down. |
These rules run in the build. One file maps every internal term to the word a customer should see, and a lint rule fails the build when jargon reaches a customer-facing screen. A second test holds the sentence patterns above. If you find jargon on this site, or a sentence that made you work for the point, it is a defect and we would like to know.