44 lines
1.2 KiB
Markdown
44 lines
1.2 KiB
Markdown
# OpenClaw Owner Notification Routing Instruction
|
|
|
|
Instruction ID: v1r1c5-owner-notification-routing-v1
|
|
Version: v1
|
|
Target Agent: openclaw
|
|
|
|
## Objective
|
|
|
|
Implement owner notification routing through configured owner communication channels.
|
|
|
|
## Routing Rules
|
|
|
|
1. OpenClaw must first inspect the owner-bound communication channels already configured in the system.
|
|
2. Select the primary owner communication channel according to system priority configuration.
|
|
3. If the primary channel is unavailable, unhealthy, or delivery fails, automatically fallback to the configured backup communication channel.
|
|
4. Record routing decision and delivery status in GitOps audit records.
|
|
|
|
## Notification Scenarios
|
|
|
|
Notify owner for:
|
|
|
|
- High risk architecture decisions.
|
|
- Agent consensus deadlock.
|
|
- Production-impacting approval requests.
|
|
- Required administrator authorization.
|
|
- Release approval gates.
|
|
|
|
## Constraints
|
|
|
|
- Do not hardcode personal communication identifiers in instruction files.
|
|
- Use configured channel registry only.
|
|
- Do not expose private contact information in logs.
|
|
- Maintain audit trail.
|
|
- GitOps workflow required.
|
|
|
|
## Return Format
|
|
|
|
Status:
|
|
Primary Channel Status:
|
|
Fallback Channel Status:
|
|
Delivery Result:
|
|
Audit Record:
|
|
Issues:
|