Skip to content

Foundation: recipe template and scaffolder #68

Closed

Description

@CompleteDotTech

Goal

A worked template that satisfies the recipe contract, and a command that stamps out a new recipe folder from the catalog.

Scope

  • recipes/_template/ with notebook.ipynb, README.md, fixtures/, and the optional helpers.py and tests/, implementing a tiny but complete example against the contract in CONTRIBUTING.md.
  • The notebook section order every recipe follows: what you will build, setup and run mode, the state, the questions, one answer up close, Python's part, evaluation, what was and was not measured, next steps.
  • python tools/new_recipe.py NN creates recipes/NN-slug/ from catalog/recipes.json with title, level, decision types, use case, and sources filled in.
  • The import convention for helpers.py from a notebook and from tests, written down.
  • tools/render_catalog.py ignores _template.

Acceptance criteria

  • The template notebook runs top to bottom offline and its fixtures validate
  • The scaffolder is tested and refuses to overwrite an existing recipe
  • A new contributor can go from scaffold to a running notebook using only the template README
  • Lint and tests pass in CI, or locally with the output pasted in the pull request if CI does not exist yet

Dependencies

References

Activity

  1. added
    type: foundationShared code, tooling, CI, or docs that recipes depend on
    priority: p0Blocks everything else; do first
    status: blockedWaiting on the issues listed under Dependencies
    on Oct 6, 2026
  2. CompleteDotTech commented on Oct 6, 2026

    @CompleteDotTech
    ContributorAuthor

    Teaching-contract handoff from independent PR91 Opus review #91 (comment): ensure the recipe README template explicitly discloses actual run mode and, for recorded inference, returned model/version, capture date and measured N. The updated root note expects notebook and README disclosure. Preserve fixture provenance and the owner recording requirement; do not invent recordings. If mixed synthetic/recorded recipe evidence is supported, disclose modes per fixture rather than one ambiguous header. These are template acceptance details, not a new implementation owner.

  3. CompleteDotTech commented on Oct 7, 2026

    @CompleteDotTech
    ContributorAuthor

    Template review handoff from genuine PR91 Opus6028667795: require N explicitly for every reported recorded Jev metric in notebook headers AND reader README, alongside returned model identity and capture date. Current run_header makes n optional, so its default is not sufficient proof of the #80 recording/claims requirement. Template defaults may demonstrate synthetic pipeline behavior, but recipe delivery must preserve individually required authentic recording coverage and label synthetic/scripted runs honestly. Keep prior fixture-mode and keyless/network-blocked execution requirements. Resolve through existing68 Sonnet ownership and both independent Opus finalhead reviews; this is requirements evidence, not a new writer.

  4. added
    status: in progressClaimed; a branch or pull request exists
    and removed
    status: blockedWaiting on the issues listed under Dependencies
    on Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: p0Blocks everything else; do firstsize: MAbout a daytype: foundationShared code, tooling, CI, or docs that recipes depend on

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions