Files
Bo 021b41c951 Skills only: cut the RPI workflow script and the machinery around the loop (#1105)
## Skills only: cut the RPI workflow script and the machinery around the
loop

#1104 landed the right ideas in the wrong form. This repository is
skills only: a skill is an instruction to a system, models route and
judge, and deterministic checks exist where reality is deterministic
(digests, tests, gates, "is this file tracked"). #1104 built a workflow
script and a set of schemas, enums, and engines where instruction was
wanted, and then spent four judge rounds hardening them. This PR deletes
that and keeps the ideas as instruction.

**Deleted.** `workflows/rpi.js` and everything that existed only to
exercise it: its probe harness in the product-boundary suite, the
convergence-law and glob-intersection fixture corpora, the cathedral
canaries that pinned its mechanisms, and the pointers to it.

**Reverted to the #1099 form.** `skills/rpi/scripts/run_once.py` and its
tests: the repair law as accepted in the loop restore, without the
class-law machinery, the snapshot verification, or the cross-leg checks.

**Kept.** `docs.claims-tracked` (a blocking gate that caught a real
stale claim on its first run), `scripts/evidence-orphans.sh` (a receipt
a shell script computes), the optional `findings[].class` field on
`verdict.v2` (a word a validator writes), and the corrected harvest-note
sentence.

**Kept as instruction.** The rpi, plan, implement, validate, council,
learn, and boundaries contracts and `docs/architecture/rpi-traversal.md`
now say, in plain sentences a model follows: a risky change gets one
fresh judge on the frozen plan before Implement; validators name a class
per finding and a returning class means go back to Plan; two judges
disagreeing is the orchestrator's decision made in the open, with both
reads in the report and a risky surface still needing both to pass; the
orphan receipt runs after Implement and each repair and rides in the
check receipts; a doc sentence that says published, pinned, or proven is
a claim to check; Learn proposes a check for any repeating finding
class.

**Evidence on the tip.** Regen check clean; rpi unit tests; cathedral
gate; routing goldens; token budgets; coverage 1 of 12; Go bar; full
gate green with a HEAD-built binary; CI's bats command green;
gate-tightening ratchet. One fresh read by Fable 5.1, asked in plain
language for what it found, recorded in the PR thread.
2026-09-06 01:32:51 +00:00

28 lines
1.5 KiB
JavaScript

export const meta = {
name: 'operating-loop',
description: 'Retired compatibility tombstone: the seven-move operating-loop workflow was replaced by distinct workflows',
whenToUse: 'Never — this name is kept only so existing invocations fail with a deterministic migration message instead of silently running retired doctrine.',
phases: [
{ title: 'Migration notice', detail: 'fails immediately with replacement pointers' },
],
}
// The seven-move operating-loop conveyor is retired. Its arguments (shape /
// wave / ratchet moves, replan and retry budgets) do not map onto the RPI
// traversal's one-experiment contract, so nothing is translated automatically:
// choosing the replacement shape is the caller's decision.
//
// - One bounded experiment, independently judged: the `rpi` skill
// (skills/rpi/SKILL.md), which the model follows directly.
// - Multi-bead repository delivery orchestration: workflows/ship-beads.js,
// or a caller-selected software factory operated through its own doors.
//
// The former doctrine page moved to docs/architecture/rpi-traversal.md.
throw new Error(
'workflows/operating-loop.js is retired. ' +
'For one bounded experiment follow the rpi skill (skills/rpi/SKILL.md); ' +
'for multi-bead delivery use workflows/ship-beads.js or a caller-selected factory. ' +
'Arguments are not translated automatically (the seven-move shapes are incompatible with one RPI traversal). ' +
'See docs/architecture/rpi-traversal.md.'
)