Flipper
Getting started

Concepts

Six words carry most of Flipper. Learn them here and the rest of the documentation reads quickly.

Episode

A raw thing that happened: a Slack message, an email thread, a document revision, a calendar event. Episodes are stored encrypted and kept as evidence — every fact can point back at the episodes it came from.

Fact

One claim, written as subject – predicate – object: *Payments API v2 — blocked by — the ledger schema review*. Facts carry a source, a timestamp, a confidence band and a sensitivity. They are never edited in place.

Entity

The subject a fact hangs off: a person, project, customer or team. Entities carry aliases, so @sam, sam@kepler.dev and “Sam Okafor” all resolve to one node in the graph.

Confidence

Every fact sits in a band — high, medium or low — based on how it was asserted, how often it is corroborated, and whether agents that used it reported it worked. record_outcome moves a cited fact by one bounded step, so confidence tracks usefulness rather than assertion.

An entity page: current facts, confidence bands, and the fact that replaced an older one.
An entity page: current facts, confidence bands, and the fact that replaced an older one.

Supersession

When something changes, the old fact is not deleted — it is marked superseded and points at its replacement. get_fact_history walks that chain, which is how “we moved the launch to Q4” stays legible six months later.

Playbook

A repeatable process — refunds, escalations, onboarding — distilled from your own facts into steps an agent can follow. A playbook is inert until a human approves it. See Playbooks.