The questions it exists to answer
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.
Where it stands, and what the gate is for
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.
- 01Now
Synthetic proof of concept
- Four memory layers
- MCP server
- Evaluated on a synthetic cohort
- 02Gate
Data-protection assessment Design
- Before the first real guest datum
- Not before the build
- No real guest until it clears
- 03Phase 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.
One stay, four memory layers
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.
- 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 yetBooking data only: nothing beyond the reservation, no profile.
- 02
During the stay
- Requests
- Interactions
- Operational events
Working memoryExpires at check-out
- 03
After check-out
- Episodic tail, weeks
- Semantic only if stated or repeatedly confirmed
Episodic, then semanticWeeks, then long with decay
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.
| Layer | Holds | Lifetime |
|---|---|---|
| Working | The current stay, in progress | Expires at check-out |
| Episodic | This stay and a short tail after it | Weeks |
| Semantic | Durable preferences, stated or repeatedly confirmed | Long, with decay |
| Segment | Anonymised patterns, what guests like this tend to need | Aggregate, 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.
Claims carry confidence, and confidence decays
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.
- Stated once
Prefers a high floor
- Source
- Said to a receptionist, one stay
- Age
- 14 months
Confidence 0.52 · illustrativeHeld, and it has faded since nothing renewed it.
- Confirmed ×4
Prefers a high floor
- Source
- Requested again on four stays
- Age
- Last renewed 3 weeks ago
Confidence 0.91 · illustrativeCorroboration is counted, not claimed.
- Inferred
Prefers a high floor
- Source
- Derived from booking behaviour
- Age
- 2 months
Confidence 0.34 · illustrativeMarked as inferred, and it never outvotes something said.
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.
Remembering is not neutral
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.
Scope-gated, and it never decides
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.
Orchestrator
Declares one layer, for one purpose.
Semantic layer, room assignment
Scoped, logged, answerable.
Answer
Who this guest is right now. Nothing more.
"Everything about this guest"
There is no call that returns a whole person. It is a structural choice, not a policy one.
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.
Where it sits in the architecture
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.
Rose reads this case study in full. She will not claim this node has run on a real guest.