memcell

Security

effective 2026-08-16

The warm line under each heading says the section in plain words. The summary is not the contract — the section is.

§1

isolation

tenants can't reach each other, and a test proves it every build

Every tenant's rows are isolated at the database layer, enforced by policy rather than by application code remembering to filter — and the isolation is tested in CI against a live database on every change.

§2

credentials

your tokens are sealed, and never echoed back

Source credentials are sealed before they are stored, under a key that rotates without downtime. Failure messages are redacted before they reach any record a person reads.

§3

keys and reach

least reach, revocable, on the record

An agent key reaches one space, as the person who granted it, and can be revoked at any moment. Operator standing is a role on the record — granted by an operator, audited like everything else — never a shared password.

§4

the record

the record is not rewritable — and you can check

History is append-only: wording changes keep the old text, confidence moves are events on a chain, and public statements are hash-chained so any reader can verify nothing was rewritten.

§5

disclosure

tell us first; test only against what is yours

Found something? Report it through the repository's security policy. Good-faith research against your own tenant is welcome; other tenants and their data are out of bounds.

© 2026 memcell · OpenOrithe status page ›