ctxgrd
  • Capabilities
  • Rules
  • Guides
Get started
Guides

Guides

Task-focused guides for operating ctxgrd — getting started, adopting compliance packs, keeping packs current, and gating an agent loop on a feature's done-signal.

  • how-to

    Adopting the GDPR and HIPAA compliance packs

    Adopting the GDPR and HIPAA compliance packs Add structured linting for GDPR Art. 28/30/35 documentary artifacts and the HIPAA Security Rule BAA register to a …

  • reference

    CLI reference

    CLI reference ctxgrd 2.1.0 – every command, its flags, the exit-code contract, and the output formats. Rule codes are not enumerated here. ctxgrd rules …

  • how-to

    Generating a changelog from the document graph

    Generating a changelog from the document graph Turn CHANGELOG.md into a generated projection of your BUG/ADR/CR documents instead of a file you edit by hand. …

  • tutorial

    Getting started with ctxgrd

    Getting started with ctxgrd Lint your first structured-markdown record – an ADR, PRD, runbook, or any .md file with <NAMESPACE>-<number> …

  • explanation

    How ctxgrd decides what to lint

    How ctxgrd decides what to lint ctxgrd is quiet by default – and this is on purpose. Understanding why requires understanding the single design decision …

  • how-to

    Keeping adopted packs current

    Keeping adopted packs current Reconcile your ctxgrd.toml pack blocks with a pack’s current shape after a ctxgrd upgrade, without losing your own edits. …

  • how-to

    Linting C4 architecture diagrams

    Linting C4 architecture diagrams Enforce the “declare your level” convention from Simon Brown’s C4 model across every diagram doc in a …

  • how-to

    Linting deep-research reports

    Linting deep-research reports Keep every deep-research report in your repository evidence-honest – a sources section present, a limitations section at …

  • how-to

    Linting Domain-Driven Design docs

    Linting Domain-Driven Design docs Enforce the strategic-DDD shape – a Bounded Context’s language and boundaries, and the relationships between …

  • how-to

    Linting non-markdown facts with external sources

    Linting non-markdown facts with external sources Gate facts that live outside markdown – rows in JIRA, pages in Notion, clauses traced in a Prolog …

  • how-to

    Polling a feature done-signal in an agent loop

    Polling a feature done-signal in an agent loop Gate an agent loop on one feature’s completion – not the whole project’s – using ctxgrd …

  • how-to

    Tracking a roadmap with ctxgrd

    Tracking a roadmap with ctxgrd Lint a Now-Next-Later product roadmap as one file per initiative, with the horizon, the owner, and cross-initiative blocking all …

  • how-to

    Verifying agent work with ctxgrd

    Verifying agent work with ctxgrd Wire ctxgrd as an external check on an AI coding agent, so that “I’m done” has to survive something the agent …

  • explanation

    Why is ctxgrd needed?

    Why is ctxgrd needed? If you already keep architecture decision records, you have probably not felt a need for a linter. The documents are written, reviewed, …

  • how-to

    Writing custom rules

    Writing custom rules Enforce a project-specific check ctxgrd doesn’t ship – in any language you can write an executable in – and wire it into …

ctxgrd.

A tool from Aktagon. Source-available under the Elastic License 2.0.

Docs
  • Guides
  • Examples
Project
  • GitHub
  • Releases
  • License (Elastic-2.0)
Aktagon
  • aktagon.com
  • Signals
  • contact@aktagon.com
© 2026 Aktagon Ltd.