Skip to content

RFC-010: AIGP Runtime Governance Protocol — 21. Deployment Manifest and Registry

AIGP Specification › RFC-010: AIGP Runtime Governance Protocol › 21. Deployment Manifest and Registry

← 20. Governed Decision Service Pattern · Section index · 22. Pre-Invocation Signal Registry →

21. Deployment Manifest and Registry

21.1 Purpose

A deployment manifest is a signed, versioned snapshot of everything governing a deployment at a point in time.

21.2 Ten Envelope Fields

# Field Content
i governing_selector Which governing specification(s) are active
ii kb_selector Which knowledge base version
iii data_source_selector Which data sources are bound
iv battery_selector Which analysis battery configuration
v runtime_configuration_record Mode, latency bounds, trace settings
vi classification_function_record How verdicts map to outputs
vii effective_date_range Temporal validity window
viii cryptographic_signature Tamper-proof integrity over the manifest
ix aigp_light_posture Embedded runtime config
x consent_tier_and_mode ENFORCE / REPORT / REPORT-TRACE + consent tier

21.3 Manifest Version Tracking

Every RECORD and TRACE message SHALL carry manifest_version_id — the SHA-256 of the active manifest’s canonical JSON (excluding signature).

21.4 Deployment Registry

The server SHALL maintain a deployment registry: one row per enforcement mechanism (name, kind, artifact signature, scope). The architecture_identifier is the SHA-256 over sorted mechanism rows — deterministic regardless of registration order.

21.5 Calibration Attestation Gate

Before first admission, the deployment SHALL pass calibration: convergence criterion, aggregation function, classification function, and divergence threshold evaluated against a certified benchmark. Failure blocks activation.

21.6 Selection Event Log

Every manifest activation, deactivation, and version change SHALL be logged with timestamp, actor, reason. Default retention: 7 years post-manifest-revocation (configurable).



← 20. Governed Decision Service Pattern · Section index · 22. Pre-Invocation Signal Registry →