glas-harness/SCOPE.md
tegwick 7a3c8669c7
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
Fix ADR-001 workplan reference after HARNESS-WP-0002 rename
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-26 12:33:07 +02:00

731 B

SCOPE

This file was generated by statehub register. Refine it as the repository boundaries become clearer.

One-liner

Meta-framework routing between concrete agent-harness backends (reins)

Core Idea

glas-harness exists to provide the capability described in INTENT.md.

In Scope

  • Maintain the repository's primary implementation.
  • Keep docs, tests, and operational metadata current.

Out of Scope

  • Own unrelated adjacent systems.
  • Make irreversible operational decisions without human approval.

Current State

  • Status: active; implementation and stability should be verified by the repo agent.

Getting Oriented

  • Start with: INTENT.md
  • Agent instructions: AGENTS.md
  • Workplans: workplans/