Architecture

Persistent memory.
Attention where it counts.

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.

Persistent stateEphemeral computeIntelligent attentionContinuous learningGuarded by ten invariants
Five planes stacked: experience, intelligence, agent, data and infrastructure. In the agent plane most agents sleep while a few wake. A shield along the side shows ten invariants guarding every layer.ExperienceIntelligenceAgentDataInfrastructure10GUARDED BY TEN INVARIANTS
What an agent knows

Nine kinds of knowledge, each honest about how sure it is.

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.

  1. Source factStayed in room 312 last December.Straight from a record
  2. Derived factFour December stays in a row.Computed from facts
  3. BeliefThey prefer a lake-facing room.Held with a confidence
  4. PatternBooks 50 to 55 days before arrival.Repeats across time
  5. HypothesisThey may have booked elsewhere this year.Open, to be tested
  6. GoalKeep the annual holiday stay.What the agent works toward
  7. DecisionWait. Apology first.With its reason
  8. OutcomeDid they rebook after the manager called?What happened next
  9. LearningWhether repair before offer works for this family.Carried into the next decision

Illustrative example: one hotel family, from the architecture specification.

Why an agent wakes

A scheduler asks when. A trigger asks why should I care.

Six kinds of trigger. The one most systems miss is absence: the event that did not happen.

Event

A booking, a reply, a complaint.

Time

A birthday or the usual booking window approaching.

Pattern

Usually books around the holidays.

Absence

Hasn't visited in a year. Hasn't replied. The event that did not happen.

State change

The preferred room becomes unavailable. A complaint is resolved.

Compound

Always books for the holidays + hasn't booked + the room is filling up.

Context, in layers

The agent never works from one giant blob.

GlobalPlatform rules that apply to every company.
BusinessThis company's identity, offers, policies and strategy.
RelationshipThis customer's identity, history, beliefs, goals and outcomes.
ExecutionOnly what this one wake-up needs.
The whole system

Five planes, 36 parts, four journeys through them.

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.

ExperienceWhat people touch
IntelligenceShared brain, used by every agent
AgentOne per customer, asleep by default
DataSources of truth, kept apart
InfrastructurePlumbing every plane relies on

    Every shield links to the invariant it stands for on the security page.

    The seven checks

    Every draft passes seven checks, in order, with no shortcut.

    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.

    See the seven checks in the control map

    1. Nothing invented.Every sentence about a customer must cite a current, sourced fact. If it cannot, the draft is blocked and logged.
    2. Nothing from another customer.Anything from another person's record is a hard block that no one can override.
    3. Nothing stale.A fact too old to be current cannot be presented as current.
    4. No false familiarity.Drafts that claim a closeness, a feeling or a context the sources do not show are blocked.
    5. Within contact limits.Caps and spacing per customer are respected, or the draft waits.
    6. No harm.Sensitive matters and private customers are protected by rule. Sensitive matters reach a customer only in that customer's own words.
    7. Your own rules.Plain-language rules your business adds, enforced on every draft. Without permission for this type of action, the draft goes to a person.
    Security is part of the structure

    Ten invariants guard every plane.

    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.

    1. 1Tenant wallA customer exists inside one business only. Businesses are walled apart by the database, not only by the code.
    2. 2Tenant-local learningNothing learned from one business's data ever helps another business or any shared model.
    3. 3Untrusted content boundaryText from any source is data, never orders. It enters a model only inside a labelled untrusted region, and only schema-valid, sourced facts come out.
    4. 4One checkpointEvery outward action passes the seven checks, in order, with no shortcut and no privileged caller.
    5. 5A person sends by defaultEvery action type starts at Propose. Autonomy comes one action type at a time, after a track record, with a recall window. Nothing widens its own permissions.
    6. 6Total visibilityEvery content read is logged. Every wake, draft and check has a decision trail. The logs cannot be edited.
    7. 7No content outside the wallSystem logs, alerts and monitoring carry IDs and counts only. People in the operator role see IDs only.
    8. 8Exit means goneAt exit all data is returned or deleted, including every backup copy, with written confirmation.
    9. 9Least data inOnly data about customers the business keeps is stored. Everything else is dropped unread, and the drop is counted.
    10. 10One-step haltAny user in a business stops waking, drafting and model calls in one action, within 10 seconds. It survives a restart. Held drafts are checked again afterwards.
    Who does what

    Taste is the scarce skill.

    People decide what is worth shipping and what good service looks like for a customer.

    People keep

    • What is worth shipping
    • Price, credit and complaints
    • Widening any agent's authority
    • A company's voice
    • The kill switch

    Agents do

    • Build against evals
    • Run and read experiments
    • Interview and synthesize
    • Prepare the morning review
    • Meter every call's cost
    Fifteen principles

    Rules the design does not break casually.

    1. Persistent agent, ephemeral computeEach customer's agent lasts; it uses compute only while awake.
    2. Business-scoped identityA person's agent exists inside one company only.
    3. Business data is not agent memoryRecords stay the company's; understanding is the agent's.
    4. Relevance before reasoningCheap screening decides who wakes before anything expensive runs.
    5. Context before inferenceBuild the right small package, then think.
    6. Evidence before beliefEvery belief points to what it rests on.
    7. Learning must include failureWhat didn't work is kept, not just what did.
    8. Human feedback is intelligenceEdits and rejections teach; they don't only block.
    9. Agent autonomy is boundedThe agent asks should I; policy decides may I.
    10. Context, not workflowsOwners describe the business; they don't draw flowcharts.
    11. Time to value beats perfect onboardingUseful agents first, enrichment after.
    12. Modular intelligenceEach engine can be replaced without rebuilding the rest.
    13. No premature infrastructureOptimise storage when real data says so.
    14. Every consequential decision is explainableA short synopsis, not a transcript.
    15. Memory never becomes noiseWhat isn't useful isn't kept.
    Built the AI Builder way

    Where the new way of building product lives in the architecture.

    The same fundamentals I work by are designed into the product: evals as the spec, experiments on every decision, judgment kept with people.

    BuildingSpecified

    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.

    Your daySpecified

    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.

    DiscoverySpecified

    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.

    ExperimentationSpecified

    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.

    QualityBuilt

    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.

    StrategyHypothesis

    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.

    Scarce skillSpecified

    Taste

    Taste is written into the system: knowing when not to call. Waiting is a decision. Discounts, refunds and open complaints are never automatic.

    Hiring signalSpecified

    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.

    Designed for scale and safety. Every part on this page is specified against the ten platform invariants, and every security control names the regulation and standard it is designed for. How each claim is proven, and in what order outside assurance follows, is set out on the security page.
    Get in touch

    Want to see how it fits together?

    I can walk you through how the agent uses customer history, records its decisions and keeps every business walled apart.