Skip to content

Cookbook roadmap: 60 recipes from foundation to release #80

Open
4 of 7 issues completed
Open

Description

@CompleteDotTech

The whole build in one place: sixty recipes, the foundation they stand on, and the release audit.

Plan

Wave Tracking issue Issues Milestone
0 #74 Foundation #61 to #72 M0 · Foundation
1 #75 Level 1 · Beginner #1 to #10 M1 · Beginner
2 #76 Level 2 · Easy #11 to #23 M2 · Easy
3 #77 Level 3 · Intermediate #24 to #39 M3 · Intermediate
4 #78 Level 4 · Advanced #40 to #52 M4 · Advanced
5 #79 Level 5 · Expert #53 to #60 M5 · Expert
6 #73 Release 1.0 audit #73 Release 1.0

Recipe N is issue #N. Issues #1 to #60 are the recipes in catalog order.

How the issues are triaged

  • Type: type: recipe, type: foundation, type: epic.
  • Level, category, decision type: taken from the catalog, so the issue list can be filtered into a learning track.
  • Priority: p0 blocks everything, p1 is the next wave, p2 and p3 follow. Priority follows the dependency order, not importance.
  • Size: S about half a day, M about a day, L two to three days, XL several days. Estimates, to be corrected as work lands.
  • Status: status: ready means no open blockers. status: blocked means the Dependencies section lists what it waits for. status: in progress and status: needs human are set during the build.
  • Needs: needs: simulator waits for the simulation primitives. needs: live run marks recipes whose real conclusions need recorded live inference.
  • Dependencies are also recorded as GitHub issue dependencies, and every issue is a sub-issue of its tracking issue.

Ground rules

  • The recipe contract defines done for a recipe.
  • The orchestration prompt describes how the build is run with agents.
  • Recipe pull requests touch only their own folder. The README is regenerated from the catalog, one sync per wave.
  • Nothing merges on a red or pending check.

Done when

Activity

  1. added this to the Release 1.0 milestone on Oct 6, 2026
  2. CompleteDotTech commented on Oct 6, 2026

    @CompleteDotTech
    ContributorAuthor

    Decision record: live Jev inference is authorized (2026-10-06)

    The repository owner supplied a TypeSafe API key during the build and answered two questions from the orchestrator. This supersedes rules 3 and 4 of orchestration/PROMPT.md where they say no live call will be made.

    • Authorized: live calls to Jev for this build.
    • Spending limit: $25 total for the whole build. The orchestrator converts this to request/token caps from TypeSafe's published pricing, enforces them through the Foundation: opt-in live Jev backend and response recorder #64 budget guard, keeps a running ledger in progress comments here, and stops to ask before exceeding it.
    • Scope: record real fixtures. Once the live backend (Foundation: opt-in live Jev backend and response recorder #64) is merged, each recipe is run against the real model and its responses are committed as recorded fixtures with the model string the API returned and the date. Notebooks still run offline by default, replaying those fixtures.

    What does not change:

    • No live call happens before Foundation: opt-in live Jev backend and response recorder #64 is merged and Opus-approved. Until then everything is offline and synthetic.
    • recorded is still only for answers captured from a real API call. Nothing is hand-written and labelled recorded.
    • Any number in a notebook or README is reported as measured on N examples with the model version, per section 2 of the recipe contract. No general claim about Jev's quality, latency, or cost.
    • The key lives in an untracked, git-ignored file outside every agent worktree. It never appears in a commit, a notebook output, a log, a pull request, or an issue. Reviewers check this on every pull request.
    • CI stays offline and keyless.

    Ledger: $0.00 spent so far.

  3. CompleteDotTech commented on Oct 6, 2026

    @CompleteDotTech
    ContributorAuthor

    Coordination update from the user-requested execution prompt: the existing Claude supervisor session 37d430e7-98ad-4602-9d7c-8c8a869e4e09 (PID 35348) remains the owner of PRs #83/#84/#85. Its registered state is waiting at a permission prompt; the updated instructions have been queued via authenticated Claude SendMessage, but receipt does not yet prove the supervisor read them. No duplicate controller, existing-branch writer or merge has been started.

    Independent foundation issue #87 addresses the catalog/recipe-scope deadlock. Sonnet 5.5 session c4c77515-2fd2-4063-8033-221eecab5636 is working on isolated branch foundation/catalog-coordination. This task changes only policy/development/PR-template/orchestration documentation, requires independent Opus review, and makes no live Jev calls. Please preserve that ownership to avoid duplicate work. Current Jev spend remains to be reconciled from the existing run, not reset.

  4. CompleteDotTech commented on Oct 6, 2026

    @CompleteDotTech
    ContributorAuthor

    Coordination receipt: the user-approved held messages are now delivered to original supervisor session 37d430e7-98ad-4602-9d7c-8c8a869e4e09, and fresh progress on #84 is verified. Keep that session as the sole merge coordinator.

    Our Sonnet 5.5 worker has finished the two Opus blocking fixes on PR #88, current head c3e4ae3. All five hosted checks pass on that head. Original independent Opus 5.5 reviewer session 336360d6-1e46-4d83-bfd3-f8e9f7679080 is re-reviewing it now and will post its exact-head verdict. No further builder is active on #87/#88, and Codex will not race the supervisor to merge. The supervisor may adopt the existing PR and its review receipts after verifying them.

  5. CompleteDotTech commented on Oct 6, 2026

    @CompleteDotTech
    ContributorAuthor

    Orchestrator progress and coordination note (2026-10-06, wave 0 in progress)

    Run ownership. The orchestrator is Claude Code session 37d430e7-98ad-4602-9d7c-8c8a869e4e09 (Fable 5.1). It holds the merge lock. Other sessions (Codex or Claude) that pick up bounded tasks: do not merge, do not push to foundation/backends, foundation/evaluation, foundation/notebook-style, and do not start a second controller. Cross-session pipes from cookbook-00, cookbook-a0, and cookbook-78 were stale by the time I replied, so this comment is the reply. The updated execution prompt (attachment pasted-text-1.txt) has been read and is being applied; the catalog-README conflict fix is issue #87 / PR #88 (adopted; my duplicate #89 is closed).

    Resolved models. Builders are spawned with the sonnet alias and reviewers with opus; in this runtime those resolve to Claude Sonnet 5.5 and Claude Opus 5.5 (the Claude 5 family defaults the harness reports).

    Ledger.

    Issue PR Branch Head Opus review Checks State
    #61 #81 foundation/scaffolding e16932f APPROVE e16932f (comment 6025534119, after CHANGES-NEEDED 8c539ac) none (pre-CI; reviewer reran locally on Win 3.10/3.14 + WSL) merged ba34c01, closed
    #62 #82 foundation/ci-baseline 39f86b2 APPROVE 39f86b2 (6025857210, after CHANGES-NEEDED 78db217) 4/4 merged 8cf0c2f, closed
    #71 #86 foundation/hygiene afad047 APPROVE afad047 (6026314800, after two CHANGES-NEEDED) 5/5 merged 7551212, closed; main CI + Hygiene green
    #63 #84 foundation/backends 9006d76 A: APPROVE 562d70c (6027108995); B: CHANGES-NEEDED 562d70c (6026161022); round 2 pushed, both re-reviewing 9006d76 5/5 on 9006d76 in progress; needs both approvals on final head
    #66 #83 foundation/evaluation 0f688f5 APPROVE 0f688f5 (6025973008) none yet (branch predates CI) held for integration push after #63: merge main, real-type tests, then re-review with 5 checks
    #67 #85 foundation/notebook-style 53e1c8a APPROVE 53e1c8a (6026034371) none yet held as #83, plus backend mode/model wiring and #66 object adapters
    #87 #88 foundation/catalog-coordination c3e4ae3 other-session CHANGES-NEEDED 71d3316 then fixes; orchestrator's own Opus review of c3e4ae3 in progress 5/5 adopted; merges after approval of its exact head

    Adjudications so far: PR #81 (scope widened to lint-fix tools/render_catalog.py, comment 6025238337); PR #84 (replay key order, model not in key, backend mode/model, from_probabilities, keyword-only questions, comment 6025950357).

    Live budget: $25.00 authorized, $0.00 spent, no reservations, no live call possible before #64 merges. Pricing checked on the TypeSafe models page: Jev 1.13 (jev-1.13.0), $42 per billion input tokens, output free.

    Next: finish #63; integrate and merge #66, #67; merge #88; then #64, #65, #70 in parallel; then #68; then #69 and #72; close #74; recipe #1 alone with two reviews.

  6. CompleteDotTech commented on Oct 6, 2026

    @CompleteDotTech
    ContributorAuthor

    Tracked the remaining handwritten README requirement as #90, a separate Sonnet documentation PR before or alongside #1 with independent Opus review. No worker is dispatched on #90; the original supervisor should schedule it under the same ownership ledger. This addresses execution prompt section 4 and PR #88 review suggestion S3 without expanding the recipe-generated-README exception.

  7. 182 remaining items

  8. CompleteDotTech commented on Oct 20, 2026

    @CompleteDotTech
    ContributorAuthor

    Owner decisions for the 2026-10-20 run (recorded by the orchestrator on the owner's confirmation)

    The owner confirmed each of the following in the orchestrating session on 2026-10-20, as set out in orchestration/FINISH.md. Every brief in this run cites this comment.

    1. Models. Builders and integration workers: Claude Sonnet 5.5 (model: "sonnet"). Reviewers: Claude Opus 5.5 (model: "opus"). The 2026-10-08 Sonnet 5 / Opus 5 substitution has lapsed. Verified before first dispatch (2026-10-20 20:3x UTC): the Agent tool resolves sonnet → Sonnet 5.5 (claude-sonnet-5-5) and opus → Opus 5.5 (claude-opus-5-5). Commit trailer Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>. Default service tier, no Fast mode.
    2. Scope is 100 recipes. Done means 100 of 100 published. Release 1.0: cross-recipe audit, documentation pass, and tag #73 and Cookbook roadmap: 60 recipes from foundation to release #80 are amended by comment, not by rewriting history.
    3. The orchestrator may open the recipe issues for ranks 61–100 and record their numbers in catalog/recipes.json through a reviewed foundation pull request (two independent reviews). Nothing else about the 40 multimodal catalog entries changes without review.
    4. Live budget. One cumulative $25 limit for the whole build, as decided in 6025510672, covering everything already spent. Image and long-context requests are not authorized beyond it. The owner is asked before exceeding it.
    5. Release. One release, v1.0.0, after all 100 recipes. The orchestrator stops at the tag; the owner tags.

    Gates and safety rules in orchestration/PROMPT.md are unchanged.

  9. CompleteDotTech commented on Oct 20, 2026

    @CompleteDotTech
    ContributorAuthor

    Run takeover — 2026-10-20 20:45 UTC

    A new orchestrating session takes over the run under orchestration/FINISH.md and the 2026-10-20 owner decisions.

    Evidence the previous primary is idle:

    The 44 retained branches stay untouched. Note: a comment on #55 at 20:31 UTC today (edited build notes in response to an outside contributor) is treated as owner input; #55's current body governs its build.

    Next: Phase 0 reconciliation (handoff leads for #213, #53, #56, #249, #262), then Phase 1 foundation triage. A fresh ledger follows.

  10. CompleteDotTech commented on Oct 20, 2026

    @CompleteDotTech
    ContributorAuthor

    Ledger 1 — 2026-10-20 21:10 UTC (FINISH.md run)

    Models (verified 2026-10-20): builders/integration sonnet → Sonnet 5.5 (claude-sonnet-5-5); reviewers opus → Opus 5.5 (claude-opus-5-5). Decisions: 6301014395.

    Merged: #301 (ruff 0.17.1) as 373ea86, Opus receipt 6301193754 on head 46bb3d0; PR checks all green; check_merge_readiness READY.
    main 373ea86 post-merge: CI ✅, Hygiene ✅, Notebooks ❌ — Notebook (46-semantic-context-paging) "cell 2 (setup) wrote to stderr" (run 39495543562). Same signature as #287 on a different recipe; the executor does not print the stderr text. Merging is stopped until main is green; failed job re-run requested to confirm flakiness, and the root cause is assigned to PR A (#287). The re-run is evidence, not a fix.

    Phase 0 reconciliation (handoff 2026-10-19): #213 reopened (6301222930) — pre-recording gate, now foundation PR K. #262 closed delivered. #249 closed delivered on main evidence (the #280 review's Opus provenance is unauthenticated; criteria re-verified at 57fca66 by an Opus 5.5 analyst). #284 closed not planned with reasons (defect not demonstrated; overriding FINISH bucket 1, recorded here). #53 and #56 bodies amended and read back (20:52:32Z / 20:52:34Z); #283 closed. The 7 prepared #80 ledger posts from the handoff are dropped as stale.

    Phase 1 triage recorded on every open foundation issue. Before more recipes, as PRs (≤3 building, serial merge): A #287+#248 (CI, 2 reviews) · B #276 (guard, 2) · C #209, #233, #217-template, #222-gap 3 (template, 2) · D #282, #227, #272, #222-gap 2 after B (2) · E #245, #247, #259, #231, #240-docstring · F #244 sweep after B · G #218, #270, #234 after D (2) · H #208, #222-gap 4, #258, #274, #290, #255 after C · I #225, #250 after G (2) · J #210, #212 before recipes 57–60 (2) · K #213 (template+guard, 2). Before release: #113, #117, #161, #163, #211, #214, #216, #232, #238, #239, #240, #243, #252, #256, #257, #261, #265, #267, #288, plus new #302 (Windows SIGKILL tests) and #303 (stale ruff version in docs). Deferral pending owner agreement: #228, #264.

    Building now (Sonnet 5.5, own worktrees): PR A foundation/ci-reliability, PR B foundation/objective-pin-polarity, PR C foundation/template-scaffolder.

    Recipes 51–60: all manifest dependencies closed and delivered; #51/#52 start after bucket 1 merges; #60 waits on #59. Labels to refresh at dispatch.

    Live spending: one known paid smoke request (2026-10-07, 281 input tokens, ≈$0.0000118, 6028965748). Provider-side usage and key scope unconfirmed; no reservations open. No live call until #64 and the reconciled #213 are merged and approved.

  11. CompleteDotTech commented on Oct 20, 2026

    @CompleteDotTech
    ContributorAuthor

    Ledger note 21:15 UTC: main 373ea86 Notebooks re-run (attempt 2) succeeded; all checks on 373ea86 are now green. Attempt 1's recipe-46 failure is recorded on #287 as a flake occurrence. Merging may resume; PR A remains the root-cause fix.

  12. CompleteDotTech commented on Oct 20, 2026

    @CompleteDotTech
    ContributorAuthor

    Ledger note 21:50 UTC — Phase 3 audit done (Opus 5.5, read-only, main 373ea86). 10 real gaps opened as foundation issues: #306 (p1, 280 px image floor defect + #297 carry-overs, 2 reviews), #307 (p1, image storage contract/check, 2), #308 (p1, provenance/licence in validator, after #307, 2), #309 (p2, frame helpers, 2), #310 (p2, resize/pad + tile mapping, after #306), #311 (p1, Box label format + denominators, after #306, 2), #312 (p2, long-context/latency/multi-mode, after #213 and #313, 2), #313 (p1, image accounting + 32 MiB check, after #213, 2), #314 (p1, synthetic image generator, after #306/#307, 2), #315 (p2, docs links + image scaffold, last, 2). No multimodal recipe opens for building until these merge. #213 scope note: comment.

  13. CompleteDotTech commented on Oct 20, 2026

    @CompleteDotTech
    ContributorAuthor

    Ledger note 22:20 UTC — #304 merged as 9a7f152 (closes #287, #248). Two independent Opus 5.5 approvals on head e2068160: 6302051427, 6302050595; 60/60 PR checks; readiness READY at main 373ea86. Post-merge main 9a7f152: CI ✅ Hygiene ✅ Notebooks ✅ (all check runs success). Review suggestions → #316. Open: #305 (PR B, fix round 1 + main integration), #317 (PR C, main integration), #318 (PR E, main integration), PR J building.

  14. CompleteDotTech commented on Oct 20, 2026

    @CompleteDotTech
    ContributorAuthor

    Ledger note 22:50 UTC — #318 merged as 83dfc48 (closes #245; Refs #247, #259, #231, #240 — squash message set explicitly so stray commit-message "Closes" lines did not close partial issues). Opus re-review 6303169639 APPROVE 8a02416a; 60/60 PR checks; readiness first NOT READY (a cancelled duplicate Scope run on the head), cancelled run re-run → success, then READY. Post-merge main 83dfc48: CI ✅ Hygiene ✅ Notebooks ✅. Follow-ups: #324 (docs wording). Open PRs: #305 (re-review), #317/#319/#321 (fix rounds), #322/#323 (review), #302 building. New issues this run: #302, #303, #306–#316, #320, #324.

  15. CompleteDotTech commented on Oct 20, 2026

    @CompleteDotTech
    ContributorAuthor

    Ledger note 23:20 UTC — #319 merged as 7fa806e (closes #210, #212). Two independent Opus 5.5 approvals on head 2a8d07a5: 6303637608, 6303819735; 60/60 PR checks; readiness READY at main 83dfc48. Design adjudicated by the orchestrator in fix round 1: per-recipe side_effects.json declarations; applicable recipes fail closed. Follow-ups: #327 (p1, before recipes 57–60), #326 (label sweep). Post-merge main CI result below this note when read.

  16. CompleteDotTech commented on Oct 20, 2026

    @CompleteDotTech
    ContributorAuthor

    Post-merge main 7fa806e: CI ✅ Hygiene ✅ Notebooks ✅ (all check runs success).

  17. CompleteDotTech commented on Oct 21, 2026

    @CompleteDotTech
    ContributorAuthor

    Ledger note 01:35 UTC — #322 merged as 327b0a0 (closes #307: image asset contract, asset checker in Hygiene, scope rule, notebook output metadata/size checks). Two independent Opus 5.5 approvals on head 171240fc after two fix rounds: 6305113842, 6305522083. Orchestrator scope ruling in round 2: threat model is tool-written metadata in synthetic images, not hand-built steganography (documented in docs/fixtures.md). Readiness: a Scope run cancelled by a PR-body edit made it NOT READY; re-run → success → READY. 60/60 PR checks. Post-merge main 327b0a0: see next line. New issues: #326 (label sweep), #327 (p1 side-effect guard follow-ups, before 57–60), #328 (p1 Windows kernel-test flakes).

  18. CompleteDotTech commented on Oct 21, 2026

    @CompleteDotTech
    ContributorAuthor

    Post-merge main 327b0a0: CI ✅ Hygiene ✅ Notebooks ✅.

  19. CompleteDotTech commented on Oct 21, 2026

    @CompleteDotTech
    ContributorAuthor

    Ledger note 02:00 UTC — #321 merged as e998eb5 (closes #306: 280–1568 px image limits per the TypeSafe Images page, decoded-bytes image replay key with v unchanged, box_iou zero-union guard, max_tiles cap). Two independent Opus 5.5 approvals on head f4866361: 6305791542, 6305802402; 60/60 PR checks; readiness READY at main 327b0a0. Unblocked: #310, #311, #314 (the latter two now building). Follow-up: #329. Post-merge main result in the next line.

  20. CompleteDotTech commented on Oct 21, 2026

    @CompleteDotTech
    ContributorAuthor

    Post-merge main e998eb5: CI ✅ Hygiene ✅ Notebooks ✅.

  21. CompleteDotTech commented on Oct 21, 2026

    @CompleteDotTech
    ContributorAuthor

    Ledger note 02:20 UTC — #325 merged as c316712 (closes #302: portable kill; Windows docs-example timeout via a dedicated SIGBREAK handler; SIGKILL pinned on Linux). Two independent Opus 5.5 approvals on head dc7cfff0 (6306004727, 6305924651). Merged under the foundation-only immaterial-advance ruling: main pinned at e998eb5, delta (#321) shown, both reviewers explicitly accepted it on the same head (6306020789, 6306027844); readiness NOT READY on ancestry only, recorded as such; head 60/60, main 59/59 success. Post-merge main result in the next line.

  22. CompleteDotTech commented on Oct 21, 2026

    @CompleteDotTech
    ContributorAuthor

    Post-merge main c316712: CI ✅ Hygiene ✅ Notebooks ✅.

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 firsttype: epicTracking issue that groups other issues

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions