Animus About Us
How we listened.

Animus is new. The methods it borrows aren't.

Animus itself is only a few months old at the time of writing. The work it borrows from is older — by decades, in some cases by half a century. The reading list splits into two parts: where the questions came from, and where the conversation came from. Each is on its own page. At the bottom of this one is a third part — what we deliberately chose not to do.

The reading list, in two parts.

Two sets of traditions.

Animus is built on two distinct bodies of work. The questions came from palliative-care interviewers, gerontologists, and oral historians. The conversation came from therapists, ethnographers, and writers on plain language. Each gets a full page below.

Part one Sources 01 – 04

Where the questions came from.

Dignity Therapy, Reminiscence Therapy & Life Review, the StoryCorps sensory pivot, paired-prompt design — and how each shows up in the seventy-eight prompts you'll be asked.

Read part one →
Part two Sources 05 – 08

Where the conversation came from.

Carl Rogers on reflective listening, photo elicitation, Studs Terkel's interviewing practice, and Orwell on plain language — and how each shows up in Animus's replies.

Read part two →
Part three.

What we deliberately left out.

As much of the work was choosing not to do something as it was choosing to. These four shapes are common in the broader space of "AI for memory and legacy"; none of them are in Animus.

Anti-pattern 01

No timeline walk.

The default shape in this category — most peer products use it — is to interview you chronologically: childhood, school, marriage, career, retirement. It works only if your life happens to fit that arc. It silently penalizes anyone whose life didn't: people who never married, people who didn't have a stable career, people whose hardest year doesn't sit in the year-slot a chronology would expect.

What we did instead. Animus never walks a timeline. The bucket order is chosen by what's emptiest in your answers, not by a calendar. Two people who use Animus for the same length of time will be asked different questions in different orders.

Anti-pattern 02

No biographical assumption.

Many systems pre-assume the milestones: tell me about your wedding day, describe your first child, what was your career like. The questions sound friendly until they don't apply to you, at which point they become small papercuts of erasure.

What we did instead. The seventy-eight prompts in Animus assume nothing about whether you married, had children, had a career, or stayed in one country. "What did becoming — or deciding not to become — a parent change in you?" is the closest Animus comes to naming a milestone, and it deliberately holds the door open both ways.

Anti-pattern 03

No question every turn.

Most chat interfaces are tuned, implicitly, to keep you typing — every reply ends in another question. Useful in customer support, corrosive in conversation about a life. It teaches the speaker that their part is to keep producing material, not to settle into any one piece of it.

What we did instead. The system prompt holds an alternating rule: most replies should not end in a question. Asking on every turn is over-functioning. Sometimes the right move is a one-word reply, or a small reflection, or just stopping. A pause is allowed to be a pause.

Anti-pattern 04

No vocabulary of immortality.

The space around digital memory has a recognizable register — words like forever, live on, reunite, bring back. The register makes promises a piece of software cannot keep, and quietly trades on a grief no software is qualified to handle.

What we did instead. A short list of words is banned everywhere in Animus — in the prompts, in the AI's replies, in the marketing copy on this site. Animus doesn't bring anyone back. It holds answers you wrote, in a voice you trained, for people you chose to share them with. That's what it does. It tries not to claim more than that.

We didn't invent these ideas — we borrowed them, plainly. Animus is a few months old. The traditions it stands on are not.

If you want the engineering side — the providers, the libraries, the storage decisions — that lives on a separate page.

What's inside → ← Back to home