Boards

A board is where creatives go to be looked at: a durable review canvas of rendered cards, sorted into sections, with keep/discard, comments, and a chat that edits. Runs produce, boards hold — one board can collect the results of many runs, so a standing "Q3 winners" board keeps aggregating while campaigns come and go.

Boards are reached through their collection, and every run gets one automatically. You can also create one empty (from the API, CLI braaand boards create, or an agent) and fill it by hand — add any creative to any board, no run required.

A creative reaches a board by going through a Board node. Producing it isn't enough: a run whose graph has no Board node makes creatives you review on the canvas, and a Route path wired to nothing leaves its creatives off the board rather than dropping them in unsorted. That is what keeps a board an edited selection instead of a dump of everything the run touched.

Reviewing

A scored run arrives pre-sorted — Approved for 75 and up, Needs review for the rest, biggest score first within a section. Cards fill in live as the run builds. Each card shows the render, its score, and a one-line critique.

• Keep or discard. Hover a card: ✓ keeps (ring), ⃠ discards (dims). The header keeps count. Kept creatives are the ones you deliver.
• Iterate by talking. The chat panel takes plain direction — "make the top one punchier", "remove variant 3", "try #2 aimed at parents" — and the grid updates as it works.
• Target specific cards. Select one or more (the amber checkbox) and your next message applies to exactly those. Clear the selection to address the whole board.
• Open any card in the editor for hand fine-tuning; it opens in a new tab.

Sections mean things

Beyond visual grouping, a section can confer a status: drop a card into a section set to confer approved and the creative is approved, wherever else it appears. Color and meaning are independent — a red section named "Hot" can still confer approved. Pipelines use the same mechanism: a Board node targeting a named section applies that section's meaning to everything it delivers.

Sharing for sign-off

Every board can mint a share link — a public, read-only review page that needs no braaand account. Hand it to whoever signs off; they see the current state of the board (renders update as you iterate, no re-send needed). The link authorizes exactly that board's renders and nothing else, and you can revoke it any time from the board's Share button. Runs started over the API or MCP return a shareUrl up front, so an external tool can pass the review link straight along.