Understand every
decision.
From your first demo to the boundaries of pre-execution enforcement. Product guides and engineering references, grounded in the MVP1 specification.
Start here
Meet TraceRook
An independent review layer for supported local coding-agent actions.
Read guideTry the native preview
Build the development app and explore a complete, explicitly labeled sample workflow.
Read guideNavigate the dashboard
Use the native interface to understand sessions, evidence, reviews, and integration health.
Read guideCloud Demo
Explore bundled sample data without mistaking a demonstration for real protection.
Read guidePolicy & protection
The decision pipeline
Follow a supported proposal from local inspection to a host-format decision.
Read guideLocal policy & rule families
Understand deterministic evidence, severity routing, and the role of contextual analysis.
Read guideOne-time approvals
A review decision authorizes one exact pending invocation, within its deadline.
Read guideCoverage & failure behavior
Verified protection requires a working callback, a supported tool path, and real evidence.
Read guideClaude & privacy
Analysis with Anthropic Claude
The planned contextual analysis backend: direct Anthropic BYOK, minimized context, and advisory verdicts.
Read guideThe privacy pipeline
Minimize first, redact locally, and reject remote transmission when the final check cannot complete.
Read guideKeys, history & deletion
Separate API key lifecycle, sanitized local history, and integration removal.
Read guideAgent integrations
Claude Code integration
The intended local hook lifecycle and verification requirements for Claude Code.
Read guideCodex integration
Local hook coverage, explicit trust review, and host-compatible decision output.
Read guideSafe configuration changes
Reversible, consent-based hook installation, repair, and removal are part of the security boundary.
Read guideTroubleshooting
Diagnose demo, provider, notification, trust, and coverage states without overstating protection.
Read guideEngineering reference
Native architecture
Three native processes, shared Swift packages, and separate authenticated UI and event transports.
Read guideEvents & IPC contracts
Versioned bounded input, normalized event envelopes, exact fingerprints, and host output.
Read guideTesting & verification
Compilation and fixtures are necessary; real pre-execution behavior is a separate acceptance gate.
Read guideMVP1 status & roadmap
Completed development milestones and the acceptance gates still required for a live beta.
Read guideFAQ & glossary
Straight answers about Claude, local enforcement, demos, permissions, and the current preview.
Read guide