Skip to content
AIGP

RFC-012: Artifact Lifecycle Protocol (ALP) — 10. Integration with AIGP and ACP

AIGP Specification › RFC-012: Artifact Lifecycle Protocol (ALP) › 10. Integration with AIGP and ACP

← 9. Storage · Section index · 11. Summary →

10. Integration with AIGP and ACP

ALP does not operate in isolation. It is the third protocol in the runbook-service governance stack, building on AIGP (RFC-010) and ACP (RFC-011).

10.1 Protocol Stack

                  ALP (RFC-012)
          Artifact Lifecycle Protocol
   CREATE  PROMOTE  EXECUTE  ARCHIVE


   Controls: What artifacts exist, who approved them,
             when they run, and what happens if they fail


                        artifacts informed by context


                  ACP (RFC-011)
          Agentic Context Protocol
   FETCH  ASSEMBLE  DELIVER


   Controls: What the agent knows


                        context fetches governed by AIGP


                  AIGP (RFC-010)
          AI Governance Protocol
   REGISTER  REQUEST  RECORD


   Controls: What the agent can do

10.2 End-to-End Flow

1. Agent receives task from orchestrator


2. ACP assembles context (conversion gaps, governance posture, user entitlements)
    Each fetch is an AIGP REQUEST  ALLOW  RECORD


3. Agent invokes AI model to generate artifact
    AIGP REQUEST (can I invoke claude-opus for artifact_generation?)  ALLOW
    AIGP RECORD (invoked claude-opus, 4200 input / 1800 output tokens)


4. ALP CREATE  agent registers artifact + compensation in DRAFT


5. ALP PROMOTE  agent submits DRAFT  REVIEW


6. ALP PROMOTE  approver promotes REVIEW  APPROVED
    Approval authority determined by artifact type + blast radius (7)


7. ALP EXECUTE  orchestrator executes approved artifact
    Hash verified against approval


8. ALP outcome  COMPLETED or FAILED
    If FAILED  compensation triggered (8)


9. ALP ARCHIVE  artifact moved to terminal state
    Full provenance chain sealed (6)

10.3 Cross-Protocol References

Every ALP artifact carries references to its AIGP and ACP origins:

ALP Field References Protocol
producer.aigp_request_id The AIGP REQUEST that authorized the AI invocation AIGP (RFC-010)
producer.acp_context_id The ACP context assembly that informed the artifact ACP (RFC-011)
producer.agent_id The agent that produced the artifact runbook-service
producer.app_id The application the agent belongs to AIGP (RFC-010)

10.4 Governance Enforcement

ALP operations are themselves AIGP-governed:

Orchestrator  governance-server: AIGP REQUEST (can runbook-service execute artifact art-20260504-001?)
governance-server  Orchestrator: ALLOW (within autonomy limits, blast radius acceptable)
Orchestrator  ALP: EXECUTE art-20260504-001
ALP  governance-server: AIGP RECORD (executed art-20260504-001, COMPLETED, 150s)

If governance-server returns DENY (e.g., autonomy limit exceeded, cost ceiling reached), the orchestrator MUST NOT execute the artifact.

10.5 Protocol Comparison

Aspect AIGP (RFC-010) ACP (RFC-011) ALP (RFC-012)
Purpose Govern AI invocations Assemble agent context Govern artifact lifecycle
Controls What AI can DO What AI can KNOW What artifacts EXIST and EXECUTE
Participants App governance-server Provider Assembler Receiver Agent Approver Orchestrator
Auth HMAC-SHA256 HMAC-SHA256 HMAC-SHA256
Storage DynamoDB Provider-native DynamoDB + S3
Integrity HMAC signatures Schema validation Hash-chain signing
Compensation N/A N/A Mandatory for executables

← 9. Storage · Section index · 11. Summary →