Knight
Definition
The accepter of a commitment. The employee or team member who receives a proposed Shrubbery from a Lead and decides whether to perform the Handshake. The Knight is always the assignee on a Shrubbery row.
Avoid: employee, assignee-user, recipient, target.
Role
The Knight is the consent-bearing actor in the system. Without a Knight's Handshake, a Shrubbery does not exist as a load-bearing commitment — it is a proposal that scores nothing. Every reliability measurement (Flow Score, Ghost Rate, completion timing) rolls up against the Knight's row-level decisions: accept, refuse, deliver, miss.
The Knight's surfaces are the Accord (/accord, where they Handshake) and their own Dossier (where their reliability history surfaces to themselves and to Leads they have worked with). The Knight does not own a CFS — the team-level CFS is the Lead's metric — but their individual Flow Score on their accepted commitments is the substrate from which CFS is built.
A Knight may also be a Lead on different rows, and in fact most users wear both hats simultaneously. The role labels are per-row, not per-user.
Lifecycle
Not a stateful concept — the Knight is a role attribution on each Shrubbery row, not an entity with states. Per-row, the Knight's interactions drive these transitions:
Pending_Handshake→Active— Knight accepts via the Accord.Pending_Handshake→Refused— Knight refuses via the Accord.Active→Completed— Knight marks the work done.Active→Pending_Handshake— Lead Renegotiated; Knight must re-Handshake.
Related guides
Last updated: 17 May 2026