Skip to content

FOUNDATIONS · ARCHITECTURE

The memory bus.
A sonar view.

Every write is an event. Every event echoes through six layers — memory, automations, the AI surface, the data fabric, integrations and trust. Scroll to walk a single write through each one.

  • LAYERS6
  • P508 ms
  • P9924 ms
  • FAN-OUTevery client
  1. 01ENTRY

    The write arrives.

    A write enters on one of three surfaces — the UI, the SDK, or the open API. Aixys treats them identically: each becomes a typed event before anything else happens, so a form submit and a script call show up in the log under the same grammar.

    The event is signed with the actor, the subject, and a verb. Nothing propagates until those three fields are present.

    SURFACES
    UI · SDK · API
    SHAPE
    actor · subject · verb · payload · at
    GATE
    RBAC · schema validation
  2. 02CORE

    The event log takes it.

    The core of the platform is an append-only event log. Nothing is edited; everything is an addendum. The log is durable by design — committed before the API returns — so downstream layers can assume the event is real the moment they hear about it.

    Every subsequent view of your data, no matter how fancy, is a derivation of this log.

    WRITE P50
    8 ms
    WRITE P99
    24 ms
    DURABILITY
    3× replicated, RPO ≤ 1s
  3. 03RULE

    Automations hear it.

    The first subscriber is the automations layer. Declarative rules — when an account is created, open a project — act on the event while the user is still looking at the confirmation screen.

    Rules compose. Two automations watching the same verb both fire; ordering is tie-broken by priority, not by who got there first.

    TRIGGER
    event verb match
    DISPATCH
    parallel, ordered by priority
    RETRIES
    7, exponential, DLQ after
  4. 04READ

    The AI surface grounds on it.

    The surface is never guessing. Every answer cites the event or object it came from, and the tokens for the answer are streamed alongside the citations — you see the source before the sentence finishes.

    The same indexer that powers citations powers recall: ask about a customer and the surface reads the events, not a snapshot.

    RETRIEVAL
    vector + BM25 hybrid
    CITATIONS
    mandatory, per-clause
    TOOL CALLS
    all typed, all logged
  5. 05SYNC

    The data fabric pushes it.

    Every open client on your tenant — a second tab, a teammate's laptop, a mobile app — is a live subscriber. The fabric pushes the event down the same socket that carried the page, so the UI updates before the user has released the mouse button.

    Offline surfaces queue intents and reconcile with CRDT semantics when they reconnect.

    TRANSPORT
    WebSocket · SSE · HTTP long-poll
    FAN-OUT
    every client on the tenant
    CONFLICTS
    CRDT merge, last-writer-wins per field
  6. 06EDGE

    Integrations + trust close it.

    The outer ring is the world. Outgoing webhooks notify whatever's listening — Slack, Stripe, your own service — and incoming integrations loop back as new events. The border between Aixys and everything else is a single log.

    Trust stamps the trail: the audit record, residency tag, and compliance evidence land in the same place the event started. One write, one story, end to end.

    OUTBOUND
    webhooks · app actions
    INBOUND
    polling · push · scheduled
    AUDIT
    SOC 2 · HIPAA · ISO 27k

PLATFORM · CLOSE THE LOOP

One write. Heard everywhere.

The memory bus is the reason a change in CRM ripples into Finance, Projects and a thought you wrote three weeks ago — instantly. See it live on your own data.