Safety Notes
Known Limitations
These limitations are known, expected, and by design for the alpha phase. Read this before evaluating to set accurate expectations.
Out of scope for alpha
Remediation execution
execution_forbidden=true is enforced everywhere. The system generates plans but never executes them.
Agent configuration via UI
Agents are configured through environment variables and config files only. No UI controls.
Multi-tenant isolation
Single operator assumed. No tenant boundary enforcement in alpha.
External authentication
No SSO, OAuth, or external identity provider. Alpha relies on local network security. Do not expose alpha ports to the public internet without an external proxy.
Production-scale load
Tested for single-digit concurrent users only.
Known gaps
Confidence scores are heuristic
Scores reflect relative model certainty but are not statistically validated against ground truth.
Evidence citations may include stale vault entries
Vault content is not guaranteed fresh. Retention policy and GC timing may leave outdated entries indexed.
Novel incident types
RCA quality depends on similarity to indexed scenarios. Novel incident types may produce lower-confidence outputs.
ChromaDB retrieval quality
Vector store retrieval quality depends on indexed content quality. Sparse or low-signal content yields weaker results.
Write operations via MCP are blocked. No autonomous remediation. No external webhooks.
If you encounter behavior that appears to violate these constraints, report it immediately via Alpha Feedback.