62 lines
1.5 KiB
Markdown
62 lines
1.5 KiB
Markdown
# OpenClaw Hermes Routing Correction Instruction
|
|
|
|
Instruction ID: v1r1c5-hermes-routing-correction-v1
|
|
Version: v1
|
|
Target Agent: openclaw
|
|
|
|
## Objective
|
|
Correct Hermes coordination routing. OpenClaw must actively package AIOS review requests and route them through the configured Hermes communication path instead of asking the user to provide missing context when the request context already exists in GitOps.
|
|
|
|
## Current Architecture
|
|
|
|
OpenClaw is the coordination entry point.
|
|
Hermes is reached indirectly through OpenClaw controlled communication.
|
|
|
|
## Hermes Routing Targets
|
|
|
|
Authorized Hermes communication Chat IDs:
|
|
|
|
- o9cq80wSaJq6utQBkUC4fE1sJWxY@im.wechat
|
|
- o9cq80x9RoA6ljoFZDxg71mS0gDA@im.wechat
|
|
|
|
## Execution Flow
|
|
|
|
1. Read current AIOS GitOps context.
|
|
2. Collect:
|
|
- Baseline version
|
|
- Branch
|
|
- Diff summary
|
|
- Problem description
|
|
- Proposed solution
|
|
- Validation requirements
|
|
3. Send complete review package to Hermes through configured OpenClaw communication channel.
|
|
4. Receive Hermes analysis.
|
|
5. Record review result in GitOps reports.
|
|
|
|
## Current Review Context
|
|
|
|
Baseline:
|
|
V1R1C4
|
|
|
|
Branch:
|
|
patch/self-evolution-agent-orchestration-policy
|
|
|
|
Proposal:
|
|
V1R1C5-agent-os-evolution-proposal
|
|
|
|
## Constraints
|
|
|
|
- Do not ask user for context that already exists in GitOps.
|
|
- Do not treat instruction ID as external skill package.
|
|
- GitOps audit required.
|
|
- No secrets.
|
|
- No direct production changes.
|
|
|
|
## Return
|
|
|
|
Status:
|
|
Hermes Routing:
|
|
Review Context:
|
|
Result:
|
|
Issues:
|