FA-97298 / Recipe scaling and nutrition / Member archive

Backward recipe step scheduler: step duration offset · case 03

Every step is shown starting at the moment it must finish.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

Steps [name, minutes, depends_on]; a step must finish before any step depending on it starts. Latest start = min(latest start of dependents, serve time) - minutes. Unknown dependency -> "error: unknown step X"; a cycle -> "error: cycle". Serve "HH:MM"; starts print as "HH:MM" modulo 24h (previous day wraps). Output [[name, time]] sorted by absolute start then name.

Why this case matters

Dinner-party and restaurant prep planners schedule long marinades and roasts backward from service.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
chain	`[["prep", "18:30"], ["rest", "18:30"], ["roast", "18:30"]]`	`[["prep", "16:35"], ["roast", "16:45"], ["rest", "18:15"]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.