Cameo: A Pattern for Channeling Practitioner Taste and Judgment

This is a report on my experience with a pattern I call cameo, routing a specific practitioner's documented judgment into a specific software development task, one dispatch at a time. It emerged while building six applications by myself, one of them important to extended family duties. That work happened in fragments of time outside work, around professional and personal responsibilities, and that constraint is what created the need for the pattern. The pattern is now essential in bassclef, the substrate I built to support that work. The paper documents three things. First, the mechanism itself: a curated catalog of practitioners, a matcher that pairs a problem's shape with the practitioner most likely to have solved that class of problem, and a set of skills that invoke them. Second, where it reached beyond the interface work that originally inspired it, into product structure, backend design, and the substrate's own architecture. Third, where it failed and how those failures were caught. The pattern is not validated at scale. For UX tasks, it ships with a champion-challenger baseline built specifically so it can be shown redundant, and one documented comparison is mixed rather than patently favorable. What this paper claims is priority and mechanism, not proof.