Prototype in minutes, ship the same day
Five planes, each with one job and a hard boundary. One part can change and ship without touching the rest.
The design gives each customer a lasting record. A shared engine checks what has changed and calls on the relevant agents to review the context and propose an action. Ten security invariants guard every layer.
The line between a fact and a guess is what stops an agent inventing things about a real person. Every item carries its source, confidence, age, and what replaced it.
Illustrative example: one hotel family, from the architecture specification.
Six kinds of trigger. The one most systems miss is absence: the event that did not happen.
A booking, a reply, a complaint.
A birthday or the usual booking window approaching.
Usually books around the holidays.
Hasn't visited in a year. Hasn't replied. The event that did not happen.
The preferred room becomes unavailable. A complaint is resolved.
Always books for the holidays + hasn't booked + the room is filling up.
Pick a journey and watch which parts light up at each step. Click any part to see what it does. Turn on Show protections to see which security invariants guard each part.
Every shield links to the invariant it stands for on the security page.
There is no privileged caller and no side door. If anything a draft depends on changes, its pass lapses and it is checked again.
The checks grew from the six in the founder's personal prototype. The Keepara build adds a harm check and each business's own rules, and makes autonomy a state of the last check rather than a separate route.
Every security question gets one of three answers: a platform invariant, your policy, or assurance. The invariants below are true for every business, forever. Choose one to see how it is enforced and which regulations it is designed for.
People decide what is worth shipping and what good service looks like for a customer.
The same fundamentals I work by are designed into the product: evals as the spec, experiments on every decision, judgment kept with people.
Prototype in minutes, ship the same day
Five planes, each with one job and a hard boundary. One part can change and ship without touching the rest.
Wake up and review what your agents shipped
The product gives a retention team the same morning: what each customer's agent noticed, proposed and held overnight, with its reasons.
Agents interview and analyze at scale, on their own
Every customer's agent is a standing discovery instrument: it forms beliefs about one person, each with evidence. Ask your agents turns that into answers about a population.
Agents design, run and read experiments nonstop
A holdout inside every decision: agents act for a random half of the customers they flag; the rest get the usual process. The comparison is recorded before the result is known.
Evals are the spec. Agents iterate until every change passes
Seven checks every draft must pass, in order, with no bypass: evidence behind every fact, nothing leaked, nothing stale, no false familiarity, within limits, no harm, and your own rules.
Where AI becomes your moat
The intended moat is memory that compounds: each relationship's history, beliefs and outcomes grow with every decision. A copy starts from zero for every customer. Not yet shown.
Taste
Taste is written into the system: knowing when not to call. Waiting is a decision. Discounts, refunds and open complaints are never automatic.
What you've shipped
Agents earn autonomy the same way: by what they have shipped. After 20 approvals without an edit, one kind of message may go out on its own.
Status: Built exists in the prototype. Partly built some of it exists. Specified written in the architecture, not built. Plan Proposal intended, not running. Hypothesis not yet shown.
I can walk you through how the agent uses customer history, records its decisions and keeps every business walled apart.