26 lines
1.6 KiB
Markdown
26 lines
1.6 KiB
Markdown
# Approval Policies
|
|
|
|
`LifecyclePolicyRevision` is immutable apart from its active selector. Editing requirements creates
|
|
a new revision; existing requests retain their original revision and evidence fingerprint.
|
|
|
|
M12 bootstraps three policies:
|
|
|
|
- `lab-promotion`: exact identity, verified integrity, non-blocked security/license, proven runtime,
|
|
current scheduler readiness and rollback target;
|
|
- `capability-production`: exact production execution approval, completed evaluation, approved
|
|
security/license, scheduler evidence revision, zero critical regressions and rollback target;
|
|
- `project-production`: all capability requirements plus eligible project fit and satisfied project
|
|
production validation.
|
|
|
|
An `ApprovalRequest` freezes declared fields and database-resolved facts. Exact references include
|
|
ArtifactSet, ModelRevision, RuntimeProfile, RuntimeProbe, worker image digest, production execution
|
|
approval, evaluation runs, ProjectFitEvidence, ResourceEnvelope, embedding/pipeline identity,
|
|
migration and rollback target. Claims are checked against resolved relationships; green labels
|
|
cannot substitute for records.
|
|
|
|
Requests are `PENDING`, `APPROVED`, `REJECTED`, `BLOCKED`, `EXPIRED`, `STALE` or `REVOKED`.
|
|
Expiration is evaluated before use. Re-resolving evidence detects changed probes, profiles, fit,
|
|
approvals and other facts and makes the request stale. A deferred ExampleVision production gate produces
|
|
`REQUIRED_EXTERNAL_VALIDATION_NOT_SATISFIED`; security, license and critical regression gates cannot
|
|
be manually waved through by the default production policies.
|