Pixel Character System
To close: Write an Outcome: brief delivered, no artist round; the idea continued as design c47/c57 Pixel Pawns. · Move design-brief.md into the cycle folder, or link it from the Outcome. · Move it from CYCLES.md to HISTORY.md.
last activity Apr 23
The things Qpoint tracks, like agents, models, tool servers and API keys, all look like "some machine" in tables and diagrams, so people mix them up.
A first-pass brief gives a pixel artist one character for each tracked thing, with states like new, sensitive or exposed. No artist feedback or sketches followed.
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
A brief names twelve characters, from Session to Power User, each with the one question it answers.
A brief for an artist, no art yet · came from Mark Parson
- A month later the design site wrote a fresh brief for eleven pixel pawns, then built their states. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
A brief names twelve characters, from Session to Power User, each with the one question it answers.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Started the character system
The record names no one; the cycle and its brief were committed by Mark Parson (git), so the credit is matched from authorship.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 0 decisions · 0 key-change entries · 593 words · 0 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c11 →