Lessons / Part 9. Figures, drawings and deliverables made from code
63 A deliverable carries specifications, not its history
A sheet with numbers and short labels only, and a notes file beside it that holds the assumptions, sources and open points.
What people usually ask
Make the equipment list spreadsheet for the neutralization unit from my notes.
What comes back
A workbook with a column headed Reasoning, cell comments that read “assumed”, and a colour code nobody asked for.
Ask this instead
Make equipment_list.xlsx for the neutralization unit from the attached data. One sheet. Columns: tag, item, material, capacity, design pressure, design temperature, connection size. Numbers and short labels only. No sentence in any cell, no cell comments, no colour, no extra column.
Where the data gives no value, leave the cell empty.
Everything else goes in notes.md beside the workbook: each assumption with the cell it affects, where each value came from, and the open points as questions. One line each.
Print the sheet as a table and the first ten lines of notes.md, then stop.
Attach: The data as a table, or the notes it comes from.
Why it works: The sheet goes to the people who build from it, and the reasoning stays in a file that is opened when a value is questioned.
Drafted with Fable 5.1 from my notes; chosen and edited by me.