Skip to main content

OpenClaw Config Template Pack (AEEF Overlay)

This page provides a real AEEF template pack for implementing OpenClaw as the execution surface for your AEEF agents.

These files are AEEF overlay templates. They are not guaranteed to match OpenClaw's native configuration formats directly. Use them as governance and orchestration reference contracts when building your OpenClaw integration.

What Is Included​

Pack folder:

  • reference-implementations/transform/openclaw-template-pack/

Files:

  • active-tasks.schema.json -- schema for a deterministic task registry (active-tasks.json)
  • monitor-loop-contract.yaml -- monitor loop behavior contract (checks, retry policy, escalation, outputs)
  • monitor-loop-checklist.yaml -- operational readiness and run checklist
  • route-policy-4-agent.yaml -- AEEF routing/gate policy for the 4-agent starter path
  • route-policy-11-agent.yaml -- AEEF routing/gate policy for the full 11-agent path

Intended Use​

Use this pack when implementing the patterns described in:

Path Selection​

Path A: 4-Agent Starter​

Use route-policy-4-agent.yaml when you are starting with:

  • product-agent
  • developer-agent
  • qa-agent
  • security-agent

This path is designed for:

  • first OpenClaw rollout
  • one repo pilot
  • fast feature/bug delivery with strong PR gates

Path B: Full 11-Agent Orchestration​

Use route-policy-11-agent.yaml when you are implementing the full AEEF Transformation model with stage ownership and enterprise gating across all 11 agents.

Suggested Implementation Sequence​

  1. Validate your task registry structure using active-tasks.schema.json.
  2. Implement the deterministic monitor loop against monitor-loop-contract.yaml.
  3. Run the monitor loop readiness checks in monitor-loop-checklist.yaml.
  4. Apply route-policy-4-agent.yaml for your first pilot repo.
  5. Migrate to route-policy-11-agent.yaml only after stable metrics and gate compliance.

File References (Pack)​

  • reference-implementations/transform/openclaw-template-pack/active-tasks.schema.json
  • reference-implementations/transform/openclaw-template-pack/monitor-loop-contract.yaml
  • reference-implementations/transform/openclaw-template-pack/monitor-loop-checklist.yaml
  • reference-implementations/transform/openclaw-template-pack/route-policy-4-agent.yaml
  • reference-implementations/transform/openclaw-template-pack/route-policy-11-agent.yaml

Implementation Notes​

  • The route policies assume AEEF gate bundles and traceability metadata are enforced in CI and PR workflows.
  • The monitor loop contract assumes deterministic checks (tmux, PR, CI, DoD) and explicit retry reason classification.
  • The task registry schema is designed to carry both operational status and AEEF traceability fields (agent-id, prompt refs, skill usage).
Last updated on by BalrogEg