Show the work
Important claims point to a named artifact, version, test, decision, or correction.
Patrick Craven / Learning in public
I'm a line cook, business management graduate, self-taught builder, and founder of Top Shelf Service LLC. I learn by building things I actually need, following the failures until they make sense, and sharing what I learn so you can use it in your own work.

I did not enter software through a formal technical pipeline. I entered through real operating problems and learned by following the failures all the way down.
Restaurant knowledge often lives in binders, memory, and whoever has time to explain. Teach began as an attempt to turn that knowledge into repeatable practice.
Important claims point to a named artifact, version, test, decision, or correction.
Built, failed, planned, and unknown stay separate so the story stays honest.
Each failure becomes a plain-language concept, a practical fix, and a rule I can reuse.
Restaurant-specific training product work that exposed the difference between a useful idea, a working system, a deployment, and verified user value.
Product work exists; pilot outcomes unprovenA publishing system for deterministic scheduling, one authority, idempotency, reconciliation, missed-post handling, and external side effects.
Release 1.1.0 verified; live state needs reconciliationThe policy and contract layer growing out of repeated failures in truth, scope, authority, evidence, recovery, and AI-assisted execution.
Decision baseline exists; runtime incompleteA shared-memory direction for better handoffs between tools and agents, with provenance and an explicit separation between retrieval and truth.
Planned directionI share the quick lessons on X and keep the complete story, proof boundaries, and next experiment here.