Ownership

Every context graph in your lake is plain markdown pages plus a fact ledger, kept in a vault owned by one user or team. Context this valuable shouldn’t live in a proprietary blob, so it doesn’t.

​

Isolation per vault

Each graph lives in its own version-controlled vault. Storage, history, and the retrieval index are isolated per vault; there is no pooled store your data mingles in. Every change the xysq Memory Engine makes is a commit you can diff, with a code-owned changelog and a ledger entry behind it. Nothing changes silently. That isolation isn’t a compliance feature bolted on later. It’s how the engine works, and it’s what makes deletion clean.

​

Nothing is a proprietary blob

Pages are standard markdown, stored as files in your graph’s own git repository, and every change to them is a commit. Sources are kept as you sent them: you can read any one back byte for byte in the app, along with its earlier versions if you have edited it. What you can read is what the engine serves, not a degraded copy. A one-click bulk export is not shipped yet. Today you read your data through the app and the API, source by source and page by page.

​

Deletion is real

Four things, and we mean all four:

• In normal operation, the engine invalidates rather than deletes. A superseded fact is closed, not erased, so lineage holds: you can always see what changed, when, and on what evidence. That’s versioning.
• When you delete a source, everything it was holding up stops being served. The source and its text go. The retrieval index entries go. Every fact it grounded is closed and its quoted evidence is scrubbed from the ledger. And the lines those facts put on your pages are removed from the pages themselves, with the surrounding prose rewritten so nothing is left leaning on a claim that no longer has a source. Not a soft hide, not a tombstone that keeps answering queries.
• What a delete does not reach, said plainly. Your vault is version-controlled, so its earlier commits still hold a page as it read before the deletion, and the audit trail still records that the deletion happened. Neither is served to you or to any agent, and neither is searchable. But version history is not the same as gone, and rewriting it is a separate capability we have designed and not yet shipped.
• Deleting a whole graph is the deeper sweep. It removes every source, page, fact, and search entry in it, along with the git repository itself, history included. It is irreversible, and it is the one delete that reaches what a source delete cannot. Your personal graph is the exception: it is your knowledge graph, and neither the app nor the SDK will delete it. Deleting your whole account is not self-service yet.

We would rather tell you where the line is than let you assume it is somewhere it isn’t.

​

Consent-gated, never trained on

Your context is never used to train models. Nothing crosses a graph boundary without a share you make or approve in the app, and every share is view-only and revocable.

​

BYO drive and private deployment (not shipped)

The direction we’re building next:

• Bring your own storage. Your graph mirrored to a drive you control, readable in standard markdown tools (open it in Obsidian and you get a graph view for free).
• Private deployment. The engine running inside your own boundary.

This is stated direction, not shipped. Today your vault lives in xysq’s infrastructure, isolated and readable as described above.

​

Next