Security and deployment boundary
Know what stays local, what is stored, and what remains yours to secure.
Perseus is a set of components, not one security slogan. Each component has a different data path. Optional transports and integrations change the boundary.
System data flow
The model stays outside Perseus authority.
Workspace sourcesPerseus Context EngineReads and renders an explicit artifact
Decisions and factsPerseus VaultStores governed memory selected by the host
Events and referencesPerseus LedgerRecords supplied evidence and chain state
Component matrix
Separate defaults from opt-ins.
| Component | Reads | Stores | Default transport | Operator responsibility |
|---|---|---|---|---|
| Perseus Context Engine | Authored workspace sources | Only the output/cache paths the operator enables | Local CLI or MCP stdio | Directive trust, output location, optional HTTP/shell/service modes |
| Perseus Vault | Memories submitted by the host | Encrypted entity bodies; plaintext FTS5 index and metadata | Local MCP stdio | Key file, filesystem ACLs, disk encryption, backup, optional HTTP/SSE auth |
| Perseus Ledger | Events and references submitted by integrations | SQLite-backed event chain and configured evidence fields | Local CLI/SDK; other transports are configured separately | Source validity, retention, transport security, reviewer and action authority |
Verified posture
What the public source supports.
- MIT-licensed source for all three components
- Published SBOM materials
- Local default paths with no mandatory Perseus cloud service
- Security policies and vulnerability-reporting path
- Release checksums and provenance material where published
Not claimed
What this does not establish.
- No facility clearance or classified-data authority
- No ATO, cATO, cross-domain approval, or safety certification
- No independent CMMC certification
- No autonomous authority over a model or mission system
- No Government approval created by MIT licensing, SBOMs, or JCP status
Primary documents
Review the source before relying on a summary.
Public-site privacy
This static site does not require an account.
Primary pages are served through GitHub Pages. Public contact actions open the visitor's email client. Product components have their own local data paths and security documents. Optional third-party destinations, package registries, GitHub, and external analyses apply their own policies.