Terminology

2205 terms, tools, patterns and metrics an architect is expected to use precisely. Each one gets a short explanation of what it is, and — where it matters — what it is commonly confused with. Search filters as you type; the column headers sort.

All areas2205 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture94 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture86 Cost Architecture & FinOps71 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization71 AI-Era Architecture69 Software Architecture & Engineering71 Architecture Patterns71 Architecture Decision-Making63 The Architect's Meta-Skills61 Delivery & Release Engineering66 Platform Engineering & Developer Experience70 Testing & Quality Architecture66 Data Platform Architecture64 Streaming & Real-Time Data69 Data Governance & Semantics69 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk64

Kind Any concept794 practice734 pattern368 metric125 case-study77 tool62 protocol45

5 terms shown.

Term	Kind	Topic	What it is
Capability Confinement Least-Privilege Agents, Trust Domain Separation, Action Authorisation	concept	Prompt Injection Defence	Limiting what an agent is authorised to do rather than trying to prevent it from being misled - because a model cannot reliably distinguish instructions from data, so the security boundary must sit outside it.
Indirect Prompt Injection	concept	Prompt Injection Defence	An attack in which malicious instructions are placed in content the model will later retrieve, rather than typed by the user.
Least-Privilege Tooling Bounded Tool Permissions	practice	Prompt Injection Defence	Giving each tool the narrowest possible capability and enforcing authorisation at the tool - the decisive control when a model's instructions can be influenced by untrusted content.
Prompt Injection Defence	practice	Prompt Injection Defence	Defending systems where untrusted content reaches a language model that can take actions — a problem of privilege, not of filtering.
Tool Authorisation Boundary Model as Untrusted Proposer, Authorise Outside the Model	concept	Prompt Injection Defence	Authorising every tool invocation against the initiating user's own permissions, outside the model - because the model cannot distinguish instructions from data and no prompt-level defence is reliable.