Result Card Engine
Every playable ends in one card worth posting. Type a result — a title, one number, an optional insight and badge — and the engine composes the exact strings a shareable card is built from: a headline, a big number, a one-line share string, and accessible alt text. The miatz move is that the card demystifies its own claim: the share string is composed from named parts you can see — the same doctrine as the flagship credential cards, where every share is simultaneously marketing and proof, not a bare vanity score. Runs entirely in your browser (0 uploads, works offline).
How to use it
- Type a title, a score and its label (e.g. "pass rate"), and an optional insight and badge — or hit Load example.
- Watch the styled card preview update live as you type. It's a real HTML card, not a canvas snapshot.
- Open the X-ray panel to see the card broken back into its named parts, plus the composed share string and the alt text a screen reader would announce.
- Copy or share the one-line share string — it always carries the title and the number, so the claim travels with its receipt.
What this clears up (the fundamentals)
- A share card is composed, not conjured — the headline, the big number, the insight line, and the badge are separate fields joined by a deterministic rule. See the parts and the "magic" one-liner stops being magic.
- Verifiable beats vanity — a bare number is a vanity claim; a number plus its receipt (which run, which insight) is verifiable. The engine keeps the receipt attached to the number.
- Accessibility is the same data — the alt text is built from the exact same parts as the visual card, so the screen-reader description and the picture never drift apart.
- One card, every surface — a single composed payload feeds the preview, the share string, the download, and the alt text. Change the source once and every surface updates together.
Where it's used
Invisible infrastructure behind every playable — the result screen every other miatz playground calls to turn its score into something worth posting. It's a miatz build-lab concept playable: play it here to feel why a good result card carries its own proof, then learn to build the compose rule and the signature reveal yourself.
FAQ
What is a "result card"?
The single shareable artifact a playable produces at its result screen — a branded card with a headline, one big number, a supporting line, and an optional badge. This engine composes the strings that card is rendered from.
Why show the "receipts" instead of just a score?
Because a bare score is a vanity claim anyone could type. When the card carries the insight behind the number — which run, which check, which trace — the share is simultaneously marketing and proof. That's the miatz signature move.
What is the alt text for?
It's an accessible description built from the same named parts as the visual card, so screen-reader users get the full result and the picture and its description can never disagree.
How is the share string composed?
It's a deterministic join: "<title> — <score> <label>", then the insight and badge are appended when present. No model call, no randomness — the same input always produces the same card.
Is anything uploaded?
No. Your title, score, and insight are composed into a card entirely in your browser — nothing is transmitted, stored, or logged. Turn off your Wi-Fi and it still works.
Limits
A teaching engine for the composition of a result card — it produces the strings and a live HTML preview, not a rendered PNG or a hosted deep link. The real platform service also renders an on-brand image and a public, no-login replay link; here you're learning the compose rule and the receipts-first doctrine underneath it.
Related
Part of the miatz playgrounds. Explore the rest from the playground catalog.
Bookmark this page (Ctrl+D, or ⌘D on Mac) — it works offline the next time you need it.