Six-Layer Harness — bamr87 hub

Six-Layer Harness — bamr87 hub An architecture diagram generated by Archify. Claude Opus · the model · Architecture component · reasoning Claude Opus the model reasoning Guides · CLAUDE.md · AGENTS.md · SCHEMA.md · Hub: bamr87/bamr87 (the harness) · feedforward Guides CLAUDE.md · AGENTS.md · SCHEMA.md feedforward Permissions · fleet.yml caps · draft-only · Hub: bamr87/bamr87 (the harness) · never merge Permissions fleet.yml caps · draft-only never merge Agentic loops · pulse · issues · tokens · evolve · Hub: bamr87/bamr87 (the harness) · bounded Agentic loops pulse · issues · tokens · evolve bounded Fleet · ~40 project repos · Architecture component Fleet ~40 project repos Sensors · drift gate · schema_lint · CI · Hub: bamr87/bamr87 (the harness) · feedback Sensors drift gate · schema_lint · CI feedback Memory · _data/*.yml ledgers · Hub: bamr87/bamr87 (the harness) · committed Memory _data/*.yml ledgers committed Observability · harness_health.yml · Hub: bamr87/bamr87 (the harness) · trip wires Observability harness_health.yml trip wires Human · review · merge · brake labels · Architecture component Human review · merge · brake labels reasoning rules from incidents caps + scopes draft PRs · issues CI + gate results verify snapshots scorecard trip wires merges Hub: bamr87/bamr87 (the harness) Legend Frontend Backend Database Cloud Security External

Guides + Permissions

  • • Standing rules in CLAUDE.md, each traced to an incident
  • • Every cap lives in fleet.yml, asserted by fixture tests
  • • Draft PRs only; no loop ever merges

Loops + Sensors

  • • A deterministic plan step precedes every agent run
  • • Drift gate, schema_lint, and CI verify agent output
  • • Escalation is a label or a fallback issue, never silence

Memory + Observability

  • • The filesystem is the memory: committed YAML
  • • dash harness scores the fleet offline from those files
  • • A tripped wire is attention; the loops own the fix