Pin the authoring guide's worked op-scripts against the release binary #344

Open
opened 2026-07-26 13:55:14 +02:00 by claude · 1 comment
Collaborator

Debt class named by the 2026-07-26 harvest audit (architect drift review): docs/authoring-guide.md now carries several worked op-script examples (the tap example, and the harvest-added LinComb and ConstantCost→CostSum wiring examples), each verified by hand at authoring time by piping it through aura graph build — but none is pinned by a test. A vocabulary or schema change would let them rot silently: the guide would keep teaching op-scripts the binary refuses.

Ask: a test that extracts the guide's fenced op-script JSON blocks and drives each through graph build (and, where the example claims specific introspect --params output, checks that too), so a rotting example fails the suite instead of the next reader.

context: existing debt class, grown by the harvest's two new examples; no current misbehaviour — the examples build today (verified in-cycle).

Debt class named by the 2026-07-26 harvest audit (architect drift review): `docs/authoring-guide.md` now carries several worked op-script examples (the tap example, and the harvest-added LinComb and ConstantCost→CostSum wiring examples), each verified by hand at authoring time by piping it through `aura graph build` — but none is pinned by a test. A vocabulary or schema change would let them rot silently: the guide would keep teaching op-scripts the binary refuses. Ask: a test that extracts the guide's fenced op-script JSON blocks and drives each through `graph build` (and, where the example claims specific `introspect --params` output, checks that too), so a rotting example fails the suite instead of the next reader. context: existing debt class, grown by the harvest's two new examples; no current misbehaviour — the examples build today (verified in-cycle).
claude added the idea label 2026-07-26 13:55:29 +02:00
Author
Collaborator

First concrete instance (harvest-2026-07-26 fieldtest, B1)

The rot class this issue names has its first observed case: docs/authoring-guide.md ~800-821 transcribed multi-regime family ids in a shape the executor does not produce (suffix -r1 with the default regime unmarked; reality is an infix -rK after the window segment with -r0 present even for an implicit default regime). Transcribed output — not just op-script inputs — rots too, so the pin should cover asserted output shapes (family-id/trace-handle lines) where cheap, not only that the examples build. The instance itself was fixed in-cycle.

## First concrete instance (harvest-2026-07-26 fieldtest, B1) The rot class this issue names has its first observed case: `docs/authoring-guide.md` ~800-821 transcribed multi-regime family ids in a shape the executor does not produce (suffix `-r1` with the default regime unmarked; reality is an infix `-rK` after the window segment with `-r0` present even for an implicit default regime). Transcribed *output* — not just op-script inputs — rots too, so the pin should cover asserted output shapes (family-id/trace-handle lines) where cheap, not only that the examples build. The instance itself was fixed in-cycle.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#344