aAnamorav0.4 · embedded runtime
memory

Entities, not notes.
People, before paper.

Anamora’s memory is structured around the things your business is actually made of — people, companies, projects, commitments, decisions, risks. Not a notebook. A graph you own.

Every claim has a source. Every fact is editable. The vault lives on your machine, in plain Markdown — yours to read, version, fork, and walk away with.

Aiyana Okonkwo

person · client · acme studios
last seenMar 18 — invoicing thread, no reply
cares aboutQuarterly pacing, NET-30, Slack only
open loopSend revised invoice for Q1
last giftAsked for the Lakoff book — not sent
what it captures

The shape of
your business.

Anamora ingests transcripts, threads, files, voice memos, and the occasional hand-typed note. It turns them into entities and links — the underlying structure of how your business actually works.

  • · people · clients, partners, advisors, family
  • · companies · vendors, customers, portfolio cos
  • · projects · in-flight, on hold, archived
  • · commitments · who owes whom, by when
  • · decisions · with the evidence that supported them
  • · risks · cooling threads, stale follow-ups

Acme · Q3 review

project · in flight · 3 commitments open
decisionsPricing held. Kickoff slipped to apr.
risksMikhail intro stale · 18 days
last sourcemeeting · acme · q3 review · 47m
vault · acme studioson disk
  • vault/
  • wiki/
  • Aiyana Okonkwo.md· person · 18 facts
  • Acme · Q3 review.md· project · 22 facts
  • Pricing held at $48k.md· decision
  • raw/
  • 2026-04-16 · acme · q3 review.md· transcript · immutable
  • 2026-04-12 · gmail · re q1 pacing.md· thread
  • vault.manifest.md
how it’s structured

Markdown wikis,
plus a derived cache.

The canonical memory is a folder of Markdown pages, linked with [[wikilinks]]. Sources live separately under raw/, immutable after ingest. A SQLite cache powers the UI but is never the source of truth.

  • · wiki pages · the source of truth
  • · raw/ · immutable transcripts and threads
  • · cited · every claim links to the source
  • · editable · forget anything, retract any source
retention & control

The vault is yours.
Including the leaving.

Memory diffs are proposed before durable belief changes. A contradictions inbox flags facts that disagree across sources. A retraction flow removes a bad source while reconciling shared knowledge that still has support.

  • · memory diffs · approval before durable belief changes
  • · contradictions · surfaced, never silently overwritten
  • · source-weighted confidence · orphan facts called out
  • · export · the vault is plain Markdown, always
memory diff · pending · 2m

Update Aiyana Okonkwo: pacing concern → resolved.

Source: meeting · acme · q3 review (14:22). Previous belief held since mar 18.

approve diffdiscuss
by application · ~3 operators per month

Memory you can actually walk away with.

If your business deserves a graph you own — not another database you rent — apply to onboard.

stage oneapply · short intake · we read it
stage twofit call · 30 min · within a week
stage threescoping doc · your install, written down
stage fourinstall & pack · ~2 weeks of build
install$4,000 – $9,000 · scoped per operator
runtime$120/mo desktop · plus your model bill