Articulate·Hype RadarOverviewDaily logSummary · 2026-05-24

Summary — 2026-05-24

Third pass — 2026-05-24 (Taste Pipeline — references-to-skill)

One item this pass. Surfaced by Anthony from a third-party post describing a reproducible pipeline that turns a curated reference set into an enforceable design skill. Direct counterpart to what Dylan currently hand-curates as the prompt anchor library, and direct mitigation of today's twin visual-misread fails.

Item Source P Q S Total Move
Taste Pipeline — references → dual-model analysis → anonymised fusion → chunked synthesis → rule-set → skill Anthony's chat 2026-05-24, third-party writeup 3 3 2 8/9 Act on. Scaffold as a SuperSebastian playbook + Dylan SOP extension. Pilot on Articulate's own brand against the existing Design/PromptLibrary/Articulate/anchors.md. If pilot proves stronger anchors than hand-curated, promote to standard onboarding step for every new brand or client engagement requiring AI-gen imagery.

The pipeline (six steps, as described)

  1. Curate references. High-resolution, tightly cropped on the details that make the reference work. Load-bearing input — "if the references suck, so does the skill."
  2. Dual-model per-image analysis. Each reference analysed independently by two frontier models (Opus 4.7 + GPT 5.5 in the source post). Focus is on why the reference works as design — layout, spacing, typography, rhythm, composition, hierarchy. NOT functional / what-it-does analysis. Output: reference-NN/opus-4-7-analysis.md + reference-NN/gpt-5-5-analysis.md.
  3. Anonymised fusion. Strip model attribution from the two analyses, hand both to GPT 5.5, get fused-analysis.md per reference. Anonymisation prevents self-preference bias when the fusing model recognises its own output.
  4. Chunked synthesis. Group fused analyses into chunks of ~6–8. Each chunk fuses into a chunk-level rule synthesis. Key insight: all-at-once synthesis summarises instead of preserving granularity. Chunking preserves rules.
  5. Final rule-set. One model pass fuses chunk syntheses into a single rule-set markdown.
  6. Skill. Concrete imperative instructions extracted from the rule-set. Enforces constraints. No vague taste words.

Why P=3 (personal productivity)

Dylan currently hand-curates Design/PromptLibrary/<brand>/anchors.md per the SOP in Design/PromptLibrary/README.md. Five blocks (voice anchor · style anchors · character locks · composition + lighting directives · banned moves) at ~2–4 hrs senior-CD time per brand. Brands live in the library now: Articulate · Articulate-OperatorSequence · Kitroom · Roche-Debbie · _template. Every client engagement seeds a new one. Roger Deakins persona faces the same problem on cinematography references. Pipeline replaces hand-curation with reproducible synthesis — brand seeded in one session, not three.

Why Q=3 (quality)

Three quality moves we don't currently run anywhere in our stack:

Direct mitigation of today's twin fails (FAIL-VISUAL-MISREAD-OGILVY-MARK + FAIL-WORDMARK-PROXY-MISCALIBRATED) — both single-model misreads of visual references that a dual-model triangulation likely catches.

Why S=2 (sellable, not 3)

Maps onto a real Articulate offer surface: "Brand Skill from Your References" — take a client's mood board / brand book / existing creative → produce an enforceable image-gen skill scoped to their brand. Productisable add-on to the brand-voice plugin pattern already in our stack (brand-voice covers copy; this covers visual). Slots into MEP brand-discovery phase. But it is not a standalone product — it is a layer inside Dylan's workflow. S=2 holds until first client engagement scopes "build us a visual brand skill from these references" as a discrete line item, at which point re-score to S=3.

Class-match against failures.md

Four class-matches, all in the same axis (visual rules unenforced because no structural source of truth). Strong adopt signal.

Re-score triggers

Build path (recommended option B — see decisions.md)

Scaffold as SuperSebastian/playbooks/taste-to-skill.md and extend Dylan's /dylan prompts <brand> subcommand with a --from-references flag that fires the pipeline. Not built this pass — playbook scaffold is the next move, pilot is the trigger after that.