We will break something. Here's what happens then.
Cendriix is software. Cendriix uses AI models. Both fail sometimes. We're pre-launch, so rather than recount incidents we haven't had, this page sets out the commitments we're binding ourselves to from day one. Incident reporting, postmortems, and vulnerability disclosure will happen inside Cendriix. You should never have to hunt for what went wrong.
Our incident commitments
These are binding. Not aspirational. If we miss one, that is itself a P1.
When something does go wrong
We have no incident history to publish yet, Cendriix is pre-launch. When that changes, this page will not. Every P1 and P2 incident will get a blameless postmortem published on our public status page, with the same detail visible to customers and non-customers alike. No paywalls, no NDAs.
Each postmortem will state the impact, the root cause, and the fix, written for an engineer, not a press release. We would rather you judge us on how we handle failure than on a claim that we never fail.
What Cendriix tells you when an AI agent gets it wrong
Every model decision is logged: prompt hash, completion hash, model version, confidence score, and the Cendriix agent that invoked it. Nothing is inferred, it is all recorded at call time.
For any AI decision above a confidence threshold, founders see: “This was an AI choice, was it right?” with a one-sentence explanation of what the agent decided and why. A yes/no confirms or corrects the record.
The /time-travel view replays every agent step, prompt, completion, tool calls, intermediate decisions, in order. Inside Cendriix. No log aggregator required.
A one-click rollback reverts the agent's output. Cendriix automatically files an internal training-data ticket so the model that made the wrong call is corrected, not silently ignored.
Open commitment ledger
Public promises. Public statuses.
Something to report?
Security disclosures, incident feedback, and transparency concerns all go to the same team, and all get a human response, not an autoresponder.