Reconvene & the paper trail
Real decisions do not end when the memo lands — conditions change, results come in, and the call has to be revisited. A finished board is not continued; it is reconvened, and the chain of rounds becomes the decision’s paper trail.
Why not just keep chatting?#
A delivered memo is a commitment, not a message in a thread.
When a board terminates, it has delivered a call: a verdict, a confidence level, the conditions that would flip it, and the strongest dissent. Appending “one more message” to that board would quietly mutate a delivered decision — you would lose what the board actually said at the time it said it.
Reconvening keeps the record honest. Round N stays exactly as delivered; Round N+1 is a new linked session that opens from the delivered call plus what changed since.
How a reconvene runs#
Round N+1 re-briefs before it re-argues.
- Open from the call. The new round starts with Round N’s verdict, its flip conditions, and its dissent on the table — nothing is re-litigated from scratch.
- State what changed. You tell the board what is different: a result came in, a competitor moved, a number shifted, a deadline passed.
- Re-brief and run. The change re-briefs the board — the same or an adjusted bench — and the round runs to its own memo, linked to its parent.
The paper trail#
A decision's history, readable end to end.
Because each round is its own session with its own memo, a decision you revisit three times leaves four linked records: the original call and every revision, each stamped with what was known and what changed. That is a paper trail no chat thread produces — you can audit not just what was decided but why it moved.
- Each round’s memo is preserved exactly as delivered.
- Rounds link parent to child, so the chain reads in order.
- Outcomes you record later attach to the round that made the call — the board learns from how its calls played out.
Where you reconvene from#
Every surface that shows a delivered call can reopen it.
- The memo page — reconvene directly from the delivered verdict.
- The dashboard — decided sessions carry a reconvene action on their cards.
- The API and MCP — the
synthboard.session.reconvenetool opens Round N+1 headlessly; asession.continuecall against a current-engine board redirects here by design. See the changelog for the wire contract.
Grounded rounds compound#
Reconvening works with memory, not instead of it.
When a round runs grounded, what it learns writes back to your World Model. By the time you reconvene, the board already knows the context the last round established — so Round N+1 spends its effort on what changed, not on catching up.