Your taste is
training data
no model contains.

Point your agent at Wedges. It runs the Both Hands Full exercises, then hands back one file — your voice, your eye, the things you refuse to outsource — so the machine works from your taste, not its defaults.

$ claude mcp add --transport http wedges https://wedges.dev/api/mcp

then say “run Wedges” · other clients ↓

The problem

AI is a mirror.

Specificity in, cinema out. Generic in, content out. Feed it a vague brief and it hands back the average of everyone. Here’s one real paragraph through the Mirror Booth:

Yours

We shot the whole thing on a borrowed Bolex in my nonna’s kitchen in East Van, the light going amber through the cheap curtains while she rolled gnocchi and refused to look at the lens.

Flattened by the machine

We shot the whole thing on a borrowed camera in a kitchen, the warm light coming through the curtains while she cooked.

Bolex → camera. Nonna’s East Van kitchen → a kitchen. The gnocchi, the cheap curtains, the refusal to look at the lens — gone. That’s your work becoming content. Wedges catches it, and teaches your agent the difference.

The artifact

One file.
Your taste,
portable.

Run the exercises once. Export a taste-profile.md you keep — markdown and JSON — and load it into any agent so it works from your judgment instead of the model’s defaults.

Nothing is stored on our end. The profile is yours.

# Taste Profile — Kris

> Load this so you serve Kris's work
> without flattening it.

## Voice patterns
PRESERVE  concrete place-names · the
          cheap-curtains specificity ·
          refusing to explain the joke
WATCH     "camera" (it's a Bolex) ·
          "a kitchen" (nonna's, East Van)

## Irreducibles — what AI can't eat
- Laughing until you can't breathe
- Getting lost in the woods, not caring

## Taste under pressure
Consistency 70% — your hand keeps
moving toward risky, specific cuts.

Connect your agent

One line. No account. No key.

Wedges is public and stateless. The exercises run through your agent; the profile comes back to you. Use the shared key, or bring your own Anthropic key for more depth.

One line in your terminal:

$ claude mcp add --transport http wedges https://wedges.dev/api/mcp

Then tell your agent: “run the Wedges taste extraction.” It self-drives from there.

What runs

Six exercises. One profile.

01mirror_boothPaste a paragraph in your voice. See exactly which specifics get sanded down.
02taste_auditPoint it at up to twelve images of your work. It names your recurring choices — and the moves you always avoid.
03selector_pressure_testTen rounds. Pick what you'd ship, defend the cut. A deterministic read on your taste under pressure.
04name_irreduciblesThe things you refuse to outsource. The things AI can't eat.
05three_documentsStyle guide, worldview, glossary — gathered in conversation, the way the keynote teaches it.
06export_profileAssembles all of it into the portable artifact you keep.

Then bring it to people

Film Club.

A profile is yours alone until you put it in a room. Start a Film Club, send the link to a few people you trust, and drop one unfinished thing. Everyone reads everyone’s work through their taste— what they’d cut, where it goes generic, whether they’d ship it. Real feedback, not polite feedback.

Start a room ◣