eooo.io
Private preview
PROJECT / 06Private context vault

Tessera

How can personal context become useful without becoming somebody else's permanent asset?

A private context vault exploring local-first memory, selective disclosure, trust boundaries, and human control over retained knowledge.

Why this project exists

Personal context should behave like a user-owned capability: locally governed, selectively disclosed, revocable, inspectable, and useful across tools without silently becoming platform property.

The work, in sequence

Sample chronology from the prototype, awaiting editorial verification.

01
Data

The archive becomes queryable context

Conversation history is reframed as governed personal data rather than a pile of exported transcripts.

02
Concept

A vault for usable memory

Local storage, trust boundaries, and selective disclosure define the first architecture.

Ideas leaving the laboratory

Longer arguments and field notes produced by the work.

Context crosses by consent

Personal memory remains behind a user-controlled boundary and leaves only through explicit disclosure rules.

Mermaid diagram

Rendering diagram. The source is available below.

Diagram source
flowchart TD
  accTitle: Context crosses by consent
  accDescr: Personal memory remains behind a user-controlled boundary and leaves only through explicit disclosure rules.
  n0["Private context: Locally governed personal knowledge"]
  n1["Trust boundary: Consent, scope, and revocation"]
  n2["Selective view: The minimum useful disclosure"]
  n3["External tool: Temporary, purpose-bound use"]
  n0 --> n1
  n1 --> n2
  n2 --> n3

No project lives alone.

This dossier remains focused on Tessera. Its dependencies and effects continue through the wider Factor-E constellation.

Next question

What consent model is simple enough to use daily and precise enough to govern consequential disclosure?

Return to the constellation