overview

One memory. Many doors. None of them owns it.

Your notes, ideas, and conversations are scattered across a dozen apps that don't talk to each other. The Construct is a portable memory system for you, your apps, and your agents: it takes in what you capture, distills it, catalogues it, and answers with receipts, from any tool you use.

Hark captures. The gateway enforces who may see what. Git holds your words, in files you own. The index is a map of the memory: disposable, rebuildable anywhere. Every answer cites the exact note it came from, or says it can't.

git: canonical
r2: raw evidence
postgres: live state
index: disposable
answers: cited
features

What it does.

Speak it, type it, snap it.

Hark, the companion capture app, cleans your stream of consciousness into readable notes and files them into the Construct. Capture never waits for enrichment.

hark → inbox → organize

Walls in the database, not in a prompt.

Every request passes five checkpoints: who is asking, what the key may do, which space it may touch, where it may write. Even the owner's key is blocked where it shouldn't write.

auth · capability · space · write · wiki

One writer. Nothing writes around it.

Every change waits in a durable queue; a single writer commits it to the vault in order, with a receipt. Your words live in Git, in files you own.

queue → writer → commit

Indexed by words and by meaning.

Keyword and semantic search fuse, nearby context is gathered, and the answer is composed only from evidence it can cite. When it can't, it says so.

fts + pgvector · rrf

Your AI life, findable.

Import your ChatGPT history with one command. Originals are preserved untouched; every message becomes searchable. Re-import creates zero duplicates.

318 conversations · 0 dupes

Yours to erase, too.

Say forget this and a cascade purges it from the vault, the index, and storage, verifies it's gone, and leaves a marker holding no content at all.

vault · index · r2 · verified
docs · architecture

All of it is written down.

Twenty-six numbered decisions govern how the system behaves. Every write is logged with who, what, and the exact change. A regression suite holds the line: if recall quality drops, or a single citation can't be proven, the build fails.

The architecture guide walks the whole system in plain English first: capture, the four kinds of memory, the gateway, recall with citations, private and shared spaces, real deletion. Technical detail appears only where it helps.

decisions: 26
canonical stores: 4
writers: 1
uncited answers: 0
Read the architecture guide
explainer · 5:52
how every memory flows through one governed pathcaptured · gated · written with provenance · indexed · retrieved with receipts
contact

Built by MartinTech.

The Construct is a MartinTech project. Self-serve onboarding opens with launch: no setup, your own vault, leave anytime.

MartinTech