Accord

Definition

The Knight-facing portal at /accord where pending Handshakes are reviewed and accepted or refused. The Accord is a UI surface, not a state — rows enter it by virtue of being in Pending_Handshake with the current user as assignee, and leave it the moment they transition out.

Avoid: inbox (reserved for the API route /api/v1/inbox), queue.

Role

The Accord is the only surface from which a Handshake can be performed. It is the consent-first gate of the system: the Knight reads the proposal, sees the source excerpt, and explicitly accepts or refuses. The Knight never sees a Shrubbery before it reaches Pending_Handshake, so the Accord is also the Knight's first-contact surface for any new commitment.

The route lists rows newest-first. Each card shows objective, deadline, source badge (Smart Paste / URL Drop / Manual / Inbox), source excerpt where applicable, and an Accept/Refuse pair. Cards do not expand inline — the affordances are top-level.

Lifecycle

Not a stateful concept of its own. Card presence on the Accord is derived from the parent Shrubbery's state:

• Pending_Handshake — visible on the Accord.
• Any other status (Active, Refused, Completed, Renegotiated → Pending_Handshake again) — leaves or re-enters the Accord accordingly.

Renegotiated rows are still Pending_Handshake; they re-appear in the Accord with a "Renegotiated" indicator and a wording/deadline diff.

Related guides

• Accord Lifecycle
• Handshake Flow
• Renegotiation Flow

Last updated: 17 May 2026