FlowSpace

Your stack is a dozen tools pretending to cooperate. CI/CD writes to its database. RevOps writes to theirs. Dashboards query a warehouse fed by brittle ETL. Your wiki holds Tuesday's version of the truth; a chat channel holds Wednesday's; nobody's quite sure which is current. Nothing shares an identity, a schema, or a because-line. Every new integration is a quarter's work. Every audit is a scramble.

GDPR Article 17 right to erasure is not satisfied by a policy document that says "we delete on request." It is satisfied when you can prove the data is gone -- structurally, verifiably, down to the storage address. EU AI Act right-to-explanation is not satisfied by a log file. It is satisfied when the explanation is the data structure itself.

FlowSpace is one substrate for all of it. DevOps writes signed thoughts. RevOps writes signed thoughts. Dashboards read signed thoughts. A wiki entry and a chat message land in the same graph as a build log and a sales opportunity — every item content-addressed (BLAKE3 hash — identical content always resolves to the same address, so dedup is by construction), cryptographically signed (you always know who put it there and when), and connected to its sources by because-lines (you always know why it's there and what it draws on). Build logs, product specs, chat transcripts, ledger rows, model weights, rendered PDFs — same primitive, same addressability, same audit.

We built this for ourselves first. It runs our own products. We are opening it up because the structural discipline is worth sharing -- and because your next integration should be a day's work, not a quarter's.

• Content-addressed storage. BLAKE3 hashes as primary keys. Identical content resolves to the same address, so dedup is by construction. No duplicate storage costs. Verifiable integrity on every read.
• Ed25519 signatures on everything. Identity is a public key. Signatures are first-class. Every record is authenticated. You always know who put it there and when.
• Because-lines. Every record cites its sources. Walk back from any claim to the evidence that produced it. This is what makes GDPR Article 15 (right of access) and EU AI Act Article 86 (right to explanation) answerable in seconds, not days.
• ThoughtSchemas. Define a data type once; any ingest target matching the schema becomes queryable immediately across all tooling. The next data source is a configuration task, not an engineering project.
• Stemlines. Reusable templates for common ingest patterns (RSS-to-pod, change-feed-to-graph, API-poll-to-ThoughtSchema). Named, signed, revisable.
• Observer-relative trust. Trust is materialised into a time-locked fractal index the observer slides through at query time — no global rank, no stored reputation number.
• Distributed mesh operation. Nodes peer directly. Content follows capacity. No single origin to knock over.
• Privacy-first erasure. Revocation is structural (rework with valid_until + nestled-key closure). GDPR Article 17 right to erasure is satisfied by construction — provably, down to the storage address. Not by a policy promise you hope someone follows.