Equipment, not endorsements
Compartments describe the kind of work. Object size is composition, not a ranking, mastery score, or claim about expertise.
Lab 04 / Interactive inventory
Not software I know. Equipment I use to build things.
Interface design, system definition, interaction prototyping, and the visual decisions that need to survive implementation.
See it used in Designing PaveExploration, synthesis, critique, and turning loose product questions into material that can be tested.
Repository exploration, rapid prototyping, implementation support, and design-system automation.
The portable workbench for editing product code, inspecting behavior, and tightening the handoff between design and implementation.
Builds, tests, repository operations, local tooling, and the unglamorous checks that keep prototypes honest.
Versioned product work, reviewable changes, and a shared place for design decisions to meet production code.
See it used in Designing PavePlanning, sequencing, and keeping product decisions connected to delivery without pretending the ticket is the work.
Working notes, research material, decision trails, and the archive needed when memory stops being a dependable interface.
Compartments describe the kind of work. Object size is composition, not a ranking, mastery score, or claim about expertise.
The open case is one limited-palette pixel raster with semantic HTML hit areas layered over each compartment. Labels, focus states, and inspection behavior remain native HTML.
Keyboard controls, reduced motion, and a readable no-JavaScript inventory are part of the object—not cleanup after it.