Project B: framecache
This one’s a library crate, not a CLI. framecache decodes raw CAN
frames into named, scaled signal values and keeps a latest-value cache
that other components query. In real life, several internal teams would
depend on a crate like this. That’s the kind of pressure we’re
simulating.
What we’re practicing:
- Skeleton-first as the working method. Yesterday the skeleton was the first milestone. Today it’s a deliverable: written by hand, reviewed, and frozen before generation starts.
- Spec review under pressure. This spec, like real specs, was assembled from several stakeholders with their own concerns. Part of today’s deliverable is whatever your review of it finds, found before generation starts, not after.
- The material from yesterday’s smell catalog. Keep it at hand.
Working agreement: same pairs, roles swapped from yesterday’s end. The review log continues, with a new section for spec findings: every question, gap, or surprise raised against the spec, with its resolution in writing.