Skip to content

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

    Edges, boundaries and paths

    View as Markdown

    Trust lives in relationships. A model, a repository, an agent or a person is not safe or dangerous alone: risk appears where one can reach, call, read, change or act for another. Keryn models those edges first and the things they connect second. This section is the manual for that model. Why the edges is the short version.

    user texta promptsendstrust boundary
    Every edge has a kind, two ends, an authority and evidence.
    • A kind, one of eight: reaches, calls, reads, writes, sends, grants, depends on, trusts.
    • Two ends, the source and the target.
    • The authority under which it exists: who may make it happen.
    • Its evidence: the file, line, test or review that supports it, or an explicit statement that there is none.

    An inventory of components, the AI-BOM, is still there. It is the list of nodes the edges attach to.

    You want to know Read
    Where authority changes in an AI system, and what supports each crossing Trust boundaries
    What the eight kinds mean, with a runnable example of several Edge kinds
    How edges combine into paths, chains and graphs, and where to put a guard Paths, chains and chokepoints
    What a model may and may not do when it reviews findings Agentic triage
    What Keryn will not do, stated as guarantees Guarantees
    How to draw your own system and analyse it Model your agent on the Trust Canvas
    Untrusted inputAgentToolDatabasesendscallschokepointwrites
    A chain. Mint cuts mark boundaries. The heavy edge is the chokepoint: guard it and the chain breaks.

    A boundary is one edge. A chain is edges in order. A chokepoint is the element many chains share. Keryn keeps the evidence on every edge, so a chain can be proven, challenged or broken.

    The edge model is the direction of the product, and the surfaces show it unevenly. Today:

    • Rules report a source-to-sink path inside a file and across files, with the proof level.
    • Rule metadata names the edge and the boundary class each rule inspects.
    • Keryn Web lists the routes that reach a model and the tools each can call, and exports the evidence graph.
    • The workflow analyser reports risky combinations in agent exports.
    • The Trust Canvas holds the full model: boundaries, reach, chains, chokepoints.

    There is not yet one model of every edge shared by all of these, and cross-file reach is bounded. See what Keryn does not do.