Skip to content

Remix submit flow

Send it through the gates

Every submission runs the automated audit gate first — accessibility and quality for components, fidelity and style-lint for prompts — and then a human decides. The form below is a browser-local demo, but the queue it feeds is the same surface the team reviews in the admin console.

Remix submit flow

Submit a remix of any published asset. It lands in the moderation queue with the audit gate marked pending — the same queue the team already reviews in the admin console. This form stores your entry in this browser (demo); the queue shows it immediately.

0 in your local queue

Real submissions would run the audit gates (a11y for components, fidelity for prompts) before a human sees them. Score fields on your entry stay 0 and gates read pending because nothing was actually audited — the queue labels them that way on purpose.

01

You submit

Title, handle, what you based it on and what changed. Nothing else is required — a remix note beats a description.

02

Gates run first

Components face the a11y audit, the lint pass and a sandbox check; prompts face fidelity scoring and style lint. Failing the sandbox is a default reject.

03

A human decides

The queue currently holds 10 sample submissions with mixed gate outcomes — including one deliberate lint failure and one safety flag — so every decision path stays visible.

What we ask of a remix

  • Keep it original: read the original before you change it, and do not paste in code you cannot explain.
  • Name the trade you made — smaller bundle, better keyboard behaviour, calmer motion are all valid reasons.
  • Respect the licence of what you fork (components are MIT, guides are CC BY 4.0) and credit the original.
  • Expect the gates: a failing lint or sandbox check is a conversation, not a verdict on you.

To reach verified, a submission needs:

  • ☐ three recorded model runs, failures included
  • ☐ palette tokens the body refers to
  • ☐ reduced-motion and token lines in the brief
  • ☐ blocks in title case, stacks from the enum
  • ☐ viewport and target audience stated
  • ☐ the craft-floor linter passing (item #69)