Resolve Hermes ↔ OpenClaw directionality and pushback rules

[marcusglee11]

Source

Architecture Normalization Issue 4 — derived from docs/10_meta/Architecture_Normalization_Targeted_Issue_List_2026-04-24.md

Scope

Define whether peer COOs may direct one another, what is authoritative vs advisory, and how pushback/escalation works.

Source docs

• docs/10_meta/Architecture_Normalization_Reconciliation_Packet_2026-04-24.md
• docs/10_meta/COO_Authority_Contract_Draft_2026-04-24.md
• Relevant runtime CLI / COO command surfaces

Acceptance criteria

• Peer directionality class explicit
• Active/standby interaction clear
• Pushback and escalation rules explicit

Required repo surfaces before merge

• Canonical governance/architecture docs
• docs/10_meta/ARCHITECTURE_SOURCE_OF_TRUTH.md
• Architecture changelog
• ADR if ratified

Authority rules

• Hermes and OpenClaw peer direction is advisory unless re-issued through active COO or CEO authority path