The memories
keep themselves.

Amesemi is a stewardship system for long questions: living memory, visible reasoning, governed action, and evidence that stays attached as work compounds.

memories held
events recorded
verified completions
7kinds of memory
Memory persists Receipts travel Authority is visible Evidence compounds Work compounds

What does it do? In plain words:

You bring a question that matters — one that would normally die in a chat window. Amesemi turns it into a run: it recalls what it already knows, researches what it doesn't, argues with itself on the record, and hands back a document in which every figure carries its quote and its source.

Then it keeps that document true. When the facts move, the record is corrected on the page — the old answer preserved, never painted over. That is the whole product: answers that stay alive, with receipts.

Don't take the words for it — watch the mind display, read the standing records, or follow the living programme.

Why this exists

Most AI tools are designed to forget. Amesemi is designed to accumulate.

Amesemi is built on the opposite premise: long-term memory, source discipline, visible reasoning, and preserved uncertainty are prerequisites for trustworthy autonomy. It is not another chatbot with better prompts — it is a research organism whose outputs carry their own evidence.

How Amesemi is different, in full — the field guide →

Atelier console

Choose the shape of the work before the work begins.

Amesemi should feel capable because it is bounded clearly. Pick a run shape and the console names the likely cost, authority, memory surface, deliverables, and the first thing the operator would ask or do. Short questions stay short; consequential action waits for approval.

quick question

A short answer that still remembers.

estimate3 cycles · low cost

operator voiceI can answer this without turning it into a cathedral. I will recall first, check the live source if it matters, name uncertainty, and stop when the answer is useful.

memorypublic + project
sourcesweb allowed
authoritylocal only
closureanswer packet

Deliverables

    First questions

      This public console is a preview of the operating model, not a fake hosted agent. Subscriber runs add private memory, deeper tools, and real completion packets.

      Memory, up close

      See one recall, end to end.

      Before the constellation, here is one recall at working resolution: what was already known, what was still missing, and the receipt that lets the answer close. Nothing here is generated for show — it is the shape every serious answer should leave behind.

      live recall standing by
      ask

      What did we decide about completion proof?

      Recalled

      provenance

      Completion counts only when the artifact on disk hashes to what the completion packet claims. Generated text never counts.

      Missing

      clear

      No blocker — the packet is signed and verifiable from bytes on disk.

      1. provenance

        Artifact checksum matched the completion packet.

      2. governance

        External action held for a signed human approval.

      3. non-erasure

        A superseded decision was kept, not deleted.

      This is one recall — operate the full memory workbench →

      The run, live

      The work shows its proof.

      This is not a simulation — it is the public trace of one working session, event for event, with sensitive content withheld. Intentions, evidence, completions, approvals, and visible reasoning each keep their own colour. Pause the run, change its pace, scrub dot by dot — the small seal in the corner names the constitutional law each event answers to.

      the run is thinking
      replaying a real session

      Research superorganism

      Work with receipts, memory with lineage.

      Ask a question and Amesemi recalls what is already known, searches where memory is not enough, challenges its own answer, then works — visibly — until the result exists as an artifact whose evidence closes the packet. Nothing learned is deleted; corrections stack on top of what they correct.

      The field guide — every capability in full →

      The operations room

      Runs continue after you close the lid.

      Scheduled runs wake on their own heartbeat — inside guards. A budget cap no run can exceed, an overlap lock prevents races, and a signature gate holds anything reaching outward for approval. A missing input becomes a typed blocker — an interrupt, not a failure. The queue below is refreshed at deploy.

      budget cap · model runs/day overlap guard signature gate

      The constitution

      Six laws the code actually enforces.

      Not aspirations — enforced stops in the execution path, checked at every memory write, every completion packet, every approval gate. The replay above traces these same laws as the run proceeds.

      The full constitution — how each law is enforced →

      Stewardship access

      Stewarded, not sold.

      Access follows the same laws as memory — additive, auditable, reversible. Two doors are open while Amesemi is in research preview.

      Research preview

      Join the waitlist

      Leave an address and you'll be invited as subscriber previews open — your own Amesemi, working on your problems. Reply to the welcome email with one fact you wish stayed true, and it enters the backlog.

      Your address is used once, to invite you. No cookies, no tracking — only anonymous page-speed telemetry.
      Founding supporter

      Fund the development

      A small circle of founding supporters resources the research preview — and the first ten may commission a standing brief: a public-information question of yours that Amesemi runs keep true, receipts attached, for as long as you subscribe. Plus first access when subscriber previews open, priority on the waitlist, and the full Amesemi Starter Kit as a thank-you. 10 of 10 seats remain.

      Become a founding supporter
      Secure checkout by Stripe · $9/month · cancel anytime. Prefer a single gesture? Founding support · $49 once — obligation-free, no subscription, and the Founding Pack is yours as a thank-you. Plain-English terms and the refund promise live in the FAQ. And free for anyone, no address asked: the Amesemi method as a starter vault — the capture → note → card discipline the memory system runs on.

      Completion packet

      Artifact
      /work/amesemi-answer.md
      Checksum
      sha256 · 42f7…9ac1
      Authority
      local write only
      Status
      verified from bytes on disk

      Every completed task carries one of these. The checksum is computed from the file itself — if the bytes do not match, the task is not done, whatever the text says.

      stewardship system · living memory · the memories keep themselves