We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
docs(wiki): de-pin stale test count in threat model The threat model said '20-test suite'; the suite is now 150 tests. Drop the hard number to match how the rest of the wiki phrases it ('the full pytest suite'), so it can't drift again.
wiki: 3 stragglers — 17→20 in About-the-name / Threat-model / Writing-case-studies
feat: full wiki — Architecture / Operator / Threat model / Roadmap Five pages, sidebar, written as long-form complement to the README: Home landing + project status _Sidebar navigation visible on every page Architecture-deep-dive why the architecture is shaped this way Operator-guide run dart-agent on a real SIFT case Threat-model honest scope of the read-only MCP boundary Roadmap phase 1-4, anti-roadmap (what we refuse) Same voice as the README. No marketing language, no overclaim. The threat model in particular is deliberately honest about what the architecture does NOT defend against.