How it works

A short path from context to continuity.

Banyan starts with a smaller claim than a full memory network: selected context can be saved, found and checked within one browser.

Capture
A person chooses one fact, decision or preference to preserve. The demo never ingests a whole conversation.
Organize
The record receives a type, optional tags and a simulated session label so it can be found later.
Verify
A SHA-256 fingerprint is calculated from the record. Verification recalculates it from the current fields.
Handoff
The simulated session changes while the browser workspace stays the same, making the saved memory available again.

What the demo really does

Small mechanics, stated precisely.

The prototype proves browser behavior only. It does not imply a remote memory service, encryption or cross-device account.

Storage

Memories are stored with localStorage under a versioned key. Clearing browser data removes the workspace.

Recall

Search checks memory content, type, session and tags. No embedding model or remote request is involved.

Integrity

The SHA-256 value changes when the fingerprinted fields change. It does not prove who wrote the memory or whether it is true.

Implementation stages

Phase 2

Requires a real public data source. A Route Handler would serve validated, read-only snapshot data with source and retrieval time.

Phase 3

Requires accounts, authorization, key management and an external memory API. None of these exist in the prototype.

Phase 4

The token is not part of the demo promise. No address, price, trading venue or launch date is currently available.

Want to inspect the behavior rather than the diagram?