docs(executive-loop): M21 Executive Operating Loop — Hermes-side contracts - #8
Merged
Merged
Conversation
…racts Counterpart to mission-control-v0 PR #20 (m21-executive-operating-loop). Records the Mission Control <-> Hermes seams as contracts only: * Morning/Evening Packet consumer mapping onto the chief_of_staff MorningBrief/EveningReport contracts (schema major 1; all M21 fields additive at 1.1; all-or-nothing parsing preserved). * Escalation <-> Executive State Machine mapping (CONTINUE/PAUSE/ NEEDS_CHAD -> events; SafetyRisk >= HIGH -> ESCALATE; safety is never waved through; UNKNOWN semantics aligned with degraded/contradicted). * Opportunity Scout as the reserved MC inbox feed (existing EXTENSION_POINTS slot; deterministic both sides; no reranking; expert-witness rejection; engine never fetches). * Memory Graph as a reserved evidence feed via MC's governed recorder (source hermes-agent already allowlisted; knowledge-growth stays UNKNOWN until wired). * Executive Coach consumption through the LEARNING intent. * Invariants: evidence or silence; determinism; mutation boundaries (each side writes only its own store); attention economy; never chase autonomously; expert-witness isolation. No runtime coupling, no code changes, no packaging change, no new dependencies — this document is the entire diff. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
🔎 Lint report:
|
13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
The Hermes counterpart of mission-control-v0 PR #20 (M21: Executive Operating Loop). One new document —
docs/executive-operating-loop-contract.md— recording the Mission Control ⇄ Hermes seams as contracts only. This document is the entire diff.Seams specified
chief_of_staffMorningBrief/EveningReport consumer contracts (PR #5, interface-only). Schema major 1; all M21 fields additive atcontract_version: 1.1; all-or-nothing parsing preserved.CONTINUE/PAUSE/NEEDS_CHADmap 1:1 onto MC'sexecutive_state.pyevents;SafetyRisk ≥ HIGH→ESCALATE→ a state with no CONTINUE row (safety is never waved through). UNKNOWN semantics aligned withdegraded/contradicted.EXTENSION_POINTS["opportunity-scout"]slot (POST /opportunities, allowed sources only, expert-witness rejected). Deterministic rankings on both sides; neither reranks the other.hermes-agentsource; MC'sknowledge-growthdimension stays UNKNOWN until wired.LEARNINGconversation intent consumes the Morning Packet'slearning_recommendation; EXECUTIVE_COACH.md doctrine satisfied by construction.Hard rules honored
chief_of_staffstays out of the wheel), zero new dependencies (uv.lockuntouched).🤖 Generated with Claude Code