Hypothesis
Retrospective review expectation stated at recording time: the complete recorded
formulation and Method can reach its intended endpoints and produce the following
finished dish: Beef slowly cooked in coconut milk and aromatics until the sauce fries down to a dark, clinging paste. This is not a hypothesis documented before historical
cooking and is not itself an observed outcome.
Procedure
This record was written on 2026-10-02 from Carlo Kruger’s retrospective report
on that date. Historical cooking dates and trial counts were not recorded.
The exact whole Recipe Version is Beef Rendang v1.
Its preserved source is recipes-tmp/beef-rendang.md with SHA-256 3f16be761399ee605efd29b7f812c9ee65fb32ed3ca14372fb359970259d079a.
The serialized draft SHA-256 is 368515193240dc4369fde70843a6fc37a5ac16095d8817f598dd1243ef067c9a.
The complete formulation and work sequence below are the recorded specification,
not newly observed timings, temperatures or yields. Correspondence to past cooking
is attributed to Carlo’s statement that the recipes as recorded were fully tested.
The historical reconstruction caveats remain in the unchanged source; Carlo’s
2026-10-02 acceptance applies to this formulation and the packet’s explicit clarifications.
PHASE A — SPICE PASTE
Ingredient Uses
Technique Applications
| Technique |
Controls |
Purpose |
| Paste frying |
Medium heat; 12 min–15 min; oil begins to separate |
Cook the aromatic paste. |
Method
- Blend onion, garlic, ginger, galangal, chilli, lemongrass, spices, and oil to a fine paste.
- Fry the paste in a wide heavy pot over medium heat for 12 min–15 min until aromatic and the oil begins to separate.
- Retain the recorded Shallot or red onion, chopped option; the alternative uses the same declared quantity, in place of the first material.
Phase Outputs
| Key |
Phase Output |
Description |
| fried-spice-paste |
Fried spice paste |
Prepared intermediate for a later Phase. Use the entire prepared paste; approximately 700 g is a finished-weight estimate. |
PHASE B — SLOW COOK
Ingredient Uses
Technique Applications
| Technique |
Controls |
Purpose |
| Simmering |
Low gentle simmer; 2.5 h–3.5 h |
Tenderise the beef. |
Method
- Add beef and turn to coat. Add coconut milk, bruised lemongrass, lime leaves, tamarind, sugar, and salt.
- Bring to a gentle simmer. Cook uncovered over low heat for 2.5 h–3.5 h, stirring more frequently as the liquid reduces.
Phase Outputs Used
| Phase Output |
Use |
| Fried spice paste |
Use fried-spice-paste. Use the entire prepared paste; approximately 700 g is a finished-weight estimate. |
Phase Outputs
| Key |
Phase Output |
Description |
| tender-beef |
Tender beef |
Prepared intermediate for a later Phase. Use all beef and its reducing coconut liquid. |
PHASE C — FRY DOWN
Ingredient Uses
Technique Applications
| Technique |
Controls |
Purpose |
| Reduction |
20 min–40 min; dry paste clings to beef |
Reach the dry rendang endpoint. |
Method
- When the beef is tender and the coconut oil separates, add ground toasted coconut.
- Continue cooking and folding gently for 20 min–40 min until the paste is dark, dry, and clings to the beef.
- Remove lemongrass and lime leaves. Rest for at least 30 min before serving.
A wide pot makes the final evaporation controllable. Stir carefully once the beef is tender.
Phase Outputs Used
| Phase Output |
Use |
| Tender beef |
Use tender-beef. Use all beef and its reducing coconut liquid. |
Results
Carlo retrospectively reported that the recipes as recorded were all successful
and fully tested, and approved this whole formulation for production. No further
Recipe-specific observations were supplied. Cooking dates, trial counts, detailed
tasting notes and instrument measurements were not supplied. Source yields are
estimates, not measured results of this retrospective record. Recorded alternatives
have no separate variation-specific testing observations in this report.
Decision
Carlo accepted the formulation as recorded, including the explicit reviewed
clarifications, for production in the complete 25-Recipe batch on 2026-10-02.
Proceed to normal exact-version Promotion after valid serialization, applicable
Curation and reference resolution. Technical validation does not perform that
human acceptance. A materially changed formulation needs its own exact-version
evidence and acceptance; this report does not automatically follow future changes.