ShrubberyDocs
Sign in

Renegotiation Flow

Overview

A Renegotiation happens when a Lead needs to change the objective or deadline of a Shrubbery that is already Active — after the Knight has already Handshaked. Rather than silently mutating a commitment the Knight agreed to, Shrubbery reverts the row to Pending_Handshake and demands a fresh consent moment. The Knight sees what changed and can accept the new terms or refuse.

Actors

  • Lead — initiates by editing a substantive field on an Active row in the Detail Sheet.
  • Knight — receives the re-opened row in the Accord and makes the new Handshake decision.
  • Squire — not involved. Renegotiation is a human-to-human flow.

Flow

  1. Lead opens the Detail Sheet for an Active Shrubbery and edits the objective or deadline.
  2. System detects a substantive change → emits a renegotiated audit event → transitions the row: Active → Pending_Handshake. The row temporarily exits the Flow Score denominator.
  3. Knight sees the row re-appear in the Accord with a "Renegotiated" indicator and a diff showing the old and new values.
  4. Knight accepts — Pending_Handshake → Active. Row re-enters the Flow Score denominator. The new deadline is now the enforceable one.
  5. Knight refuses — Pending_Handshake → Refused. Row enters Ghost Rate numerator. Terminal.

Edge cases

  • Non-substantive edits — editing metadata or wording that does not change the objective or deadline emits Edited instead and leaves the row Active. No Accord re-entry; Knight is not notified.
  • Multiple renegotiations — a Lead can renegotiate an Active row multiple times. Each cycle is a distinct renegotiated event in the Audit Trail and a fresh Accord entry for the Knight.
  • Renegotiation while previous round is still Pending — cannot happen; a row that is Pending_Handshake is not editable without triggering another renegotiation cycle. Only Active rows can be renegotiated.
  • CFS impact — while the row is in Pending_Handshake post-renegotiation, it is not in the Flow Score denominator. It re-enters the denominator the moment the Knight re-Handshakes with Active. The original deadline does not carry over; the new deadline governs on-time scoring.
  • Knight refuses the re-negotiated terms — the refusal counts toward Ghost Rate just like any other Pending_Handshake → Refused transition. The Lead may create a new Shrubbery with revised terms if they still need the commitment tracked.

Last updated: 22 June 2026