Szymon P. Peplinski × Opus 4.7
Feedback enters the product process as evidence.
Core trick
Clusters public app reviews, audits them against six design lenses, and re-audits the proposed direction, outputting a markdown brief with SHA-256 provenance.
Description
Feedback enters the product process as evidence. It leaves as opinion. Auditable Design keeps the reasoning intact.
The system reads a public Duolingo review corpus, clusters recurring friction, audits it through six canonical design lenses (Norman, WCAG, Kahneman, Osterwalder, Cooper, Garrett), grounds findings in the actual product interface, proposes a direction, and re-audits before handoff.
The output is a single markdown brief: measured pain, priority reasoning, validated direction, and full provenance (SHA-256) for every input.
The brief is implementation-ready: the demo shows the brief and the corrected mockup side by side.
The key contribution of Opus 4.7 appears at the verification stage.
During real-product inspection, Opus 4.7 surfaced a pricing inconsistency no upstream layer identified: Super costs 500 gems on one screen and 450 on another — same product, same session.
This was not present in user feedback. It was not defined in the heuristic baseline. It required comparing pixels across separate screens.
Under identical conditions, Sonnet 4.6 confirmed all baseline heuristics but surfaced no additional findings. Opus 4.6 produced adjacent observations. Only Opus 4.7 produced a new, independent observation.
The difference is not accuracy. It is the ability to name what is missing.
Cost per cluster: around $1. A qualitative study: tens of thousands.
Not louder recommendations — better accountability.
Built with Claude Opus 4.7 and Claude Code.
README excerpt
# Auditable Design **Built with Claude Opus 4.7.** Decision infrastructure for product teams: preserves the chain of reasoning from raw user feedback to defensible design direction. > Feedback enters the product process as evidence. > It leaves as opinion. > Auditable Design keeps the reasoning intact. Auditable Design reads user feedback, clusters recurring friction, grounds it in the actual product surface, audits pain through six design lenses, prioritises the problem, proposes a direction, and re-audits that direction before handoff to a human designer. The output is not a summary, not a generated UI, and not a shipped decision. It is an **evidence-backed direction brief**: a structured artifact that says what hurts, where it hurts, why it matters, what direction could reduce it, and exactly which evidence supports every claim. This submission showcases Opus 4.7 where product agents need more than fluent summarisation: **grounded dissent, false-positive correction, and independent defect discovery.** Submission for the **Anthropic Built with Opus 4.7** hackathon (21–26 April 2026). --- ## Demo - **[3-minute video walkthrough](https://youtu.be/i9PORz--Aws)** — narrated end-to-end demo - **[Live site](https://speplinski.github.io/hackathon-opus-47)** — interactive walkthrough of the pipeline, the cluster, and the validated direction - **[Example brief output](examples/design_brief_cluster11_opus47.md)** — the markdown artifact a designer actually opens --- ##