ShrubberyDocs
Sign in

Renegotiated (audit event)

Definition

The audit event emitted when a Lead makes a substantive edit to an Active Shrubbery, reverting it to Pending_Handshake and requiring a fresh Handshake. Renegotiated is an event type on the audit trail, not a row status.

Avoid: reopened, reverted, re-sent. Do not confuse with Edited.

Role

A Renegotiation is the safety valve for when a commitment's terms need to change after the Knight has already agreed. Rather than silently mutating an Active commitment, Shrubbery reverts the row to Pending_Handshake and demands a fresh consent moment — the Knight is never bound to terms they did not accept.

Substantive fields that trigger a Renegotiation: the objective text or the deadline. Non-substantive edits (wording tweaks, metadata) emit Edited instead and keep the row Active.

The row re-enters the Accord with a "Renegotiated" indicator and a diff showing what changed. The Knight can accept the new terms or refuse. While the row is in Pending_Handshake post-renegotiation, it temporarily exits the Flow Score denominator until the Knight re-Handshakes.

Lifecycle

Not a status — Renegotiated is an audit event. The row's status after this event is Pending_Handshake.

  • Trigger: Lead edits objective or deadline on an Active row.
  • Effect: row status → Pending_Handshake; renegotiated event written to audit trail.
  • Resolution: Knight re-Handshakes → Active; or Knight refuses → Refused.

Last updated: 22 June 2026