// Set & Signal · Post generator

The code, ready to post.

A standing rotation built from the canon itself — carousels that walk the code and the ladder in order, single cards for one rule at a time, manifesto lines for the slower posts, and the life-prompt questions that ask something back. Every caption is written out too, because the image is only half a post.
← the brand kit · the print pieces →

Build the queue

Copy comes from brand.json at runtime — the same canon the culture page renders from. Edit a rule there and it changes here, on the site, and in every post you cut afterwards. Nothing on this page invents a rule.

—
How to run it. Daily is fine — the volume of events supports it — but every post earns its place. Two engines carry the feed: the event (announcement, day-of, recap) and the code (the carousels below). Carousels are the backbone; a sequence earns a second look and a save where a single card doesn't. The single rule cards, manifesto lines and life prompts are the quiet days between them — not filler, and never a repost to keep a streak alive.

Pin the code carousel to the top of the profile: it's the first thing a new follower should read. Run the ladder whenever someone actually graduates a rung, so the claim has a face attached. Slot a life prompt when there's nothing to announce — it's a real question, answerable in a line, and it isn't about us.

Rotate the stock as well as the post. Four stocks × two formats is a lot of variety out of one canon, and it's the cheapest way to keep a daily feed from going flat without touching the system.

Carousels download as their own zip in slide order; the big zip carries every image plus a captions.txt, one caption per post.
Stocks. The four options are the poster system's own — taken from brand.json § poster_standards, so a kraft post and a kraft flyer are the same colours rather than an approximation. Signal is the default default for screens; Night (charcoal and cream) is the cinematic layer; Kraft is the artifact family — same print DNA as the envelope and the tickets, and its stamp-rust accent is locked by the standard, so nothing here offers to recolour it. Rotating stock is the cheapest way to keep a feed from going flat without touching the system.
A note on the word. brand.json bans "engagement," and principle 04 goes further — "We do not want your engagement. We want your presence." So nothing here optimises for a metric. What these formats do is give people something worth answering, saving, or bringing someone to. That tends to travel further anyway, and it doesn't cost you the voice.
A night's pack. Drop a poster project (the .json or .zip the poster builder saves) and the announcement carousel, the story card, the day-of card and the recap frame come off that one record — so the print piece and the feed can't disagree about the lineup. The poster art rides along inside the project file. Layout, tier styling and the serial / artist's-proof numbering stay in the poster builder; this only receives the finished poster and the facts of the night.