GOVERNANCE & TRUST · SECURITY ARCHITECTURE
Know where the state came from. Keep control of where it runs.
ClueState is engineered with rigorous tenant boundaries, hashed credentials, immutable provenance records, and complete provider freedom.
TENANCY & ISOLATION
Strict Workspace Partitioning
Every entity, topic schema, episode interaction, memory claim, and evidence row is tagged with an immutable workspace identifier. Cross-tenant leakage is prevented at both the application layer and database query filter layer.
CREDENTIAL SECURITY
SHA-256 Hashed API Keys
API keys (cs_live_...) are displayed exactly once at generation time. Only their cryptographic SHA-256 hashes are persisted in the database. Ingestion keys are strictly scoped to the data plane and cannot be used to escalate privileges or manage keys.
PROVENANCE & AUDIT
Verifiable Evidence Offsets
Every extracted memory contains exact character offsets (char_start, char_end) linking the claim back to the source episode. ClueState verifies that the excerpt exists in the stored text and hashes the content to ensure tamper-evident traceability.
DEPLOYMENT INDEPENDENCE
Zero LLM Lock-In
ClueState maintains state semantics independently of any single AI model. Connect commercial providers (OpenAI, Anthropic, Gemini) or operate 100% on-premises using local Ollama models in air-gapped environments.
Inspect the Codebase & Security Policy
Full transparency under the permissive Apache 2.0 open-source license.