05ae530442
Install current verified harness releases inside Docker, preserve persistent accounts and settings, and provide separate interactive and pipeline model defaults with terminal onboarding and fuzzy pickers. Add Docker-aware authoring transport, Pi stage execution, bounded workflow controls, reliable final-result readback and usage settlement, and finite short-lived CLI pipe draining. Keep dated installation evidence and packaged authoring guidance consistent. Verified with a real Docker installation, both harness stages and interactive authors, the built-in plan/implement/review starter, independent host race/vet checks, installer tests, and packaged skill tests. Generated release receipts stay ignored in clean checkouts.
50 lines
2.3 KiB
Markdown
50 lines
2.3 KiB
Markdown
# Runner-owned limits and shared memory
|
||
|
||
Use these blocks for bounded feedback loops. Never ask a model to count visits,
|
||
increment revision counters, or enforce retry caps. Model verdicts concern current
|
||
work only. Counters are runner audit data, not model input. A fresh session alone
|
||
does not guarantee independent review: explicitly select its input fields.
|
||
|
||
````markdown
|
||
```limits
|
||
{"max_visits":3,"on":["rejected"]}
|
||
```
|
||
|
||
```memory
|
||
{"task":"input.prompt","checks":"planner.checks"}
|
||
```
|
||
|
||
```edges
|
||
approved -> #success
|
||
rejected -> implement
|
||
error -> #failure
|
||
```
|
||
````
|
||
|
||
These blocks accompany a normal review stage's prompt/output/tools/configs.
|
||
Pipelines counts actual visits, ignoring model-generated counters. On visit three,
|
||
`approved` can succeed; `rejected` retains its verdict but routes to `#failure`.
|
||
Visit count, limit decision and original target are retained in `inspect --json`
|
||
and run metadata. `max_visits` accepts 1–5. Every `on` outcome must declare a
|
||
nonterminal edge. Without `on`, entering beyond the cap fails before execution.
|
||
Global 30-step/five-visits-per-stage safety limits still apply.
|
||
|
||
`memory` maps input aliases to `input.FIELD` (original input) or `STAGE.FIELD`
|
||
(latest completed output of that stage **in this run**). A memory block replaces
|
||
previous-stage input with only those fields. Without it, previous output remains
|
||
input. Reads retain source and visit sequence. Missing required fields fail before
|
||
execution. Append `?` to omit an unavailable field, e.g.
|
||
`"feedback":"review.findings?"` for implement's first visit. Self-memory is
|
||
rejected. Limits: 50 bindings; 1 MiB per retained in-memory value map.
|
||
|
||
Implementers can receive task, plan and optional findings. Independent reviewers
|
||
should receive task/acceptance criteria and inspect actual artifacts—not previous
|
||
verdicts, counters, or implementation conversations. Selected content remains
|
||
untrusted data; this cannot prove semantic independence or prevent all injection.
|
||
|
||
Memory is run-local; persisted completed outputs/read provenance are its audit.
|
||
There is no cross-run memory, restart/resume, or hidden replay. New runs/retries
|
||
start fresh. Arbitrary prose is not executable policy. Future AI-assisted
|
||
guidelines validation is **not implemented**; structural validation does not
|
||
recognize every unreliable counting instruction.
|