Guides

From CLAUDE.md files to a governed MCP context server: the three maturity levels of agent context, the failure modes of each, and when to move up a level.

A folder-structure and naming convention for engineering documentation in git: requirements, ADRs, change specs, architecture fitness tests, and component docs — the same shapes in every repo topology.

A practical 12-point checklist across four control groups — context delivery, verification, evidence, and access boundaries. Most organisations score under 4 of 12 today.

How Sanitized Publishing works: SystemDox scans every Knowledge Base publish for secrets, PII, internal infrastructure and confidential terms, auto-redacts them into chips backed by an encrypted vault, and reports what to rotate.

A quick guide to installing an authenticator app and enabling two-factor authentication for SystemDox — with recommended free apps for iPhone and Android.

How SystemDox publishing works: turn the markdown in your repositories into a documentation site served at your own workspace subdomain, with a unified landing page and search across every repository and git organisation.

Connect Claude Code, Cursor, or any MCP-compatible AI tool to SystemDox. Get your checks, project rules, specs, and documentation injected into AI context automatically.

How SystemDox indexes architecture knowledge and delivers it to AI coding agents via an MCP Server and static exports.

Learn how SystemDox Checks turn recurring AI mistakes into automated architecture fitness tests that run in CI/CD on every pull request.