Security

Your node decides what leaves.

Keys for who gets in. Grants for what they see. You hold the line.

Cognitive Firewall

The part of your node that decides what gets seen.

Every request — person, app, or AI — hits the gauntlet before anything leaves. The firewall runs on a minimum disclosure rule — only exactly what’s needed. Filters run on your node from the permissions you set. Never from the asker’s app.

01PERMISSIONsession · ceilingkey, or nothing02NEGOTIATIONnarrow, or denybefore any data03TIERclamped by grantdefault_disclosure04RETRIEVALdense artifactsnever selected05FILTERSmanifest · PIINSFW dropped06MINIMIZERprovable subsetbackstop last6 LANES54321 LANEA GRANTEE ASKS“how are they doing?”through their own AIWHAT LEAVES“they're fine, busy week”one sentence, one recordDENIED · only 01 or 02 can do this · p95 ≈ 0.8 ms
  1. Permission

    No key for this asker, this data, this question? Refused before retrieval.

  2. Negotiation

    Too broad? Narrow the ask — or get nothing.

  3. Disclosure

    Only the protected form, filtered — never a dump.

  4. Minimizer

    A final pass that can only remove facts.

Uncertain? Fail closed.

Who

No key, no entry.

Hand a key to a person, an agent, an app. Same rules. Same ledger. Without a key, nothing gets through.

  • People and AIs.You decide who holds a key.
  • One click to revoke.Access gone before the next read.

What

A key gets them to the door. Grants decide what walks out.

Who is not what. Given a key, your node — with the grants you set — decides what they actually see.

As data enters, a protected copy is written next to the raw record. You see raw. People you share with get the protected form — because it exists before anyone asks.

incoming recordprivacylayerYou see rawdinner w/ Maya, 7pm —call 555-0142 re: leaseOthers see protecteddinner w/ [person], 7pm —call [phone] re: lease

Records still awaiting processing can’t be shared — fails closed.

On your node

Built where your data lives.

Your database. Your machine or your infra. Access, filters, and the ledger all run there — not in someone else’s app.

Watch reads and writes per key. Nothing touches your data silently.

145 adversarial probes before every release. One leak blocks the ship.

Table of connected apps with per-key read and write counts
Per-key reads and writes — live on your node.

Get yours

Hold the keys. Run the node.

Issue, scope, watch, revoke — on infrastructure you own.

enter TOPOS