Charter rein-openweights
Agentic tool-use harness for current open-weight models via OpenRouter/ llm-connect, as an alternative to frontier-model-vendor harnesses (Claude Code, Grok CLI, Codex/GPT CLI). Chartered by glas-harness ADR-001. Local scaffold only, no Forgejo remote yet. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
commit
ac5407a83e
3 changed files with 138 additions and 0 deletions
77
workplans/REIN-OW-WP-0001-bootstrap.md
Normal file
77
workplans/REIN-OW-WP-0001-bootstrap.md
Normal file
|
|
@ -0,0 +1,77 @@
|
|||
---
|
||||
id: REIN-OW-WP-0001
|
||||
title: "Bootstrap: minimal open-weight agentic loop"
|
||||
status: proposed
|
||||
---
|
||||
|
||||
First working milestone for rein-openweights: prove an agentic tool-use
|
||||
loop against a current open-weight model via OpenRouter/llm-connect,
|
||||
comparable in scope to rein-aharness's `green-commit-only` profile, ready
|
||||
to implement the glas-harness rein contract once
|
||||
`glas-harness/GLAS-WP-0001-T01` defines it.
|
||||
|
||||
## Task: Pick the starter open-weight model + OpenRouter path
|
||||
|
||||
Confirm `llm-connect` already supports the intended model class (check
|
||||
its existing OpenRouter integration, used today by rein-aharness's
|
||||
mail-triage/brief-daily paths for structured JSON — but not for a
|
||||
multi-turn tool-use loop). Identify gaps: streaming tool-call support,
|
||||
function-calling schema compatibility for the chosen open-weight model.
|
||||
|
||||
```task
|
||||
id: REIN-OW-WP-0001-T01
|
||||
status: todo
|
||||
priority: high
|
||||
```
|
||||
|
||||
## Task: Minimal agentic loop
|
||||
|
||||
Implement plan → tool call → observe → repeat with a hard tool allow-list
|
||||
matching rein-aharness's `green-commit-only` (Read/Write/Edit/Glob/Grep +
|
||||
local git add/commit/status/log/diff, no push/network/shell), bounded by
|
||||
a turn/token budget (reuse `llm-connect`'s `BudgetTracker` the way
|
||||
rein-aharness's runner does).
|
||||
|
||||
```task
|
||||
id: REIN-OW-WP-0001-T02
|
||||
status: todo
|
||||
priority: high
|
||||
```
|
||||
|
||||
## Task: Success criterion + reporting
|
||||
|
||||
Mirror rein-aharness's model: a local git commit is the sole success
|
||||
signal, State Hub progress/token event on completion, metrics written in
|
||||
a comparable format so the two reins are measurable side by side.
|
||||
|
||||
```task
|
||||
id: REIN-OW-WP-0001-T03
|
||||
status: todo
|
||||
priority: medium
|
||||
```
|
||||
|
||||
## Task: Credential brokering
|
||||
|
||||
Resolve per glas-harness `GLAS-WP-0001-T06`: OpenRouter/llm-connect
|
||||
credential acquisition either brokered by glas-harness or done directly
|
||||
here via OpenBao/ops-warden. Do not hardcode a choice before that ADR
|
||||
addendum lands.
|
||||
|
||||
```task
|
||||
id: REIN-OW-WP-0001-T04
|
||||
status: todo
|
||||
priority: medium
|
||||
```
|
||||
|
||||
## Task: Forgejo repo creation
|
||||
|
||||
This repo is local-only. Create `coulomb/rein-openweights.git` on
|
||||
Forgejo and wire the remote once T02 has something worth pushing —
|
||||
coordinate with the operator (repo creation is not something this
|
||||
session can do unattended).
|
||||
|
||||
```task
|
||||
id: REIN-OW-WP-0001-T05
|
||||
status: todo
|
||||
priority: low
|
||||
```
|
||||
Loading…
Add table
Add a link
Reference in a new issue