The board

Agents ask the board with two tools:

• HireAgent proposes a seat that reports to the agent. Nothing is hired until you approve it; approval hires it exactly as proposed.
• ProposeStrategy is for the head of the company: its plan toward the goal, which it proposes before splitting the work into issues and hires. The plan shows as a Strategy line in the Inbox and on its issue; Approve strategy or Send back answers it, and the head is woken with your answer.
• RequestBoardApproval asks you to approve another decision.

Your decision is posted on the issue it came from, and the agent that asked wakes to read it.

The Inbox

The Inbox reads like a mail list: one list, newest first, under Today, Yesterday, the weekday, then the date. Each line shows an unread dot, the kind, who it is from, a subject with a one-line preview, the issue and the time. Unread lines are heavier; All, Unread and Needs answer filter the list, and Mark all read clears the dots.

• Needs answer: decisions, strategies, hires, budgets, tool approvals, merges and issues assigned to you. Their two answers (Approve or Reject, Merge or Reject, Allow or Deny, Mark done or Reply) show when you point at the line or move to it. An answered item stays in the list, read, with how it ended: Approved, Rejected, Merged, Sent back.
• News: failed runs, and runs interrupted when Synoec closed. Those are not failures: the runs one quit stopped are a single line, and Run again in its detail picks the work back up.

Click a line, or move to it with Up and Down and press Enter, to open its detail over the page and mark it read: the full text, the whole diff, the command a tool would run, or spend against the limit, with the answers and a note for the agent. Esc or a click outside closes it. Mark unread on a line, or U, marks it unread again. Read marks are kept with the company.

The sidebar’s Inbox count and Needs you on the Dashboard count only what needs an answer. Needs you shows the same asks as cards.

A merge’s detail shows the diff. Reject sends the work back: the changes stay on the company branch, the issues in review go back to todo with your note, and their agents wake to revise; the card returns once an agent has run again. Merge commits the agents’ work on the branch and merges it into the project’s checkout the way a subthread is merged: a dirty checkout or a conflict refuses the merge and leaves nothing half-merged. A merge is recorded in Activity and noted on every issue in review, and agents’ briefs say what still waits for a merge, so they never ask about work already merged. Activity lists who did what, newest first.