feat: add contract-registry.yaml — OpenProse enforcement index
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 5s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 2s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 5s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 2s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 1s
Maps all 28 prose contracts to enforcement categories (compliance, monitoring, remediation, build/deploy, maintenance, reference). Each entry includes: - Trigger mechanism (scheduled, event-driven, passive, on-demand) - Execution protocol (agent, timeout, requires, SOP) - Verification postconditions with commands - Receipt format and storage - Escalation tiers (info/warning/critical/fatal) - Circuit breaker configuration - Dependency resolution (DAG) - Last run status tracking MVP targets: hermes-key-enforcement (compliance) and proxmox-monitor (monitored → disk-gc-threat-response remediation) Related to relay #707: OpenProse Contract Enforcement Process — Draft for Review
This commit is contained in: