AI Risk Management Framework
NIST — component or architectural context.
Definition
A bounded technical identity.
A capability lifecycle follows a capability from definition and approval through provisioning, operation, change, retirement, and replacement.
Why it matters
Make the technical question explicit.
Long-lived systems need to know which capability version exists, who may use it, what evidence supports it, when it changed, and how dependents behave when it is withdrawn.
Technical context
Semantic / ontology / capability
This page provides a stable descriptive reference for the stated concept. Implementations, products, operating models, and applicable requirements remain context-specific and replaceable.
Evidence and terminology boundary
Evidence class C.
The cited authority supports component concepts or architectural context. It does not define this exact compound identity; LJP uses the phrase descriptively.
Machine-readable resources
Public identity resources
Namespace manifest · LLM summary · Robots policy · Sitemap
No ontology, API, agent card, MCP endpoint, or executable service is published. JSON-LD describes this page; it is not a formal vocabulary.
Credibility boundary
What this page does not claim.
The identity does not provision, approve, monitor, or retire any operational capability.
This identity is not an agent, workload, sensor, control plane, runtime, operating platform, database, network, or standards authority. It is not an endorsement, certification, or conformance claim.
Library context
Portfolio discovery record
View the Library record. Licensing, stewardship, partnership or acquisition discussions welcome.