Canon term · Identity & discovery

Trust Boundary

The line across which assumptions about trustworthiness change, and at which input must therefore be validated and authority re-established.

  • StatusIndustry term
  • AdoptionWidely used
  • LayerGovernance

Why it matters

Multi-agent systems multiply boundaries faster than most architectures document them. Every delegation from one agent to another crosses one, and the practical question is whether authority is re-checked at the crossing or silently inherited.

Where it comes from

Long-standing in security engineering; applied to agents from 2025 onward.

No published instrument defines this term yet; the note above is its origin.

What it is not

These are routinely confused with Trust Boundary. The distinctions have consequences for how a system is governed.

  • Network perimeter

    A perimeter is topological. A trust boundary is semantic and frequently sits inside a single process.

How it connects

What relies on it

MARQUE questions it addresses

  • AuthorityWhat is the agent permitted to commit, and who granted that?

Connected through the MARQUE (a reference framework organized around eight questions) crosswalk, an editorial mapping. These objectives from the Financial Services AI Risk Management Framework are assigned to the same questions that this term addresses. The ones sharing most of this term's vocabulary are shown first, as a reading aid. The assignment is to the question, not to the term: the source does not map this term to any objective directly.

Question: Authority · 39 control objectives assigned

  • GV-2.1.1AI Risk Management Roles and ResponsibilitiesGovern
  • GV-2.2.2Mandatory AI Risk Management TrainingGovern
  • GV-1.4.2AI Risk Documentation StandardsGovern
All 39 objectives assigned to Authority

Cite and reuse

Cite the identifier QIS-TERM-00004, not the URL: identifiers are stable, URLs may change. This entry is free to read, quote and index under the dual license. Corrections sent to editor@qisfund.com are published.

Technical details: identifier, graph relationships and record
QIS-TERM-00004: outbound relationships as published in api/graph.json and api/lexicon.json
PredicateTarget identifierTargetPredicate meaning
constrainsterm:task-delegationTask DelegationThe subject bounds what the object may do.
addressesmarque:authorityAuthorityThe subject speaks to the object as a question or concern.
Canonical identifier
QIS-TERM-00004
Tier
Canonical industry term
Domain · layer
Identity & discovery · Governance
Semantic aliases
None recorded
First published
2026-08-02
Last reviewed
2026-08-02 · 180-day cycle