Great fun but I will point out that Sandwich is a town in Kent (England, UK). The BoM for Sandwich will be rather more involved than for a sandwich (which will be multiple sub-assemblies of the whole).

etc etc, soz!

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

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.

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

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.

> AGPL (Affero General Pickle License): Same as GPL, but if you serve the sandwich over a network (delivery apps), you must also publish the recipe. This is why most restaurants avoid AGPL pickles.

I love a good APGL joke, and this one especially tickles me because I'm currently a delivery driver instead of a dev.

The most delightful thing I've read in a while.

Finally, something the software industry can learn from: sandwiches have dependency management figured out.

Mmmmmh, specifications

What's the purl (Package URL) equivalent of surl:mystery, for stuff like Claude Code, which now only supports running a script to install? It does have a pretty easy to read install script, but the docs don't suggest reading it before running it as an option, they just say to run it https://code.claude.com/docs/en/setup

Also it doesn't address mold: harmful on bread, wonderful when intentionally added to cheese

Edit: Claude Code has a homebrew cask, and homebrew supports Linux (I haven't been using it on Linux so it didn't occur to me when reading this). It can be specified in purl using pkg:brew.