Implementation status

Progress for this independent site. Source implementation, hosted behavior, independent review and acceptance are separate states.

Source and publication identity

Source: product/TASKS.md

Source SHA-256 (LF-normalized text): bbdd30d8a434dc6b8c1dcc06530de2c839cafb4f863e8d6b433aca0652e604f7

Transformation: public-business-v2

Hosted source revision: 43c95a027624b804bcb616c8ee79405f47c66f13

Repository source (authorized repository access required)

Implementation progress

Implemented: 0 / 10 groups (0.0%)

Deployed: 0 / 10 groups (0.0%)

Verified: 0 / 10 groups (0.0%)

Open groups
10
Blocked groups
2
Unknown groups
0

PROGRESS-GROUPS-1 · denominator D=10 common requirement groups. Every applicable child must meet the state before its group counts. Equal-group percentages measure coarse requirement coverage, not effort, time, quality or final acceptance. New scope can reopen a group.

Diagnostic detail: 16 source-implemented child rows; 126 open; 7 blocked; 149 total mapped rows. These site-specific counts do not set the headline percentage.

Last checklist update: 2026-10-07T02:14:03.036Z

Deployed source: 43c95a027624b804bcb616c8ee79405f47c66f13. Complete-group hosted evidence time: unknown. Static status updates appear after deployment and page refresh. Reload status

Is the Best Recipe — implementation checklist

Updated: 2026-10-07T02:14:03.036Z

BRD-SHA256: d4ddea4f3901366328aca81eb7aa5805f379b0ffc4350a91f957aba31d7d6de6

Candidate basis: 6ffe70919afff01a2ce5803686f8048c93676485 (prior published source, not this correction commit). Public-document CI passed on that source; the new identity/projection correction needs its own hosted proof.

Current result

The independent site shell, own branding, local demo account, local cookbook/collections, recipe renderer and requested-email interface have source implementations. No accepted hundred-recipe export has arrived in this checkout. Articles/resources, exact-dish media and complete culinary variants remain dependent inputs. Email transport and inbox-return proof are not established by this frontend. The source-only documentation increment adds BRD and status routes, deterministic safe rendering and validation; it has not been deployed or independently accepted.

Hosted evidence: Delivery reported successful hosted build of 0a9792435da8fde36ede8dcf1a85e03e72a5ef66. Author inspected its desktop and 390px phone rendering and demo login/logout. Later source and all full-content journeys require separate deployed verification. This is author observation, not independent QA approval.

Next action: Delivery publishes this exact source plus the two server-only document inputs; QA verifies /BRD.HTML, /brd.html and /status, parity/privacy/mobile behavior and hosted validation. Batch/Content supply the actual accepted corpus in parallel.

Requirement rows

PUB-DOC-01

Requirement: PUB-DOC-01 — Exact BRD route

BRD section: Public documentation and status acceptance

Required finish: Hosted /BRD.HTML renders the current BRD business content as readable HTML rather than a raw download, missing route or homepage fallback. Preserve requirement meaning, headings and traceable identifiers, including latest accepted deltas. Record actual URL, deployed source identity, date, viewport and screenshot. Verify /brd.html if implemented.

PUB-DOC-02

Requirement: PUB-DOC-02 — Safe public scope

BRD section: Public documentation and status acceptance

Required finish: Publish only the current business requirements and their implementation status. Render an explicit public business-content projection from the current BRD: retain all accepted business requirements and honest implementation limits while excluding private operational and personal information. Do not expose raw private appendices through HTML comments, downloadable sources, source maps or bundled data. Record the projection rule and any excluded internal sections for owner review without reproducing sensitive values. Privacy exclusions cannot hide an unmet business requirement or fabricate a pass.

PUB-DOC-03

Requirement: PUB-DOC-03 — Full checklist

BRD section: Public documentation and status acceptance

Required finish: product/TASKS.md maps every currently accepted BRD requirement/criterion and applicable coverage-map obligation to an implementation row, using stable existing requirement IDs or section/anchor references. Group rows only when individual obligations and their different states remain traceable. Preserve superseded history as history, not duplicate active obligations. Include ACT-UX-01–12 and PUB-DOC-01–10. Missing work stays visible; a finished shell is not completion of its content or journeys.

PUB-DOC-04

Requirement: PUB-DOC-04 — Honest status fields

BRD section: Public documentation and status acceptance

Required finish: Each row records actual assigned owner, source progress, hosted proof, independent review proof, gap, next action, last-updated timestamp and candidate identity. Separate planned/in progress/source complete/deployed/reviewed/accepted; use not verified or awaiting owner when appropriate, never invent an assignment or evidence. Link public-safe evidence; retain sensitive proof privately with a truthful public summary. Display meaningful status, not a cosmetic percentage inferred from checkbox count.

PUB-DOC-05

Requirement: PUB-DOC-05 — Deterministic source

BRD section: Public documentation and status acceptance

Required finish: Generate/render BRD business content from product/BRD.md and status from product/TASKS.md through a documented deterministic transformation. Avoid a separately maintained HTML requirements copy. Identify the source revision/content digest and transformation so reviewer can compare actual source to published output and detect staleness. A generated projection is not permission to omit business scope.

PUB-DOC-06

Requirement: PUB-DOC-06 — Update discipline

BRD section: Public documentation and status acceptance

Required finish: Every implementation commit by Codex or Mac updates relevant task progress/evidence, next action and timestamp. Meaningful changes require matching task updates; nonfunctional changes record an explicit justified no-impact disposition where applicable. Assigned instruction owner places this rule in the existing per-repo Codex/Mac entries. Preserve other writers and separate branch state; main evidence is not proof of Mac preview behavior or vice versa.

PUB-DOC-07

Requirement: PUB-DOC-07 — Scoped validation

BRD section: Public documentation and status acceptance

Required finish: Hosted prebuild/CI validation must catch missing checklist coverage, required fields, stale generated output and meaningful implementation changes without task updates. Demonstrate both a rejected deliberately stale/missing update case and a corrected passing case in the approved hosted workflow. Check actual changed paths and task references; a changed timestamp alone does not demonstrate meaningful progress.

PUB-DOC-08

Requirement: PUB-DOC-08 — Candidate identity

BRD section: Public documentation and status acceptance

Required finish: Avoid a document embedding the hash of the commit that contains itself. Use content digests or a prior verified source revision with explicit meaning; inject the actual deployment/source revision through CI/deployment metadata for the served candidate. Keep document update time, source identity and hosted verification time distinct. Unknown deployed identity stays unknown until Delivery supplies it.

PUB-DOC-09

Requirement: PUB-DOC-09 — Readable discovery

BRD section: Public documentation and status acceptance

Required finish: Homepage/footer expose clearly labeled BRD and Status links. Both pages work on mobile and desktop with readable headings, wrapping tables/long links, keyboard navigation and meaningful link text. Status links to the repository product/TASKS.md at an identified source revision; a private repository link is labeled as requiring authorized access while the public status remains readable. Verify exact-case route, refresh/direct navigation, all links and privacy-safe content on the hosted candidate.

PUB-DOC-10

Requirement: PUB-DOC-10 — Completion and handoff

BRD section: Public documentation and status acceptance

Required finish: Source or CI success alone cannot close this delta. Delivery supplies exact hosted /BRD.HTML and /status URLs, source/deployment identity and route/content proof; assigned QA independently verifies source parity, public-safe scope, checklist coverage, mobile/desktop readability and update behavior. Record finite defects and recheck repairs. Only after those exact deployed paths/proofs return does Solutions prepare the subsequent Mac prompt; no deployment or acceptance is presumed now.

mandatory-checklist-coverage-to-preserve:100-original-reviewed-recipes

Requirement: 100 original reviewed recipes

BRD section: Mandatory checklist coverage to preserve

Required finish: Existing Recipe writer/common-intake owner, Batch, Content and reviewers; distinguish 100 retained inputs from 100 distinct complete reviewed output recipes, export/lineage and actual per-site static consumption. No handmade substitute or count inflation.

mandatory-checklist-coverage-to-preserve:articles-and-learning

Requirement: Articles and learning

BRD section: Mandatory checklist coverage to preserve

Required finish: Content/Recipe and builder: complete articles, ingredient/technique/resource libraries, before-cook/help content, useful relationships and return to the originating step.

mandatory-checklist-coverage-to-preserve:discovery-and-classification

Requirement: Discovery and classification

BRD section: Mandatory checklist coverage to preserve

Required finish: Builder/UIUX with Batch/Content: home, search, category/collection/filter flows, all nine classification groups where supported, occasion placements, related browsing, canonical recipe identities/routes, metadata, empty/error/back states.

mandatory-checklist-coverage-to-preserve:identity-and-imagery

Requirement: Identity and imagery

BRD section: Mandatory checklist coverage to preserve

Required finish: Visual, Content and builder: Is the Best Recipe own branding, distinct exact-dish home/major-category features, rights/alt/caption and responsive fallback; no generic illustration passed off as verified dish imagery.

mandatory-checklist-coverage-to-preserve:real-activity-and-adaptation

Requirement: Real activity and adaptation

BRD section: Mandatory checklist coverage to preserve

Required finish: UIUX, builder and domain/technical reviewers: find, assess time/effort/ingredients/equipment, shop, mobile cook/placekeeping/checkoffs/timers/screen behavior, clean complete print, supported scaling/units/substitutions/preferences/notes/own versions and recovery. Unsupported mechanisms remain explicit gaps/proposals.

mandatory-checklist-coverage-to-preserve:keeping-and-sharing

Requirement: Keeping and sharing

BRD section: Mandatory checklist coverage to preserve

Required finish: Builder/CRM and QA: demo login/logout, local My Recipe Book/save/organize/made-state, share/return, persistence/reset limitations and truthful privacy; no database or implied cloud account.

mandatory-checklist-coverage-to-preserve:bounded-real-email

Requirement: Bounded real email

BRD section: Mandatory checklist coverage to preserve

Required finish: CRM/Software, existing mail owner and Delivery: fixed authorized recipient, existing finite cap/deduplication contract, actual sent/received proof and exact campaign landing return; UI simulation is not transport completion.

mandatory-checklist-coverage-to-preserve:ad-free-quality-and-evidence

Requirement: Ad-free quality and evidence

BRD section: Mandatory checklist coverage to preserve

Required finish: All assigned implementers and independent reviewers: NO ADS EVER; accessibility/keyboard, phone/desktop, print, error/recovery, dated real user/research evidence, labeled opinions, supported alternatives and hosted screenshots/reproduction.

mandatory-checklist-coverage-to-preserve:public-docs-status-and-delivery

Requirement: Public docs/status and delivery

BRD section: Mandatory checklist coverage to preserve

Required finish: Assigned builder/instruction owner, Delivery and QA: PUB-DOC-01–10, full per-requirement task mapping, deterministic safe projection, update validation, exact deployment/source evidence, independent Mac branch continuity and finite repair/recheck.

ACT-UX-01

Requirement: ACT-UX-01 — Ad-free

BRD section: Traceable acceptance delta

Required finish: No advertising anywhere in the recipe experience, including browsing, detail, cooking, printing and account/campaign return. Inspect rendered states and relevant source/integrations for ad slots, ad content and advertising scripts. Approved user-requested signup/campaign communication is governed by the existing finite mail contract; it does not authorize third-party advertising.

ACT-UX-02

Requirement: ACT-UX-02 — Find

BRD section: Traceable acceptance delta

Required finish: A person can find relevant recipes through the specified search, categories and collections, understand results, recover from no results and return without unnecessarily repeating choices. Demonstrate a realistic task across the real reviewed corpus, on phone and desktop.

ACT-UX-03

Requirement: ACT-UX-03 — Decide

BRD section: Traceable acceptance delta

Required finish: Before committing to cooking, the person can assess time, effort, ingredients and equipment using actual recipe information. Distinguish total/active/wait time where the source supports it; do not invent effort scores or equipment/time facts. Demonstrate a choice and the ability to inspect needed information without losing the candidate recipe. Missing source fields become precise content/schema gaps.

ACT-UX-04

Requirement: ACT-UX-04 — Shop

BRD section: Traceable acceptance delta

Required finish: Support the transition from choosing a recipe to obtaining its ingredients: understandable quantities, units and needed items, with a usable shopping workflow and return to the recipe. Demonstrate the implemented route and limits. Combined lists, pantry inference, ordering, retailer integrations or synchronizing lists are proposals unless separately supported and assigned; do not silently promise them.

ACT-UX-05

Requirement: ACT-UX-05 — Cook on mobile

BRD section: Traceable acceptance delta

Required finish: Demonstrate readable ingredients and steps, placekeeping, checkoffs, timers and the specified screen behavior in a realistic cooking flow with messy hands in mind. Record viewport, interaction burden and interruption/resume behavior. UI/UX must specify and verify the chosen mechanisms; no hands-free, voice, wake-lock, background-timer or cross-device guarantee follows from this requirement alone. If a browser capability is unsupported or denied, expose its actual limit and usable recovery rather than claiming success. Step/timer completion never certifies food safety.

ACT-UX-06

Requirement: ACT-UX-06 — Print

BRD section: Traceable acceptance delta

Required finish: Print a complete clean recipe with necessary ingredients, quantities, equipment and full instructions, readable pagination and no ads, navigation clutter or clipped steps. Inspect the actual print output/preview for the candidate, including long recipes and current supported servings/units; do not count a print button alone.

ACT-UX-07

Requirement: ACT-UX-07 — Modify

BRD section: Traceable acceptance delta

Required finish: Demonstrate supported scaling, unit conversion, substitutions, notes and own versions with clear distinction between the original and personal changes. Preserve original source and explain persistence/reset limits. Use supported culinary data: do not automatically scale cooking time/temperature or invent safe substitutions/conversions. Unsupported cases need explicit boundaries and an owner gap; generalized AI rewriting, cloud accounts and publishing personal versions are not implied.

ACT-UX-08

Requirement: ACT-UX-08 — Keep, organize, share

BRD section: Traceable acceptance delta

Required finish: Demonstrate keeping and finding a recipe in My Recipe Book, organization, notes/version retrieval, supported sharing and return. Exercise refresh, logout/reset and an unavailable share mechanism as applicable; identify actual device-local persistence and a truthful fallback. Do not imply private cloud storage, synchronization or that private local notes travel with a shared public URL.

ACT-UX-09

Requirement: ACT-UX-09 — Evidence and alternatives

BRD section: Traceable acceptance delta

Required finish: Every user-behavior claim cites actual dated feedback or research and a usable source link, including scope/limitations. Label design opinions, hypotheses and untested recommendations. Explain the evidence and expected activity improvement behind recommendations; when implemented, demonstrate alternatives in hosted previews and retain the comparison evidence. No fabricated interviews, invented study results or universal conclusions from one opinion.

ACT-UX-10

Requirement: ACT-UX-10 — Live defect proof

BRD section: Traceable acceptance delta

Required finish: For a claimed live defect, retain exact URL, observation date/time, viewport and screenshot, plus reproduction, expected/observed behavior and deployment/source identity when available. Tool failures are labeled separately from product defects. Recheck the repaired hosted candidate against the same criterion. Do not present old screenshots as current live proof.

ACT-UX-11

Requirement: ACT-UX-11 — Independent Mac review

BRD section: Traceable acceptance delta

Required finish: Mac Claude records gaps/recommendations and evidence under this repository's product/ on mac-claude-qa, preserving its assigned branch and authorship. Windows owners consume the scoped evidence through PO and actual writer handoff; neither side silently replaces the other's implementation or declares the other's acceptance.

ACT-UX-12

Requirement: ACT-UX-12 — Parallel progress

BRD section: Traceable acceptance delta

Required finish: Research and current live inspection may proceed alongside the five builds. No new research gate, forced strongest-site-first sequence or cross-site completion dependency is introduced. Record missing evidence and continue independent authorized implementation; final acceptance still requires the applicable evidence.

expanded-complete-product-contract-october-6-current:100-recipe-library

Requirement: 100-recipe library

BRD section: Expanded complete product contract — October 6, current

Required finish: At least 100 complete distinct engine-produced recipes in this site's static artifact, with stable IDs and source/output lineage. The same reviewed dataset can be copied into each repository. Category/search/filter and collection results link to actual recipes; empty/reset/back work. Count real recipes, not duplicate cards/routes or placeholders.

expanded-complete-product-contract-october-6-current:editorial-learning

Requirement: Editorial learning

BRD section: Expanded complete product contract — October 6, current

Required finish: Articles and ingredient/technique/resource pages contain useful coherent content and links to the applicable recipes and back. Technique/help returns to the exact originating cooking step without losing work. Retain provenance and rights; no empty navigation stubs.

expanded-complete-product-contract-october-6-current:guest-cooking

Requirement: Guest cooking

BRD section: Expanded complete product contract — October 6, current

Required finish: Browse, read ingredients/equipment, follow steps, use supported servings/units/help/timers, then print/share/return. Scaling does not invent culinary rules or proportionally scale time/temperature. Checked steps/timer end do not prove safety.

expanded-complete-product-contract-october-6-current:demo-login-logout

Requirement: Demo login/logout

BRD section: Expanded complete product contract — October 6, current

Required finish: Same the authorized demo inbox and newly generated mock-only password across all five. Correct/incorrect login, logout, expired/missing local demo state and return to intended recipe/book/campaign work. The public demo is not secure authentication and never validates company credentials.

expanded-complete-product-contract-october-6-current:my-recipe-book

Requirement: My Recipe Book

BRD section: Expanded complete product contract — October 6, current

Required finish: Save/unsave, list/open, create/rename/remove collections, move/organize saved recipes and reopen supported notes/progress in browser-local storage. Explain device-only persistence concisely. Handle first-use empty book, duplicate save, storage denial/corrupt state and removal without deleting source recipes. Login return retains a pending save once; logout handling is explicit and does not falsely imply server deletion.

expanded-complete-product-contract-october-6-current:sharing-printing

Requirement: Sharing/printing

BRD section: Expanded complete product contract — October 6, current

Required finish: Real browser clipboard/share/print where supported, with cancellation/denial paths and useful fallbacks. Public URLs never include local notes, credentials or email data. Printed quantities/units agree with the selected supported screen state; return preserves context.

expanded-complete-product-contract-october-6-current:campaign-signup-email-return

Requirement: Campaign/signup/email/return

BRD section: Expanded complete product contract — October 6, current

Required finish: Reach a real static campaign landing, explicitly request its signup email, obtain an honest receipt state, open the delivered designed email and follow its button back to that exact site's campaign landing. Useful landing content survives fresh browser or local logout. Signup does not silently create a production account or enroll marketing.

full-recipe-coverage-map-builders-batch-and-reviewers:original-100-coll-01-j22

Requirement: Original 100 / COLL-01, J22

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Select 100 retained ingredient sets; existing writer produces full English original recipe and companion records using established pattern; Content reviews/refines through correct owner loop. — Batch binds retained source identities, method/run/output/review/export. No 35-item slice, duplicate member, handmade recipe or invented qualification fills the count.

full-recipe-coverage-map-builders-batch-and-reviewers:classification-coll-03-05-09-home-01

Requirement: Classification / COLL-03–05/09, HOME-01

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: One primary canonical recipe URL, many ordered collections/category memberships, evidence-backed tags/filters, “Also in” and related browsing. Category membership never duplicates a recipe. Category page exists for its first included recipe; ad-hoc filter state is not a second canonical recipe. — Batch supplies actual memberships/primary category/evidence, builders render one registry across home/hubs/detail. Test multi-category recipe, filters, zero result, back and canonical consistency.

full-recipe-coverage-map-builders-batch-and-reviewers:full-vocabulary-r2-working-set

Requirement: Full vocabulary / r2 working set

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Use the nine groups and exact vocabulary below. Provide meaningful coverage for relevant meal/dish/ingredient/method/effort/cuisine/occasion/style; diet only with evidence. Named collections and seasonal placements are distinct from ad-hoc filters. — Batch/Content disposition all relevant terms against the 100 retained inputs; do not create unsupported tags, certifications or empty “complete” categories. Latest explicit holiday, potluck, comfort-food and breakfast coverage must be represented in the input/selection map.

full-recipe-coverage-map-builders-batch-and-reviewers:home-and-features-home-01

Requirement: Home and features / HOME-01

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Distinct actual featured recipe for home and every major section/category, suitable context and image; categories share registry. Occasion windows/order from existing accepted records, ordinary collections remain reachable. — Per-site placement→recipe ID/revision→category/occasion→asset/alt/caption mapping. Visually inspect different dishes and accurate images; no generic dish identity or universal repeated hero.

full-recipe-coverage-map-builders-batch-and-reviewers:identity-discovery-coll-02-03-06-08

Requirement: Identity/discovery / COLL-02/03/06/08

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Canonical primary-category/item route, correct breadcrumbs, title/description and factual Recipe/CollectionPage/ItemList/BreadcrumbList data; useful crawlable HTML. Wrong/moved addresses give honest not-found, no fake home success. — Inspect metadata/HTML/routes and stable back/return. Preserve study noindex while retaining correct metadata; no production SEO/indexing claim. Current owner types now include primaryCategoryId, tagIds and tags; bind real reviewed values, never guess primary from array order.

full-recipe-coverage-map-builders-batch-and-reviewers:complete-recipe-public-parts-1-5-10-17

Requirement: Complete recipe / public parts 1–5,10–17

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Identity/tradition wording without unsupported authenticity; description; yield/prep/cook/total; exact dish hero; 2–5 practice techniques; fixed versus judgment; supported quantities/units; grouped ingredient check-off; equipment by yield; before-you-cook article; full ordered step cards with primary required actions, cues, why/recovery, seasoning and safe parallel cues. — Writer/Content provide all fields and ingredient/step references. Do not hide missing fields behind decorative cards. Inspect full recipe, unsupported quantity, units and image fallback. Companion material uses reviewed source, not missing-data invention.

full-recipe-coverage-map-builders-batch-and-reviewers:familiar-cooking-parts-7-9-18-23

Requirement: Familiar cooking / parts 7–9,18–23

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Jump controls, keep-awake opt-in where supported, check-only timers, substitutions/job/stand-ins/step changes/not-a-swap, preferences with supported changes, variations, “Make it the best”, “My best”, “Why it's the best”, “Best for [place or situation]”, local made-state and correction/parent-version meaning. — Demonstrate supported local state and return; fixed safety endpoints cannot be edited. No invented community aggregates, public member publication or unprovided AI effect. Current CRM book shape only IDs/collection labels: Batch/Software/CRM must bind additive local My-best/preferences state rather than silently omit feature or overload credentials/book shape.

full-recipe-coverage-map-builders-batch-and-reviewers:book-and-account-item-01-current-crm

Requirement: Book and account / ITEM-01, current CRM

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Guest value first; disposable demo login/logout, same-origin intended-action return, device-local book save/organize/reopen/remove. Local personal versions remain truthful, never secure company accounts or cloud sync. — Correct/incorrect login, refresh, denied/corrupt storage, duplicate save, collection edits, logout/clear behavior; data does not cross origins.

full-recipe-coverage-map-builders-batch-and-reviewers:libraries-articles-lib-01

Requirement: Libraries/articles / LIB-01

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Ingredient identity/forms/prep/choose/store/jobs/allergen evidence with references; technique what/why/cues/recovery/fixed/judgment/tips; Shawn's applicable teaching retained; full related articles/resources and bidirectional recipe links. Ingredient reference pages remain distinct from main-ingredient collections; reserve ingredient/technique routes. — Reviewed companion records and actual bindings; no empty stubs. Inspect recipe→help/reference→same cooking step return. Safety claims and public/private evidence boundaries preserved.

full-recipe-coverage-map-builders-batch-and-reviewers:full-print-card-01-page-01

Requirement: Full print / CARD-01, PAGE-01

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Chosen supported servings/units, full ingredients/equipment/instructions, primary safety, substitutions, practice/fixed guidance, check-at table and canonical return. Complete text preset remains; illustrated card needs its required matched ingredient/hero/every-step assets, tips/fixes and QR, never a partial card called complete. — Hosted print preview/PDF, text and illustrated applicable states, page breaks, no clipped content, image correspondence, cancel/return. No local application execution.

full-recipe-coverage-map-builders-batch-and-reviewers:signup-campaign-email-signup-01-crm

Requirement: Signup/campaign/email / SIGNUP-01, CRM

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Promised useful item on screen immediately; existing bounded real mail to Michael; exact campaign return without login wall; duplicate request still offers useful item without duplicate send. Brand is Is the Best Recipe throughout message. — Record actual request/receipt/inbox timestamps against BRD's 60-second welcome criterion; do not claim timing without measurement. Preserve fixed-recipient finite attempt ceiling and uncertainty reconciliation. Designed email/landing source branding needs CRM/Frontend update, not only documentation.

full-recipe-coverage-map-builders-batch-and-reviewers:other-public-parts-24-26-30

Requirement: Other public parts / 24,26–30

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: Ordinary related recipes and publication facts remain. Ads stay off. Assistant invitation/WebMCP requirements retained in coverage with exact available capability/refusal, no invented live assistant integration. Part27 transformers/cross-family integrations excluded by latest instruction. — No fake AI/counters/awards/earned badges. Record any unsupported non-transformer feature as a concrete owner gap, not silently dropped scope. Production staff CRUD, public community publishing and real identity remain outside this static demo's effect grant.

full-recipe-coverage-map-builders-batch-and-reviewers:english-brand-qa-supersession

Requirement: English/brand/QA supersession

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: English-only; five distinct own visual styles, same exact public name/logo; no competitor/mockup naming on public site/email identity. Independent review traces this map, reviews pixels and interactions on hosted phone/desktop, repairs and rechecks. — Candidate/ref/source versions, actual visual evidence and case disposition. Concise truthful demo-control notices remain.

classification-vocabulary-carried-from-the-brd-linked-r2-working-set:a-meal

Requirement: A. Meal

BRD section: Classification vocabulary carried from the BRD-linked r2 working set

Required finish: When do you eat it? — breakfast · brunch · lunch · dinner · appetizers · snacks · sides · desserts · drinks — recipeCategory

classification-vocabulary-carried-from-the-brd-linked-r2-working-set:b-dish-type

Requirement: B. Dish type

BRD section: Classification vocabulary carried from the BRD-linked r2 working set

Required finish: What kind of dish is it? — soups · stews-and-chili · salads · sandwiches · tacos · pasta · noodles · rice-dishes · grain-bowls · casseroles · curries · stir-fries · pizza · breads · cakes · cookies · pies · sauces · dips — recipeCategory

classification-vocabulary-carried-from-the-brd-linked-r2-working-set:c-main-ingredient

Requirement: C. Main ingredient

BRD section: Classification vocabulary carried from the BRD-linked r2 working set

Required finish: What is it made from? — chicken · beef · pork · lamb · turkey · fish · shrimp · eggs · beans-and-lentils · tofu · vegetables · potatoes · mushrooms · cheese · fruit · chocolate — keywords

classification-vocabulary-carried-from-the-brd-linked-r2-working-set:d-method-and-equipment

Requirement: D. Method and equipment

BRD section: Classification vocabulary carried from the BRD-linked r2 working set

Required finish: How is it cooked? — one-pot · sheet-pan · skillet · slow-cooker · instant-pot · air-fryer · grill · smoker · dutch-oven · cast-iron · no-cook · baked · campfire — cookingMethod

classification-vocabulary-carried-from-the-brd-linked-r2-working-set:e-quick-and-easy

Requirement: E. Quick and easy

BRD section: Classification vocabulary carried from the BRD-linked r2 working set

Required finish: How much time and effort? — 15-minute · 30-minute · 5-ingredient · 7-ingredient · make-ahead · freezer-friendly · batch-cooking · weeknight · beginner — totalTime (computed)

classification-vocabulary-carried-from-the-brd-linked-r2-working-set:f-diet

Requirement: F. Diet

BRD section: Classification vocabulary carried from the BRD-linked r2 working set

Required finish: Who can eat it? — vegetarian · vegan · gluten-free · dairy-free · egg-free · nut-free · low-carb · high-protein · kosher · halal — suitableForDiet (evidence required)

classification-vocabulary-carried-from-the-brd-linked-r2-working-set:g-cuisine

Requirement: G. Cuisine

BRD section: Classification vocabulary carried from the BRD-linked r2 working set

Required finish: Where is it from? It is grouped by region. — Americas: american · southern · cajun-and-creole · tex-mex · mexican · caribbean · brazilian; Europe: italian · french · spanish · greek · german · polish · british-and-irish; Middle East and Africa: middle-eastern · north-african · west-african; Asia: indian · chinese · japanese · korean · thai · vietnamese · filipino — recipeCuisine

classification-vocabulary-carried-from-the-brd-linked-r2-working-set:h-occasion-and-season

Requirement: H. Occasion and season

BRD section: Classification vocabulary carried from the BRD-linked r2 working set

Required finish: What is it for? — game-day · thanksgiving · christmas · hanukkah · passover · easter · ramadan-and-eid · diwali · lunar-new-year · fourth-of-july · halloween · valentines-day · birthday · potluck · picnic · camping · date-night · feeding-a-crowd · cooking-for-two · spring · summer · fall · winter — keywords

classification-vocabulary-carried-from-the-brd-linked-r2-working-set:i-style

Requirement: I. Style

BRD section: Classification vocabulary carried from the BRD-linked r2 working set

Required finish: What mood is it? — comfort-food · budget · family-friendly · copycat · leftovers · lunchbox · light-and-fresh — keywords

full-site-acceptance-amendment-october-6-current:m-engine-provenance-and-size

Requirement: M — Engine provenance and size

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Static artifact contains at least 100 distinct complete actual engine outputs with stable IDs, exact agreed common-intake/method/input/output receipt and review for permitted mockup use. Independently account for count/duplicates/completeness and reviewer disposition. Same dataset across five is allowed; handmade/copied recipes, duplicate cards and placeholders do not count.

full-site-acceptance-amendment-october-6-current:n-full-content-navigation

Requirement: N — Full content navigation

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Browse/search/filter/category/collection → recipe, article → recipe, ingredient/technique/resource → recipe and exact return all work; no empty stubs/broken relationships. Exercise representative normal/empty/back paths; record static inventory for the full catalog.

full-site-acceptance-amendment-october-6-current:o-demo-identity-and-book

Requirement: O — Demo identity and book

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Same named demo login and newly generated mock-only password on all five, never real company credentials. Exercise correct/incorrect login, logout and intended-action return; save/unsave, create/rename/remove collection, organize, reopen and applicable notes/progress. Empty book, duplicate save and storage denial/corruption are truthful. No database or false secure-account/cross-device claim.

full-site-acceptance-amendment-october-6-current:p-real-email-boundary

Requirement: P — Real email boundary

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Existing approved Gateway/mail service and provider are actually bound; server fixes the recipient to Michael, forbids arbitrary recipient/sender/template/return overrides and applies existing bounded abuse/replay controls. Provider secrets are absent from public source/bundles/URLs. Demo password is not a service grant. Unauthorized-recipient verification must prove refusal without sending to anyone else.

full-site-acceptance-amendment-october-6-current:q-delivered-campaign-loop

Requirement: Q — Delivered campaign loop

BRD section: Full-site acceptance amendment — October 6, current

Required finish: At each applicable campaign, explicit signup action → honest pending/success/error → actual permitted email delivered to Michael → designed email button → exact originating mockup host and campaign landing. Retain receipt and actual delivered-content/return evidence; accepted/queued alone is not delivery. Fresh-tab/logged-out return still reaches useful content. No hidden marketing enrollment.

full-site-acceptance-amendment-october-6-current:r-retry-refusal

Requirement: R — Retry/refusal

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Send double-click/retry uses the admitted deduplication/reconciliation path; failed/unknown outcome is not called delivered or blindly replayed. Record the actual owner controls and evidence; do not perform unauthorized fault injections or extra-recipient sends. Browser save/share/print denial and full cooking return remain covered.

full-site-acceptance-amendment-october-6-current:s-hosted-whole-site-inspection

Requirement: S — Hosted whole-site inspection

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Exact GitHub source and Vercel build/deployment evidence plus actual browser/Vision mobile and desktop inspection and exercised full journeys; repair and re-inspect affected candidate. First-page screenshot, 200 response or successful scaffold build alone cannot pass.

full-site-acceptance-amendment-october-6-current:a-reference-binding-and-distinction

Requirement: A — Reference binding and distinction

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Selected reference/order is explicit; this front page's structure, typography, imagery, spacing, navigation and responsive composition match the intended adaptation. Own-brand scope is respected. — UI/UX source capture/locator and side-by-side phone then desktop review; unresolved reference identity cannot pass.

full-site-acceptance-amendment-october-6-current:b-first-useful-action

Requirement: B — First useful action

BRD section: Full-site acceptance amendment — October 6, current

Required finish: A guest understands the Recipe promise and can reach a useful fixture without forced account, contact capture or internal implementation clutter. — Hosted first-page interaction and exact destination.

full-site-acceptance-amendment-october-6-current:c-discovery-and-return

Requirement: C — Discovery and return

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Applicable search/filter/category/detail controls produce real fixture results; empty/reset and back preserve useful context. — Normal and empty-result flow, back/return evidence; explicit applicability disposition if absent from the reference.

full-site-acceptance-amendment-october-6-current:d-content-and-assets

Requirement: D — Content and assets

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Complete coherent yield, ingredients, equipment and ordered instructions; required hero/ingredient/step imagery is meaningful and source-suitable. No unsupported qualification/testing/endorsement claims. — Fixture/asset review plus rendered full recipe, including image failure behavior.

full-site-acceptance-amendment-october-6-current:e-cooking-state

Requirement: E — Cooking state

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Applicable checks, steps, help and timers work; view/disclosure changes preserve work. Clear/reset has scoped effect. Timer end makes no safety claim. — Before/after and refusal/recovery evidence; no silent restart/duplicate alert on return.

full-site-acceptance-amendment-october-6-current:f-quantity-and-units

Requirement: F — Quantity and units

BRD section: Full-site acceptance amendment — October 6, current

Required finish: All presented selections resolve to supported meaningful fixture states; invalid input retains correct last valid state. Time/temperature do not scale proportionally. — Supported/unsupported/invalid examples, meaning review; no unapproved production-engine call.

full-site-acceptance-amendment-october-6-current:g-connected-local-flow

Requirement: G — Connected local flow

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Applicable cooking/shopping/gathering views transfer selected meaning without losing progress or forcing navigation. — Forward and return flow with exact local/demo boundary; no external plan or invite effect.

full-site-acceptance-amendment-october-6-current:h-print

Requirement: H — Print

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Printed recipe is readable, unclipped, complete and uses current supported servings/units. Required safety remains; QR/return points to this mockup's recipe. — Hosted browser print-preview/PDF evidence and cancel/return state, as applicable.

full-site-acceptance-amendment-october-6-current:i-save-share-account-truth

Requirement: I — Save/share/account truth

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Browser-local saving/sharing either works in its stated scope or reports denial. Demo account/payment behavior never claims production success. Real signup email is restricted to the named recipient and requires actual delivery evidence; no arbitrary personal-data collection or hidden subscription. — Storage/clipboard denied and normal states; observed network/effect boundary.

full-site-acceptance-amendment-october-6-current:j-phone-and-accessibility

Requirement: J — Phone and accessibility

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Phone layout/touch/readability and reduced motion work; keyboard order/focus, accessible names and dialog return are coherent; desktop independently works. — Actual viewport dimensions, browser, input mode/emulation, screenshots and interaction notes. A phone failure holds affected readiness.

full-site-acceptance-amendment-october-6-current:k-isolation-and-exposure

Requirement: K — Isolation and exposure

BRD section: Full-site acceptance amendment — October 6, current

Required finish: No shared runtime imports/state or unapproved production bindings with Network or other mocks; no private operational material in public assets or routes. — Assigned source inspection and hosted request/route inspection; the deployment owner verifies private information stays protected.

full-site-acceptance-amendment-october-6-current:l-deployment-and-decision

Requirement: L — Deployment and decision

BRD section: Full-site acceptance amendment — October 6, current

Required finish: Exact candidate builds and is served at https://recipe-mock-4.isthebestrecipe.com; failures are retained and replacement checked. Independent review and Michael's decision are recorded separately. — Commit, deployment URL/ID, build result, canonical host readback, reviewer and actual acceptance disposition.

Prose scope retained alongside row requirements

The full static journey includes canonical category/item routes, category and collection pages, article/ingredient/technique/library pages, campaign landing, book and login. Own visual identity and all supported taxonomy/occasion coverage, before-cook guidance, guided cooking/placekeeping/timers, local shopping, supported scaling/units/preferences/versions, exact return and error recovery remain required. Transformers and localization are excluded by the current scope. No absence from the current baseline schema cancels these obligations. Owner: Frontend/UIUX with Batch/Content/Software. Source: partial; hosted and independent review: not verified. Next: bind current owner fields, implement missing routes and interactions, then review. Updated: 2026-10-07T01:37:25.522Z.

Change record

Update rule

Every implementation commit updates affected requirement rows, evidence, next action, timestamp and this change record. A timestamp-only edit is not a substantive status update. Use source digests or a prior verified revision, never a self-referential commit hash. Mac branches and main maintain separate proof.

section:accepted-public-brd-and-implementation-status-october-6-2026

Requirement: Accepted public BRD and implementation status — October 6, 2026

BRD section: Accepted public BRD and implementation status — October 6, 2026

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:public-documentation-and-status-acceptance

Requirement: Public documentation and status acceptance

BRD section: Public documentation and status acceptance

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:mandatory-checklist-coverage-to-preserve

Requirement: Mandatory checklist coverage to preserve

BRD section: Mandatory checklist coverage to preserve

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:accepted-activity-ux-correction-october-6-2026

Requirement: Accepted activity UX correction — October 6, 2026

BRD section: Accepted activity UX correction — October 6, 2026

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:traceable-acceptance-delta

Requirement: Traceable acceptance delta

BRD section: Traceable acceptance delta

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:ownership-and-result-handling-for-this-delta

Requirement: Ownership and result handling for this delta

BRD section: Ownership and result handling for this delta

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:expanded-complete-product-contract-october-6-current

Requirement: Expanded complete product contract — October 6, current

BRD section: Expanded complete product contract — October 6, current

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:engine-output-static-consumer-acceptance

Requirement: Engine output → static consumer acceptance

BRD section: Engine output → static consumer acceptance

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:bounded-real-mail-contract

Requirement: Bounded real mail contract

BRD section: Bounded real mail contract

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:scope-and-evidence

Requirement: Scope and evidence

BRD section: Scope and evidence

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:full-recipe-coverage-map-builders-batch-and-reviewers

Requirement: Full Recipe coverage map — builders, Batch and reviewers

BRD section: Full Recipe coverage map — builders, Batch and reviewers

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:classification-vocabulary-carried-from-the-brd-linked-r2-working-set

Requirement: Classification vocabulary carried from the BRD-linked r2 working set

BRD section: Classification vocabulary carried from the BRD-linked r2 working set

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:consumer-schema-and-handoff-consequence

Requirement: Consumer schema and handoff consequence

BRD section: Consumer schema and handoff consequence

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:october-6-michael-correction-controlling-public-identity-and-content-requirements

Requirement: October 6 Michael correction — controlling public identity and content requirements

BRD section: October 6 Michael correction — controlling public identity and content requirements

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:selected-composition

Requirement: Selected composition

BRD section: Selected composition

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:october-6-full-site-expansion-controlling-amendment

Requirement: October 6 full-site expansion — controlling amendment

BRD section: October 6 full-site expansion — controlling amendment

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:full-site-acceptance-amendment-october-6-current

Requirement: Full-site acceptance amendment — October 6, current

BRD section: Full-site acceptance amendment — October 6, current

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:latest-correction-acceptance-additions

Requirement: Latest correction acceptance additions

BRD section: Latest correction acceptance additions

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:october-6-public-brand-and-content-correction

Requirement: October 6 public-brand and content correction

BRD section: October 6 public-brand and content correction

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:shared-login-implement-now-in-all-five

Requirement: Shared login — implement now in all five

BRD section: Shared login — implement now in all five

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:fixed-campaign-bindings-build-these-exact-routes

Requirement: Fixed campaign bindings — build these exact routes

BRD section: Fixed campaign bindings — build these exact routes

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

fixed-campaign-bindings-build-these-exact-routes:recipe-mock-1

Requirement: recipe-mock-1

BRD section: Fixed campaign bindings — build these exact routes

Required finish: welcome-1 — https://recipe-mock-1.isthebestrecipe.com/campaigns/welcome-1 — Your recipe collection from Is the Best Recipe

fixed-campaign-bindings-build-these-exact-routes:recipe-mock-2

Requirement: recipe-mock-2

BRD section: Fixed campaign bindings — build these exact routes

Required finish: welcome-2 — https://recipe-mock-2.isthebestrecipe.com/campaigns/welcome-2 — Your recipe collection from Is the Best Recipe

fixed-campaign-bindings-build-these-exact-routes:recipe-mock-3

Requirement: recipe-mock-3

BRD section: Fixed campaign bindings — build these exact routes

Required finish: welcome-3 — https://recipe-mock-3.isthebestrecipe.com/campaigns/welcome-3 — Your recipe collection from Is the Best Recipe

fixed-campaign-bindings-build-these-exact-routes:recipe-mock-4

Requirement: recipe-mock-4

BRD section: Fixed campaign bindings — build these exact routes

Required finish: welcome-4 — https://recipe-mock-4.isthebestrecipe.com/campaigns/welcome-4 — Your recipe collection from Is the Best Recipe

fixed-campaign-bindings-build-these-exact-routes:recipe-mock-5

Requirement: recipe-mock-5

BRD section: Fixed campaign bindings — build these exact routes

Required finish: welcome-5 — https://recipe-mock-5.isthebestrecipe.com/campaigns/welcome-5 — Your recipe collection from Is the Best Recipe

section:signup-request-interface-and-consent

Requirement: Signup/request interface and consent

BRD section: Signup/request interface and consent

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

signup-request-interface-and-consent:202

Requirement: 202

BRD section: Signup/request interface and consent

Required finish: accepted — “Your demo link was accepted for sending. Check your inbox.”

signup-request-interface-and-consent:200

Requirement: 200

BRD section: Signup/request interface and consent

Required finish: already_accepted — “This demo link was already requested. Check your inbox.” No second send.

signup-request-interface-and-consent:400

Requirement: 400

BRD section: Signup/request interface and consent

Required finish: invalid_request — “The request could not be submitted.” Preserve page context.

signup-request-interface-and-consent:403

Requirement: 403

BRD section: Signup/request interface and consent

Required finish: not_available — “Email verification is not available for this request.” No effect.

signup-request-interface-and-consent:429

Requirement: 429

BRD section: Signup/request interface and consent

Required finish: limit_reached — “This demo's verification limit has been reached.” No countdown implying automatic reset.

signup-request-interface-and-consent:503

Requirement: 503

BRD section: Signup/request interface and consent

Required finish: unavailable — “Email is temporarily unavailable. Your demo session is unchanged.” No simulated success.

section:mail-owner-enforcement-and-finite-verification-budget

Requirement: Mail owner enforcement and finite verification budget

BRD section: Mail owner enforcement and finite verification budget

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:email-logo-binding-october-6-revision-3

Requirement: Email logo binding — October 6, revision 3

BRD section: Email logo binding — October 6, revision 3

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

email-logo-binding-october-6-revision-3:recipe-mock-1

Requirement: recipe-mock-1

BRD section: Email logo binding — October 6, revision 3

Required finish: https://recipe-mock-1.isthebestrecipe.com/images/visual-brand-wordmark-v1-preview.png

email-logo-binding-october-6-revision-3:recipe-mock-2

Requirement: recipe-mock-2

BRD section: Email logo binding — October 6, revision 3

Required finish: https://recipe-mock-2.isthebestrecipe.com/images/visual-brand-wordmark-v1-preview.png

email-logo-binding-october-6-revision-3:recipe-mock-3

Requirement: recipe-mock-3

BRD section: Email logo binding — October 6, revision 3

Required finish: https://recipe-mock-3.isthebestrecipe.com/images/visual-brand-wordmark-v1-preview.png

email-logo-binding-october-6-revision-3:recipe-mock-4

Requirement: recipe-mock-4

BRD section: Email logo binding — October 6, revision 3

Required finish: https://recipe-mock-4.isthebestrecipe.com/images/visual-brand-wordmark-v1-preview.png

email-logo-binding-october-6-revision-3:recipe-mock-5

Requirement: recipe-mock-5

BRD section: Email logo binding — October 6, revision 3

Required finish: https://recipe-mock-5.isthebestrecipe.com/images/visual-brand-wordmark-v1-preview.png

section:designed-email-template-recipe-mock-welcome-v3-

Requirement: Designed email — template recipe-mock-welcome-v3

BRD section: Designed email — template recipe-mock-welcome-v3

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:consumer-changes-and-acceptance-receipt

Requirement: Consumer changes and acceptance receipt

BRD section: Consumer changes and acceptance receipt

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

Public projection correction

Updated: 2026-10-07T01:39:37.445Z. Retained current CRM login, account lifecycle, purpose/consent, fixed campaign bindings, finite send/retry/refusal, logo/message, exact-return and proof obligations even where located in mixed execution appendices. Only private addresses/paths/actor identifiers and unrelated execution history are excluded. Section-level rows now trace prose obligations in addition to explicit criteria. Static public JSON is generated from these two documents and checked for parity at hosted prebuild/CI; raw source documents are not imported by application routes.

Document rendering correction: CRM message examples render as escaped code blocks; long requirement identifiers wrap on phones. Unknown Markdown prefixes cannot stall rendering. Removed the unused raw-document runtime reader; deployed routes import only the generated public projection. Hosted checks and independent acceptance remain pending.

Independent QA round 1 corrections

Updated: 2026-10-07T02:05:52.0711406Z

Read-only evidence: Mac QA round 1, product/qa/MAC-QA-ROUND1.md on the independent mac-claude-qa branch at 06e5319. Observations apply to hosted source 9ed9c7d9 at 320x700, 390x844 and 1440x900 on October 7 UTC. Main and alternate branches remain separate; this intake does not merge either branch or claim the alternate has these changes.

M4-R1-F01 source correction: removed the public design-study identity from the footer. Is the Best Recipe remains the brand; local-storage and AI-illustration disclosures remain. PUB-DOC-02 source correction: public-business-v2 removes internal reference attribution, operational provenance, execution directions and mail binding locators while retaining business acceptance, finite send limits, consent, refusal, exact return and full checklist obligations. Existing source BRD is unchanged. Source fix is not a deployed pass.

Prior hosted CI evidence: https://github.com/everintent/recipe-mock-4/actions/runs/37558509851 passed on 6ffe709; does not establish this candidate's hosted behavior.

M4-R1-F01

Requirement: Public brand identity

M4-R1-F03

Requirement: Honest empty library versus zero search results

M4-R1-F04

Requirement: Branded not-found recovery

M4-R1-F05

Requirement: Complete canonical route inventory

M4-R1-F06

Requirement: No empty learning destinations

M4-R1-F07

Requirement: Invalid recipe recovery

Progress and dashboard increment

Scope edition: PROGRESS-GROUPS-1. D=10 accepted common groups. Every criterion maps to one primary group. Headline group completion requires every child complete at its respective source/deployed/independent-review state. Partial groups never count as complete; child counts are diagnostic only. The current full groups remain incomplete, even where the source shell or route works. Zero verified groups is not a claim that no useful source work exists.

Prior candidate 56c17fe remains independently publishable. This increment adds /status.html, derived metrics and a session-gated device-local /dashboard and /my-recipe-book. Session gating is public-demo usability, not secure authentication. Existing book storage is reused; collection creation/rename/deletion and notes operate locally. Real-recipe dependent acceptance remains blocked on content. A disallowed return URL falls back to /dashboard. Logout keeps saved recipes/notes; storage failure is explained rather than claimed persistent.

section:accepted-progress-percentages-and-working-dashboard-october-6-2026

Requirement: Accepted progress percentages and working dashboard — October 6, 2026

BRD section: Accepted progress percentages and working dashboard — October 6, 2026

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

section:common-progress-definitions-for-all-five-sites

Requirement: Common progress definitions for all five sites

BRD section: Common progress definitions for all five sites

Required finish: All current business obligations in this section, including prose and listed steps; individual table criteria remain separately indexed below.

common-progress-definitions-for-all-five-sites:g01

Requirement: G01

BRD section: Common progress definitions for all five sites

Required finish: 100 distinct complete original Recipe-engine/common-intake outputs, retained provenance and required review, actually integrated as static content

common-progress-definitions-for-all-five-sites:g02

Requirement: G02

BRD section: Common progress definitions for all five sites

Required finish: Complete articles, ingredient/technique/resource libraries, supporting guidance and relationships

common-progress-definitions-for-all-five-sites:g03

Requirement: G03

BRD section: Common progress definitions for all five sites

Required finish: Search/category/collection/classification, canonical routes/metadata, filtering/back/error/empty-state discovery

common-progress-definitions-for-all-five-sites:g04

Requirement: G04

BRD section: Common progress definitions for all five sites

Required finish: Own public identity and distinct accurate dish/ingredient/step imagery, rights, captions and responsive presentation

common-progress-definitions-for-all-five-sites:g05

Requirement: G05

BRD section: Common progress definitions for all five sites

Required finish: Find/decide/shop/cook/print/adapt activities, supported quantities/units/substitutions, timers/placekeeping and recovery

common-progress-definitions-for-all-five-sites:g06

Requirement: G06

BRD section: Common progress definitions for all five sites

Required finish: Demo login/session/dashboard, My Recipe Book/save/collections/notes/versions, persistence/reset/logout and supported sharing/return

common-progress-definitions-for-all-five-sites:g07

Requirement: G07

BRD section: Common progress definitions for all five sites

Required finish: Existing bounded real-email contract, consent/status, authorized transport/inbox and exact campaign return

common-progress-definitions-for-all-five-sites:g08

Requirement: G08

BRD section: Common progress definitions for all five sites

Required finish: NO ADS EVER, accessibility/phone/desktop quality, honest limitations and dated evidence/independent repair-recheck requirements

common-progress-definitions-for-all-five-sites:g09

Requirement: G09

BRD section: Common progress definitions for all five sites

Required finish: Public /BRD.HTML and /status plus /status.html, safe complete business projection, task traceability, discoverable responsive reading and independent branches

common-progress-definitions-for-all-five-sites:g10

Requirement: G10

BRD section: Common progress definitions for all five sites

Required finish: Derived honest progress metrics, explicit source/deployed identities, freshness and meaningful-update/coverage validation

PROG-01

Requirement: PROG-01 — Status paths

BRD section: Traceable acceptance delta

Required finish: /status.html and /status both resolve to the current status experience, with the same source data; a redirect is acceptable if it preserves the destination. Homepage/footer status navigation remains visible and usable on phone/desktop, with direct navigation, revisit/back and refresh exercised. Keep /BRD.HTML working.

PROG-02

Requirement: PROG-02 — Derived metrics

BRD section: Traceable acceptance delta

Required finish: Implement the D/I/H/V definitions, denominator edition, exact counts and blocked/open/unknown values above from TASKS. Demonstrate a known incomplete/blocked row stays out of completed counts, changed evidence is invalidated appropriately and percentages update deterministically. No invented current progress values.

PROG-03

Requirement: PROG-03 — Freshness and validation

BRD section: Traceable acceptance delta

Required finish: Hosted checks catch missing/duplicate denominator IDs, uncovered accepted requirements, inconsistent states/evidence, stale projection and meaningful changes without task updates. Display source versus deployed identity and update times clearly. Verify the hosted page against the exact assessed TASKS revision, including refresh after a real new deployment; do not promise automatic live updates before deploy.

DASH-01

Requirement: DASH-01 — Working login entry

BRD section: Traceable acceptance delta

Required finish: The existing public disposable demo account validates correct/incorrect credentials and establishes the scoped local demo session. Ordinary successful sign-in opens /dashboard with a clear account entry. Preserve existing same-origin pending-save/campaign return exactly once when login originated there, and provide a direct dashboard link; the new default dashboard must not break accepted intended-action return. Incorrect credentials never create a session.

DASH-02

Requirement: DASH-02 — Session-gated route

BRD section: Traceable acceptance delta

Required finish: Direct /dashboard access without a valid demo session redirects to the existing login flow with safe intended return; successful login returns to the dashboard. Refresh/back/history and logout cannot expose an active dashboard session after logout. Client-side demo route gating is a usability state, not secure protection for private data. No real customer data or server identity claims.

DASH-03

Requirement: DASH-03 — Useful dashboard

BRD section: Traceable acceptance delta

Required finish: Provide actual functioning saved-recipe access, collection create/rename/delete/organization and supported notes/personal-version entry using existing browser-local data. Reflect the same data as My Recipe Book without a divergent store. Show useful empty states and clear ways back to browse and manage collections; do not fabricate saved recipes or the missing 100-recipe corpus. Recipe-dependent acceptance remains open until real reviewed content is available.

DASH-04

Requirement: DASH-04 — Persistence and recovery

BRD section: Traceable acceptance delta

Required finish: Exercise save/organize/note update and refresh/back/reopen, logout and subsequent login, deliberate local clear/reset and unavailable/corrupt storage. Preserve existing logout-versus-book-clearing meaning and give truthful local-only/device-origin limits. No cloud synchronization, paid service, production authentication or new backend follows. If real identity is later wanted, retain it as a separate decision.

DASH-05

Requirement: DASH-05 — End-to-end proof

BRD section: Traceable acceptance delta

Required finish: Assigned QA performs real hosted clicks: guest dashboard redirect → incorrect login → correct login → working dashboard → collections/notes/saved-item interactions where real data permits → refresh/back → logout → denied dashboard access. Record exact URL/deployment/source, viewport, screenshot, result, missing-content limits and fix/recheck. Source or logged-in badge alone cannot pass.

Independent deployed document recheck

QA observed the F01 footer correction on source56c17fe, deployment dpl_3x5Fx1sH1BG2wRtBsHrcUy7bj7NL on October6 19:09–19:13 PDT. This closes only that bounded footer observation; complete identity/imagery group remains open. New finite D14/D15 findings below are source-fixed in this increment and require exact hosted recheck.

D14

Requirement: Phone BRD overflow observed: viewport390, document scroll524. Source correction constrains document and table wrappers, wraps identity/long content and keeps table overflow local.

D15

Requirement: Empty deployment revision created malformed blob// source URL. Source now admits only a nonempty40-hex revision; otherwise displays unknown and working labeled main fallback.

Dashboard guard correction: pageshow/focus recheck the session and pagehide clears admitted UI state, so Back after logout cannot retain an active dashboard claim. Source identity validates full nonempty SHA and labels normalized LF source digests. No Mac branch was merged or changed.

Validation increment: hosted guard rejects a verified child without deployed evidence, checks every mapped group/state and preserves the existing missing-coverage, stale-output and meaningful-update rejection cases. Public progress uses the common ten-group edition; source changes in this candidate carry no stale live pass.

R4-DASH-01 and progress-proof correction

Updated: 2026-10-07T02:22:02.475Z

Source correction: dashboard storage warnings render independently as alerts and cannot be masked by successful-operation notices. Collection success describes tab state, not guaranteed device persistence. Both account logout paths retain session state and explain failure when deletion throws. Existing restoration and prior D14/D15 fixes remain unchanged. Hosted denied-storage/logout-failure recheck is pending.

PROG-02 evidence correction: implemented child rows bind application-and-validation-v1 scope digest (all app except generated documents, all validation scripts, package and current BRD; normalized LF). Completed hosted/review rows additionally require an immutable assessed source, evidence time, matching evidence scope digest and explicit unchanged-scope reuse. Any changed scope invalidates old proof; reset deployed/review states until rechecked. Current hosted/review group totals remain zero. Hosted negative cases cover stale/missing bindings and duplicate identity, plus an explicit unchanged-scope positive fixture. These are validation fixtures, not fabricated actual evidence. Prior source becba61211271c789ed26fb02fd798c8ae3df4b3; exact new pin supplied after commit.

Hosted build correction: becba612 failed with EISDIR because the physical status.html route conflicts with the /status prerender filename. Removed that physical route and configured an exact /status.html rewrite to /status. Source scope includes next.config.ts. Prior public documents remain live; this is a source repair awaiting replacement hosted build, not a claimed successful deployment.

Return to recipes