Skip to content

    Type a page, a command such as keryn scan, or a rule id.

    Journeys

    View as Markdown

    A guide answers one question. A journey takes you from a question to something you can show a colleague. Each one runs on a small repository written for the page, uses real output (every command block is run against the CLI before the site is published), and ends with what you proved: the edge or trust boundary you looked at, and how well.

    The Keryn CLI, git, and jq for the steps that read JSON. The AI engineer journey also uses the Trust Canvas in a browser. Nothing is uploaded: the scans and the canvas run on your machine, and the one step that can send findings to a model is a button you press and confirm.

    The journeys link to these instead of repeating them: the edge section for trust boundaries, edge kinds and chains, the rule catalog for what each rule inspects, and the taxonomies for how rules map to OWASP, CWE and NIST AI RMF entries.