3 Commits

Include renames

Author	SHA1	Message	Date
jerome	484ea00597	fix: resolve registry issues — placeholders, missing postconditions, DAG/escalation/CB injection ... - Replaced <pve-api> placeholder with actual Proxmox API endpoint - Replaced <service-endpoints> with actual service URLs in infrastructure-monitoring - Replaced vague 'send test DM' with actual API call in zulip-health - Added 3 postconditions to hermes-agent-baseline (was empty) - Simplified verify commands in hermes-config-template and hermes-agent-baseline - Updated provision-cron-jobs.py to match actual registry schema for: - Circuit breaker: max_retries, trip_action, window - Escalation: severity levels (info/warning/critical/fatal) - DAG: depends_on array All 10 scheduled contracts now pass validation.	2026-07-13 19:07:23 -04:00
jerome	8abbd6f001	fix: add multi-dimensional index to contract-registry.yaml ... Adds index.by_domain with pm2-self-heal and disk-gc-threat-response in infrastructure group. All 28 contracts now accounted for in every index dimension: by_category, by_domain, by_owner, by_trigger, by_sensitivity.	2026-07-13 16:39:52 -04:00
jerome	cca5a57265	feat: add contract-registry.yaml — OpenProse enforcement index ... 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	2026-07-13 15:40:10 -04:00