Skip to content
    Case study

    Anima

    Memory that means no guest has to ask twice.

    Keeps what a guest said and what happened, so nobody asks twice, without watching.

    Synthetic proof of concept · deployment frozen until the data-protection impact assessment (DPIA) clears
    Read with AI

    Where this sits

    • Hospitality Multi-Agent Architecture: an orchestrator and domain agents, connected through MCP.

      For
      The reader who wants the whole picture.
      Status
      Design, with built nodes.
    • The F&B agent for boutique hotels: one WhatsApp message a day with tomorrow's covers and staffing, and the outcome recorded next to the manager's reply.

      For
      Other agents via MCP, or a hotel / F&B manager with WhatsApp.
      Status
      Built and tested on the Apaleo sandbox and on public restaurant data. 0 real users. Being made pilot-ready; no hotel yet.
    • The environmental node. Turns street, weather and event signals into structured risk the other nodes can act on.

      For
      Other agents, through MCP, not humans.
      Status
      Built, maintenance mode since July 2026.
    • AnimaYou are here

      The guest memory node. It keeps what a guest said and what happened, so nobody has to ask twice, without watching.

      For
      The nodes that need to know who is arriving.
      Status
      Synthetic PoC. Architecture ready, deployment frozen until the data-protection impact assessment (DPIA) clears.

    How the nodes fit together: the architecture note

    Sec. 01

    The questions it exists to answer

    Section 01

    Four questions a general manager cannot answer today, and every one of them is a memory question.

    In practiceA guest asked for a quiet room on three consecutive stays, and had to ask again on the fourth.

    • What does this property know about a guest that nobody ever wrote down?
    • What did we learn last stay that we will fail to use during this one?
    • What does a guest have to repeat every single time, and what does that cost us?
    • Which of the things we believe about them did they tell us, and which did we infer?

    The fourth one separates this from a customer database. A property that cannot tell what a guest said from what a system inferred has already lost the argument it will eventually have with the guest, or with a regulator.

    Sec. 02

    Where it stands, and what the gate is for

    Section 02

    A synthetic proof of concept today, with the data-protection assessment placed before the first real guest datum.

    In practiceIt has never run on a real guest, and it will not until that assessment is complete.

    Fig. 2.1 · The road, and the gate on itThree steps
    1. 01
      Now

      Synthetic proof of concept

      • Four memory layers
      • MCP server
      • Evaluated on a synthetic cohort
    2. 02
      Gate

      Data-protection assessment Design

      • Before the first real guest datum
      • Not before the build
      • No real guest until it clears
    3. 03
      Phase 4

      Production Design

      • Real guests, real stays
      • Only on the far side of the gate

    An employee can be told they are being modelled. A guest cannot meaningfully consent to being modelled during a two-night stay.

    The older version of this was the concierge who never had to ask twice: a guest memory running on one person's recall, with a bus factor of one. So Anima is a guest memory, not a twin.

    Sec. 03

    One stay, four memory layers

    Section 03

    Four layers with different lifetimes, because permanence is the default failure.

    In practiceA guest orders a decaf at 11pm before an early flight. Tonight, that matters. Forever, it is a false belief.

    Fig. 3.1 · One stay, and what is held at each pointThree phases · four layers
    1. 01

      Before arrival Design

      • Booking data
      • Situational context: a delayed train, a local event, the weather
      • Tacet gives disruption by line and place; Anima links it to the booking. Tacet holds no personal data.
      • No external data about the person, no profiling
      No memory yet

      Booking data only: nothing beyond the reservation, no profile.

    2. 02

      During the stay

      • Requests
      • Interactions
      • Operational events
      Working memory

      Expires at check-out

    3. 03

      After check-out

      • Episodic tail, weeks
      • Semantic only if stated or repeatedly confirmed
      Episodic, then semantic

      Weeks, then long with decay

    Marker on the stay Design

    Health data stays in the stay. An allergy is GDPR art. 9 data, used on explicit consent for a concrete service, never inferred. Keeping it for a future stay needs its own, separate consent.

    Segment layerAnonymised patterns across the whole house, never an individual.
    A first-time guest is not recognised, but can still be anticipated.
    The four memory layers of Anima, what each holds and how long it lives
    LayerHoldsLifetime
    WorkingThe current stay, in progressExpires at check-out
    EpisodicThis stay and a short tail after itWeeks
    SemanticDurable preferences, stated or repeatedly confirmedLong, with decay
    SegmentAnonymised patterns, what guests like this tend to needAggregate, never individual

    Working memory should use the decaf tonight, so the bar does not ask twice. Semantic memory should never conclude the guest drinks decaf.

    Sec. 04

    Claims carry confidence, and confidence decays

    Section 04

    Nothing is stored as a fact. Everything is a claim with a source, a weight and an age.

    In practiceA preference from 2019 that nobody confirmed since does not outvote something said last week.

    Fig. 4.1 · One preference, three claimsClaim: "prefers a high floor" · Illustrative values
    1. Stated once

      Prefers a high floor

      Source
      Said to a receptionist, one stay
      Age
      14 months
      Confidence 0.52 · illustrative

      Held, and it has faded since nothing renewed it.

    2. Confirmed ×4

      Prefers a high floor

      Source
      Requested again on four stays
      Age
      Last renewed 3 weeks ago
      Confidence 0.91 · illustrative

      Corroboration is counted, not claimed.

    3. Inferred

      Prefers a high floor

      Source
      Derived from booking behaviour
      Age
      2 months
      Confidence 0.34 · illustrative

      Marked as inferred, and it never outvotes something said.

    Illustrative values, nothing here is measured. The same sentence, held three different ways. Nothing is stored as a fact.

    Weights fall over time unless something renews them. A system that reports a confidence it did not measure is worse than one that reports none.

    Sec. 05

    Remembering is not neutral

    Section 05

    The stay no longer ends at check-out. Whether to remember is an act of care or an exercise of power.

    In practiceThe guest leaves the building and their record stays, in infrastructure that never forgets and never forgives.

    Whether to remember is an act of care or an exercise of power.

    Edmondo Grassi, The Remains of the Stay: Memory, Identity, and the Afterlife of the Guest, Hotel Yearbook 2026 Technology Edition.

    Sec. 06

    Scope-gated, and it never decides

    Section 06

    Every consumer declares which layer it is querying, and no call returns a whole person.

    In practiceThe orchestrator asks for semantic-layer preferences relevant to a room assignment, and nothing else.

    Fig. 6.1 · The scope gateOne layer per call
    Caller

    Orchestrator

    Declares one layer, for one purpose.

    Request that passes

    Semantic layer, room assignment

    Scoped, logged, answerable.

    Anima

    Answer

    Who this guest is right now. Nothing more.

    Request that does not passBlocked by protocol

    "Everything about this guest"

    There is no call that returns a whole person. It is a structural choice, not a policy one.

    After the answerA human validates what the orchestrator proposes. Anima never decides.
    A boundary that depends on people asking politely is not a boundary.

    Anima answers one question, which is who this guest is right now. What to do about it belongs to the orchestrator, with a human validating, the same separation between perception and decision the F&B node enforces.

    Sec. 07

    Where it sits in the architecture

    Section 07

    One of four domain nodes, five agents with the orchestrator.

    In practiceGuest experience is not a node: guest.* lives in the shared contract, not behind this one service.

    What Anima knows reaches other nodes only through the orchestrator, one layer at a time. Guest experience itself is not a node, which is why guest.* lives in the shared contract rather than behind this one service.

    The architecture note has the whole picture, including what the other nodes own and what they refuse.

    Ask Rose about this page

    Rose reads this case study in full. She will not claim this node has run on a real guest.

    Share and reuse
    EmailMarkdown

    © Ivan de Murard. All rights reserved.

    Contact

    Designing guest memory that respects privacy

    Hotels forget too much, or remember too much. Let's discuss memory with confidence decay, consent and bounded contexts.

    Questions are stored for 90 days · Privacy

    · Ivan writes the notes on the pages in Rose's voice. Her answers here are live.