coulomb/rein-aharness
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Rename repo to rein-aharness per glas-harness ADR-001

Browse source 
Repo-identity rename only (directory, git remote, pyproject name,
self-referencing docs). CLI/package/deploy rename tracked separately
in REIN-A-WP-0002-T02 since it touches a live Railiance deployment.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-26 12:28:44 +02:00
parent f770825975
commit 8e700c07de
4 changed files with 107 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

17
INTENT.md
View file

@ -1,9 +1,18 @@
# INTENT
> This file explains why agent-harness exists — the problem it solves, the
> principle that governs its boundaries, and what it must never become.
> Established by DEC-2026-002 (binky-control DecisionQueue, resolved
> 2026-07-17) and ADR-001 in this repo.
> This file explains why agent-harness (repo renamed `rein-aharness`, see
> glas-harness ADR-001) exists — the problem it solves, the principle that
> governs its boundaries, and what it must never become. Established by
> DEC-2026-002 (binky-control DecisionQueue, resolved 2026-07-17) and
> ADR-001 in this repo.
>
> **Naming note (post-rename):** this repo is one of possibly several
> **reins** — concrete harness implementations for different operating
> circumstances, analogous to how "rails" name different workload
> operations models. glas-harness is the meta-framework that routes
> between reins; `rein-aharness` is the Claude-Code-CLI-based rein for
> governed, unattended/scheduled tenant work. See
> `../glas-harness/docs/adr/ADR-001-rein-harness-family.md`.
## Why it exists