mortalsystemsdownload
GUARANTEES

the guarantees, labeled honestly.

every control carries exactly one label. enforced means a passing automated test backs it, and the build fails if that mapping breaks. advisory means a declaration shown in the ui, not a technical control. roadmap means not built, and the product says so. a control marked conditional is enforced only for identities configured for it: a network route attached, a tool scope declared. the identity's own manifest is what tells you whether it applies.

CONTROLVALUELABELTESTS
browser state isolation
cookies, localstorage, indexeddb, service workers, http cache, extension state and logged-in sessions live inside the identity's own chromium profile and are absent from every other identity.
separate chromium user-data-dir per identityENFORCEDG1 G2 G3 G4 G5 G6 G7 G16
filesystem partition
files and downloads land under the identity's own files root. destroying one identity never touches another identity's partition.
identity-partition-onlyENFORCEDG8
memory scope
notes and ai context are readable and writable only with the identity's own token. cross-identity access is refused by the runtime, not hidden by the ui.
identity-onlyENFORCEDG9 G18
history retention
when false, browsing-history artifacts are removed from the identity's profile when its browser session ends.
true | falseENFORCEDG15
lifecycle expiry
a non-persistent identity expires on schedule and runs its onExpiry action. expirations missed while the runtime was stopped are honored late on the next start, never skipped.
finite lifetimes fire on scheduleENFORCEDG10 G11
destruction
destruction removes the identity's browser profile, files, downloads, notes, ai history and database rows, records a tombstone and a destruction report, and resumes from its journal if interrupted.
journaled deletion contract D0-D7ENFORCEDG12 G13 G14
wallet
a declaration shown in the ui, not a technical control. mortal does not restrict which wallet extensions run inside an identity in v1.
none | read-intent | declaredADVISORYBADGE-1
network route
an identity with a network route attached is bound to it: chromium is launched on that route, every non-local request goes through it, and there is no direct fallback if the route is down. an identity with no route stays 'standard' and shares your ip address and network path. the schema cannot express enforcement without an attached route, so the badge only reads enforced when the control is real. mortal enforces the route you attach; it does not provide routing. bring your own proxy.
standard | routedENFORCED
conditional · enforced only for identities with a network route attached; routeless identities remain advisory
G19
tool scope
an identity that declares a tool scope is held to it: the runtime checks that scope before it touches any upstream server, so a call to a server or tool outside the scope is refused even when that tool is live and working, and the refusal is journaled on the identity. an identity that declares no scope stays 'open' and may reach whatever the operator registered. the schema cannot express enforcement without a declared scope, so the badge only reads enforced when the control is real. mortal scopes the calls it brokers; a connection an agent opens on its own is outside this boundary.
open | scopedENFORCED
conditional · enforced only for identities that declare a tool scope; identities with no declared scope are open and remain advisory
G20
email
email aliasing is not built. the field exists so blueprints can declare intent; it enforces nothing today.
none | temporary | dedicatedROADMAPBADGE-1
redaction
content redaction is not built. the schema pins this value to false.
falseROADMAPBADGE-1

what mortal systems does not guarantee

  • · identities without a network route attached share your ip address
  • · mortal does not provide routing or egress: it enforces the route you attach; bring your own proxy
  • · mortal scopes the tool calls it brokers: an agent holding its own connection to a server is outside that boundary
  • · identities on the same machine share your device fingerprint
  • · websites can correlate identities via behavior, reused accounts, or reused wallets
  • · clipboard contents you carry between identities are not separated
  • · data a website already holds server-side is outside mortal's reach

what destroyed means

mortal systems removed the identity's browser profile, files, downloads, notes, memory, and ai history from this machine, and recorded the destruction. mortal cannot remove: data websites stored server-side while you were logged in, anything you exported or moved outside the identity's folders, os-level artifacts (search indexes, thumbnails, backups you configured), or data recoverable by forensic tools on some storage hardware. destroyed means removed, not forensically shredded.

mortalsystems
local-first · no account · no telemetry · your identities never leave your machine