A personal project, built in four milestones

A little memory.
A longer journey.

New chat. Different computer. Same project.
Memvek gives a fresh AI assistant a place to find the notes you chose to keep.

See how we built it

Private, self-hosted memory. Not a recording of every conversation.

A miniature memory workshop with a computer, a card cabinet and a recovery safe. — One place to keep the thread.MEMVEK

THE STARTING POINT

“I explained this yesterday.
Why do I need to start again?”

We built Memvek around that small frustration. First, prove the idea. Then make it useful across sessions and devices. Finally, make it recoverable.

THE BUILD LOG, IN PLAIN WORDS

Four steps forward.

A timeline of what changed.
Each step made the next one possible.

Meet the example: a fictional community garden called Maple Garden. These short stories explain the features. They are not transcripts of our tests.

01THE EXPERIMENTCompleted

First, prove that
memory can work.

Before we built Memvek, we tried its memory engine, Hindsight, with an actual AI client.

We checked whether saved information could come back with its source. We also explored what happens after a correction or deletion.

WHAT THIS ADDEDA tested starting point, not yet a finished app.

A small memory engine on a test bench, with a source card and inspection tools. — A test bench before a toolbox.

EXAMPLE / THE FIRST NOTE

Can the assistant find the reason?

1. Save a fact
“Maple Garden uses rainwater for the seedlings.”
2. Ask later
“How do we water the seedlings?”
3. Inspect the source
The returned memory points to the note that supports it.

What we learned: a useful result needs a source. A search result alone does not prove relevance or safe deletion.

02THE WORKING NOTEBOOKCompleted

Give the memory
some ground rules.

We built Memvek around the engine. It keeps the exact notes, their current versions, and the work you want to hand over.

You choose what to save. You can correct it, export it, or ask Memvek to forget it. Work in progress stays “pending” until completion is known.

WHAT THIS ADDEDUseful memory with an original you can read.

An indexed memory notebook and a card cabinet, with a new card replacing an older one. — The note stays exact. The current version stays clear.

EXAMPLE / A PLAN CHANGES

Keep the new plan, not the old advice.

1. Remember
“The garden workday is Saturday.” Save this note explicitly.
2. Correct
Rain changes the plan. Replace Saturday with Sunday.
3. Resume
A fresh assistant sees Sunday as the current plan. The exact note is available.

What we learned: being saved and being ready for search are different states. Memvek must say which one it knows.

03THE SHARED DESKCompleted

Change the computer.
Keep the thread.

We connected a Mac and a Linux computer to one private Memvek service.

A fresh assistant could read a saved handoff on the other device. We also tried handoffs in both English and Traditional Chinese.

WHAT THIS ADDEDA shared memory, instead of two isolated chats.

Two computers at a shared desk with one central memory cabinet. — Two devices. One set of chosen notes.

EXAMPLE / PICK IT UP AT HOME

Hand over the next step.

1. End a session
On the laptop: “The seed list is ready. Next, check the tool list.”
2. Open a fresh session
On the other computer: “Resume the Maple Garden plan.”
3. Continue
The assistant reads the handoff. If a file is missing, it asks for the file.

Memory carries the handoff, not your files. This was verified on a private home network, not from outside the home.

04THE RECOVERY KITCompleted

Make room for
things to go wrong.

We exercised restarts, service outages, competing edits, and deletion while work was still in progress.

We added encrypted backups and tried recovery in a separate copy. We also checked a model change without processing the old notes again.

WHAT THIS ADDEDA checked recovery path, not just a happy path.

A recovery safe with two backup cartridges and a separate restored memory cabinet. — Keep a backup. Check the copy before use.

EXAMPLE / AFTER AN INTERRUPTION

Recover without reviving old advice.

1. Keep a recovery copy
An encrypted backup stores the original notes and the memory engine together.
2. Recover separately
After a failure, restore into an isolated copy, not over the working service.
3. Respect later changes
Apply known deletion records before use. A missing newer note stays unavailable.

Not yet scheduled: unattended daily production backups. More live testing of memories built from several sources is also a future follow-up.

PUT THE PIECES TOGETHER

One project.
A fresh assistant.

Follow a note through Memvek today.
This is an illustrated demo, not a live service.

01 / YOU CHOOSE WHAT TO KEEP

“Remember this
for Maple Garden.”

Save the workday plan on your laptop. Memvek keeps the exact original and queues it for the memory engine.

YOU → ASSISTANT

“Remember: our garden workday is Sunday. Bring gloves.”

The note can be pending while the engine works. Memvek does not claim it is ready early.

MAPLE GARDEN / MEMORY CARDSaved → pending → ready

EXACT ORIGINAL

Sunday.
Bring gloves.

Your chosen note stays readable. The memory engine helps find it later.

Source: your saved garden note

The original is the reference. Search is an aid.

No sign-in, saved data, or model calls. Buttons only change this example.

WHAT MEMVEK IS — AND IS NOT

A notebook for your assistant.
Not a source of permission.

You choose the notes.

No automatic recording of every chat. Keep only content you approve.

Sources still matter.

Read the original. A ranked result can miss the point. Your current instructions and project files remain authoritative.

Private is not all-local.

You host the service. The configured AI provider can receive saved content for processing.

A little memory.A longer journey.

Four steps forward.

First, prove thatmemory can work.

Can the assistant find the reason?

Give the memorysome ground rules.