# Task-guides inputs: the GUM worked-example project

Pinned inputs for the Task guides walkthrough (article 13) and the
Case lifecycle trace (article 14).

## Provenance

`otchet-neopredelennosti/` is a copy of
`corpus/laws/org/jcgm/gum/examples/otchet-neopredelennosti/`
(package `examples.jcgm_gum.otchet_neopredelennosti`) at checkout
commit `99b8818f02` (2026-10-04, source tree clean), minus the
`.law-cache/` directory (regenerable engine cache, 7 files).
Everything else — `law.toml`, `package.law`, `law.lock`,
`queries/` (16 saved queries), `cases/` (3 cases), `deps/`
(vendored dependency snapshots) — is byte-identical to the
committed project, with one exception: `check.py` carries a small
bundle-only patch (the canon-registration check runs only when the
canon layout is detected next to the snapshot, otherwise it prints
a skip note instead of crashing on a missing `law.toml`). The
patch changes no expectation and no engine call.

This is a read-only snapshot: the walkthroughs below copy it to
scratch and never write into the bundle.

## The seven queries of the Task-guides pass

Article 13 attaches one saved-query answer per ask step:

| Step | Saved query |
|---|---|
| ask-input-count | `queries/chislo-vkhodov.json` |
| ask-input-variance | `queries/dispersiya-x1.json`, `queries/dispersiya-x2.json` |
| ask-input-contribution | `queries/vklad-x1.json`, `queries/vklad-x2.json` |
| ask-combined | `queries/summarnaya.json` |
| ask-contribution-count | `queries/chislo-vkladov.json` |

Case: `cases/vkhod-bez-otsenki.lawcase` (`VkhodBezOtsenki`).

## How to run (checkout-only)

Working directory for the `law` commands is the scratch project
copy; the `./law` CLI (built engine) comes from a full checkout,
so the archive alone is not enough.

```bash
cp -r files/task-guides/otchet-neopredelennosti /tmp/gum-pass
PROJECT=/tmp/gum-pass
law ask $PROJECT --case VkhodBezOtsenki \
  --query-json $PROJECT/queries/chislo-vkhodov.json \
  --out /tmp/gum-answers/chislo-vkhodov
# input_count → 2 (COMPUTED)
```

Verified 2026-10-04: the baseline ask on the snapshot copy
returns `input_count → 2 (COMPUTED)` for `VkhodBezOtsenki`, and
the full Case-lifecycle trace (article 14) runs on it end to end
— see `../lifecycle/README.md`.

## Honesty notes

- The route's `--card` path stays NOT RUN (cards named by the
  route are absent from the package catalog); the saved-query
  path above is the repeatable one.
- The k-chosen branch still stops on the engine-side
  `sqrt_bounds` type mismatch; that fix belongs to the package /
  engine owners, not to this snapshot. Verified 2026-10-04:
  `check.py --law <checkout law>` from an unpacked layout now
  runs past registration (skip note printed) through the
  per-question asks and stops exactly at that documented
  `summarnaya` TYPE_ERROR.