Start with one question.
Reference layer for AI Agent Lifecycle, Agentic Lifecycle Governance, Missing Regulatory Objects, RCCS-M, ALCS, MPLP, Deterministic Delivery, and AI agent governance terms.
- 01Canonical category
- 02Primary concept stack
- 03Entity mesh
- 04Engineering terms
- 05Supporting terms
Move from the category to the evidence surface.
Concepts are the reference layer connecting the author identity, lifecycle category, definitions, projects, and evidence.
- 01IdentityAuthor and site anchor
- 02CategoryAI Agent Lifecycle
- 03ConceptsDefinitions and relations
- 04ProjectsProtocol and proof paths
- 05EvidenceCitations and artifacts
Concepts is the reference layer behind the AI Agent Lifecycle mainline. It is not the main human journey.
Use this page to distinguish the primary concept stack from supporting terms. The main public journey still starts at /lifecycle/.
For quote-ready citation anchors, see Definitions. For the visible semantic navigation surface, see Concepts Map / Entity Mesh. For engineering practice anchors, start with Deterministic Delivery. For regulatory and enterprise governance mappings, open AI Agent Governance and Lifecycle Responsibility.
Start with the lifecycle category.
AI Agent Lifecycle defines the accountable lifecycle of agent work from intent to accepted outcome.
Primary Concept Stack
These terms are the first-stage public concept stack. Everything else is supporting architecture.
AI Agent Lifecycle
AI Agent Lifecycle defines the accountable lifecycle of agent work from intent to accepted outcome.
Open definitionAgentic Delivery
Agentic Delivery names the missing layer between agent execution and accountable outcomes.
Open definitionDeterministic Delivery
Deterministic Delivery is the discipline of making agentic work scoped, configured, authorized, evidenced, reviewable, accepted, remediable, and rollbackable across a lifecycle. It does not require deterministic model outputs.
Open definitionAgentic Lifecycle Governance
Agentic Lifecycle Governance explains why AI agent and multi-agent compliance requires lifecycle responsibility objects, Missing Regulatory Objects, RCCS-M, and ALCS.
Open concept coreMPLP
MPLP is the lifecycle protocol path for making Agentic Delivery explicit, governable, and auditable.
Open protocol pathMulti-Agent Lifecycle Governance
Multi-Agent Lifecycle Governance is the multi-agent form of Agentic Delivery: governing responsibility, authorization, evidence, and outcome acceptance across agents, roles, projects, and lifecycle stages.
Open lifecycle field analysisConfirmation Boundary
The lifecycle point where autonomous execution becomes authorized responsibility.
Open definitionEvidence Chain
Structured proof that agent work can be reviewed, replayed, disputed, and accepted.
Open definitionSemantic Loss
The degradation of intent, constraints, responsibility, and evidence across lifecycle handoffs.
Open lifecycle field analysisGlobal AI Compliance Entity Mesh
Definition-first entity pages for the white paper's core governance object layer.
Missing Regulatory Objects
Missing Regulatory Objects are lifecycle responsibility objects that model-centric governance does not consistently define for AI agent and multi-agent systems.
Open entity pageRCCS-M
RCCS-M is the MRO-adjusted Regulatory Compliance Coverage Score for assessing whether governance can express lifecycle responsibility objects.
Open entity pageALCS
ALCS is the Agentic Lifecycle Conformance Score for assessing whether lifecycle responsibility stays coherent across agentic work.
Open entity pageLifecycle Responsibility Objects
Lifecycle Responsibility Objects are the object layer that keeps AI agent work tied to authority, evidence, accepted outcome, substitution, dispute, and remediation.
Open entity pageEvidence Chain
Structured proof that agent work can be reviewed, replayed, disputed, and accepted.
Open entity pageAccepted Outcome
Accepted Outcome is the lifecycle point where AI agent work becomes reviewable, attributable, and accepted responsibility.
Open entity pageAuthority Boundary
Authority Boundary defines who may authorize agentic action, under what scope, and with what responsibility record.
Open entity pageDeterministic Delivery and Agent Architecture
Engineering-practice pages for scoped, configured, verifiable, rollbackable, and lifecycle-governed agent work.
Deterministic Delivery
Deterministic Delivery defines how agentic work can be scoped, authorized, evidenced, reviewed, accepted, remediated, and rolled back without requiring deterministic model outputs.
Open engineering termRollbackable Agent Workflows
Rollbackable Agent Workflows define how agent work can return to a known lifecycle state with authority, evidence, accepted outcome, and remediation records intact.
Open engineering termVerifiable AI Agents
Verifiable AI Agents are agent systems whose lifecycle state can be inspected across intent, authority, evidence, review, accepted outcome, dispute, replay, and remediation.
Open engineering termConfigurable Agent Governance
Configurable Agent Governance defines how governance profiles, authority limits, tool constraints, context boundaries, and substitution rules remain evidence-linked.
Open engineering termAgent Architecture Governance
Agent Architecture Governance maps human roles, agent roles, tools, evidence, accepted outcomes, and lifecycle responsibility boundaries beyond orchestration topology.
Open engineering termSupporting Terms
These terms clarify the mainline. They are not first-stage public concepts.
Lifecycle Role Decomposition
Lifecycle Role Decomposition translates human work roles into lifecycle responsibility boundaries that agent systems can execute, confirm, trace, roll back, and accept.
Open supporting termLifecycle-Governed Agent Workflow
Lifecycle-Governed Agent Workflow is a protocol-generated workflow model where human work models become confirmable, traceable, rollback-aware, and delivery-aware agent work.
Open supporting termIntent Drift
Intent Drift describes how agent work gradually separates from the original human objective, constraints, and accepted outcome criteria.
Open supporting termContext Drift
Context Drift describes the loss, staleness, or misweighting of project context as agent work moves across sessions, tools, and summaries.
Open supporting termDeterministic Delivery
Deterministic Delivery defines how agentic work can be scoped, authorized, evidenced, reviewed, accepted, remediated, and rolled back without requiring deterministic model outputs.
Open supporting termRollbackable Agent Workflows
Rollbackable Agent Workflows define how agent work can return to a known lifecycle state with authority, evidence, accepted outcome, and remediation records intact.
Open supporting termVerifiable AI Agents
Verifiable AI Agents are agent systems whose lifecycle state can be inspected across intent, authority, evidence, review, accepted outcome, dispute, replay, and remediation.
Open supporting termConfigurable Agent Governance
Configurable Agent Governance defines how governance profiles, authority limits, tool constraints, context boundaries, and substitution rules remain evidence-linked.
Open supporting termAgent Architecture Governance
Agent Architecture Governance maps human roles, agent roles, tools, evidence, accepted outcomes, and lifecycle responsibility boundaries beyond orchestration topology.
Open supporting termAI Agent Governance
AI Agent Governance defines the authority, confirmation, evidence, and review conditions that make delegated agent work accountable.
Open supporting termProtocol Engineering
Protocol Engineering makes intent, context, plans, confirmations, traces, evidence, and accepted outcomes explicit for AI agent systems.
Open supporting term