rein-aharness/SCOPE.md
tegwick 363866f3a8 Close out statehub-register bootstrap housekeeping (REIN-A-0001)
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-26 19:46:05 +02:00

52 lines
2.1 KiB
Markdown

# SCOPE
## One-liner
Claude-Code-CLI-driven rein: governed, unattended/scheduled agent runtime.
Formerly `agent-harness`; renamed per glas-harness ADR-001. Deployed live on
Railiance for tenant `binky-control`.
## Core Idea
The single shared, multi-tenant runtime: consumes tasks (local JSON file or
issue-core polling), loads a kaizen-agentic persona, runs a bounded Claude
Code CLI session under a named tool profile allow-list, verifies a local
commit, reports to State Hub and `.kaizen/metrics`. The harness is the only
credential holder and only policy enforcement point for its sessions.
## In Scope
- Instance manifest resolution (`.kaizen/schedule.yml` extensions),
named tool profiles (`green-commit-only`, `blue-mail-triage`)
- Task intake: local task-file (dev) and issue-core polling (production)
- The agentic session itself (`adapter.py`/`runner.py`), including
per-tool-call audit streaming (`--stream-tool-events`,
`HARNESS-WP-0002-T03`)
- kaizen metrics + State Hub progress/token reporting
- Railiance packaging and deployment (`Containerfile`, `deploy/`)
- Two non-Claude, non-agentic side paths: deterministic mailbox scan
(`mail-scan`) and llm-connect-JSON-driven mail-triage/daily-brief
## Out of Scope
- Scheduling and blueprint authoring — stay in `activity-core` and
`kaizen-agentic` respectively (this repo only consumes/loads them)
- Being the glas-harness meta-framework itself — this repo is one
concrete rein under it, not the router
(`glas-harness/docs/adr/ADR-001-rein-harness-family.md`)
- LLM provider abstraction — stays in `llm-connect`
## Current State
`HARNESS-WP-0001` (foundation) and `HARNESS-WP-0002` (rename + glas-harness
alignment, including the live Railiance cutover) are both done. Live-proven
through glas-harness's gateway with a real Claude Code session and a real
verified commit. Deploy artifacts, CLI, and package are all under the
`rein-aharness` name on the live Railiance deployment.
## Getting Oriented
- Start with: `INTENT.md`
- Deploy: `deploy/README.md`
- Agent instructions: `AGENTS.md`
- Workplans: `workplans/`