■ PAGE 02 / 07 — HOW IT WORKS · ANIMUS PORTAL · OPERATING RECORD

The case is the product. Everything else serves it.

Chat tools end with an answer. Automation tools end with a status. Animus is built around a third object: a persistent case that carries the work from intake to an accepted, owned, explainable outcome.

■ SEC 01 / 04 — ANATOMY OF A CASEHOW IT WORKS

Anatomy of a case

Every case is a durable operating record. People and agents work from the same object — not from copies of context scattered across chats, tickets, and scripts.

CASE · CUSTOMER ISSUE #1842 — RECORD FIELDS

OWNERThe accountable person. Never optional, never an agent.

SOURCEThe originating item: backlog entry, customer issue, RFP, exception, schedule.

CONTEXTRecords, documents, policies, knowledge, and acceptance criteria attached at intake.

WORKFLOWThe versioned package of phases, roles, rules, and gates this case runs under.

STATERunning, waiting, blocked, in review, awaiting approval, accepted, rejected.

EVIDENCEArtifacts, test results, citations, diffs, and reviewer findings as they accumulate.

DECISIONSEvery verdict, override, and approval — who, what, when, on what evidence.

COSTModel and execution spend attributed to the case and its phases.

■ SEC 02 / 04 — STRUCTURED VERDICTSHOW IT WORKS

Structured verdicts, not vibes

Reviews return a typed decision the workflow can route on. A reviewer — agent, deterministic check, or person — must land on one of five verdicts, with evidence attached:

ADVANCE

The work meets the standard. Proceed to the next phase.

REWORK

Specific deficiencies, returned to the responsible phase with findings.

WAIT

Missing information or a pending dependency. Pause visibly, with an owner.

REJECT

The case should not proceed. Recorded with reasoning.

FAIL

The workflow cannot complete. Escalate with full state preserved.

■ SEC 03 / 04 — RECOVERYHOW IT WORKS

Built to be interrupted

Production work gets interrupted: providers time out, inputs stall, people go home. Animus persists workflow state, journals every step, and checkpoints artifacts — so a case resumes from where it stopped, not from scratch.

▪Durable workflow state independent of any single process

▪Step journals: what ran, with what inputs, producing what

▪Checkpointed artifacts and environments

▪Resume, re-run, or reassign without losing the record

▪Every recovery visible on the case history

■ SEC 04 / 04 — CONTROLSHOW IT WORKS

Controls that hold under pressure

BUDGETSModel and execution spend capped per phase and per case; exhaustion pauses, never silently degrades.

PERMISSIONSEach role — agent or human — sees only the context, tools, and systems its phase requires.

GATESConsequential actions (merges, sends, payments, external calls) require the configured approval.

POLICIESOrganization rules evaluated at phase boundaries; violations stop the case with an owned exception.

SEEN ENOUGH MECHANISM?

Watch a real case earn its approval.

SEE THE 90-SEC RUN →TALK TO US

founders@launchapp.dev