What, you've never seen industrial strength sandwich production?

[1] https://www.youtube.com/watch?v=_YdWBEJMFyE

[2] https://www.youtube.com/watch?v=tRUfdBEpFJg

You forgot to accomodate for MCP. You don't expect us to build the sandwiches manually as if we were cavemen living in 2023 do you???

I asked claude to use this and create a ham salad sandwich with no onion for me https://gist.github.com/aranw/c2b59f42b20eb47e01bc66841233c2...

I'll email this over to my local bakery on Monday for my lunch order might need to make some modifications for there build environment

This promotes impractical version pinning. That leads to spoilage unless the lockfiles are updated every few hours. Freshness should be checked at build time, and the resolved version for each ingredient recorded in the SBOM but a lockfile SHOULD NOT be used for perishable ingredients. Bacteria will result in Spoilage Vulnerabilities if versions are locked inappropriately.

Some sandwich ingredients are known to be used both as standard toppings and as sauce components. To avoid ambiguity, condiments such as guacamole and relish (as well as ketchup) SHOULD define a stable API (Avocado and Pickle Interface).

So is "toasting the bread a little bit" in the semver for the bread? Is this part of the integrity hash?

Where are post assembly instructions stored?

Panini and croque monsieur sandwiches are left out of this spec.

Author didn't post the repo so I don't know where to submit an issue.

This is fantastic, now, after implementing SAP home edition at your house, you’ll be able to use the procurement module and leverage EDI to source the ingredients of your sandwich while maintaining full traceability according to the relevant ISO standards.

Hopefully this has built in support for second sourcing

> The 2025 egg price crisis was a cascading failure equivalent to a left-pad incident, except it affected breakfast.

They better load the SBOM correctly in SAP.