Triage

Triage sits above Archive in the rail, with a count. The page lists what the board last pulled, newest collected first: a title, the post's own words, which platform it came from, and three things you can do with it — read the summary, open the original, or dismiss it.

Free to invited Cloud accounts on an Engineering board while it is a preview. On a Marketing board, and on an account that is signed out or not yet invited, there is no rail row and akb triage fetch refuses.

A triage item is not a card

Triage is deliberately outside todo/. An item is never scheduled, never ranked, never counted in your board numbers, and never becomes a card on its own — it is somebody else's sentence, waiting for you to decide whether there is work in it. Cards are what you have decided to build.

That means triage needs looking at, the way a mailbox does. Dismissing an item is permanent: its file goes, its id is written to docs/kanban/triage/handled.md, and no later pull brings it back. There is no undo, and that is the point — a list you can never empty is one you stop opening.

Connect a source

Two settings, both filled in by hand for now.

The endpoint goes in your board's docs/kanban/config.md, as one more line beside the settings already there:

- **Triage endpoint** — https://signals.example.com/v1/pull

The token goes in docs/kanban/.env, where the board keeps every key. It is never shown on a screen, written to a log, or repeated in an error:

TRIAGE_ENDPOINT_TOKEN=…

docs/kanban/.env is kept out of git by the board's own .gitignore.

These replaced the earlier Signal endpoint and SIGNAL_ENDPOINT_TOKEN, which are no longer read, and the akb signals command, which is gone. Rename them in your own config.md and .env, and update any script or recurring card that still runs the old command — nothing is rewritten for you.

What the endpoint returns

The board sends GET <your endpoint> with Authorization: Bearer <your token> and expects JSON shaped like this:

{
  "signals": [
    {
      "source_id": "t3_1abcdef",
      "title": "Three of us run Claude Code and the conventions keep getting reverted",
      "summary": "We each have Claude Code open on the same repo…",
      "platform": "Reddit",
      "url": "https://www.reddit.com/r/ClaudeAI/comments/1abcdef/",
      "collected_at": "2026-09-06T21:40:00Z"
    }
  ]
}

All six fields are required, and a signal missing any of them is not imported — the pull counts it as a failure and names what was missing. collected_at is when the data platform collected the post, not when your board pulled it; the board records the import time itself.

• source_id is the signal's identity. The board dedupes on it, against the inbox, the handled record, and the rest of the same batch — so the same post sent on ten pulls is one file.
• platform is free text. The board recognises none of them: it draws a mark for the ones it knows and a neutral one for everything else, which is what lets any source be connected.
• There is no paging and no ceiling. What the endpoint sends is what the board takes.

Turning what a platform actually returns into this shape is yours to write — that converter is the reason the board never has to know a platform.

Pull

akb triage fetch

It reports what it did — Added 12 items, skipped 3, failed 1. — and explains each failure on its own line. A request that fails, an answer it cannot read, and a setting still to be filled in all write nothing at all: triage is left exactly as it was.

The first successful pull makes docs/kanban/triage/inbox/ and seeds a recurring card, Fetch triage items, in todo/recurring/. Give that card a cadence and the board pulls on its own; leave it without one and nothing runs until you ask. Delete the card if you don't want the job — nothing puts it back.

Put something in yourself

The endpoint is not the only way in. Add to triage on the page takes a pasted link, some typed text, or a dropped file, and from a terminal:

akb triage add --title "What it is" --text "Its own words." --source "where it came from"

--file <path> takes the body from a file when it is longer than a line or two. Neither needs an endpoint or a Cloud account. An item triage already holds is refused rather than doubled.

This is also where the board's own Proposer writes: with it switched on, every card you archive is reflected on and what should follow it lands here, carrying the card that prompted it. See Agents.