← All clips · Uncategorized

Sign and countersign a contract

PASSING GATE Venue ManagerGuest 15 steps · 23.2s · recorded Aug 25, 9:10 PM · eadc380

Viewing an archived run (20260826T040959Z-eadc380). Back to the current run.

Speed

Source: e2e/scenarios/test_wf_sign_and_countersign_a_contract.py:1 · run 20260826T040959Z-eadc380 · steps carry start_ms/end_ms offsets into the video

Steps

  1. The list is step 1 of the manual and the gate scenario never opens it — it reaches the contract by id. This is also where a drafted contract nobody locked would have to be noticed, which is stall 1.

  2. `require_staff`. A manager reads the redline history so the agreement is not a black box to the person who has to run the night.

  3. Reading and executing are different powers, enforced at the route and not by hiding a button — a hidden button is a decoration, and this call skips the page entirely.

  4. 'This signing link has expired — contact the venue.' Told to somebody whose only relationship with the venue is this email. Checked while the signature is still owed, which is when it matters: once they have signed, the same page keeps showing their status even on a dead token — the receipt outliving the link is the right call and is asserted below.

  5. Recorded as the target. The plan this raised is the fix; this assertion turns green when it ships.

  6. Signed out on purpose: the single-use token authorises this page, not a session.

  7. The typed name is checked against the legal name captured at intake — a signature is not a free-text box.

  8. The manual's step 7 — 'check where the agreement stands without pestering anyone'. A waiting party with a self-serve answer generates no chase traffic, which is the cheapest receipt there is.

Notes

Sign in to leave a timestamped review note. Notes land in the same review backlog as in-page annotations.

  1. No notes on this clip yet.
Run history (6)