Soundly RunSound familiar?

The AI kept the old rule

Delivery now takes ten days, not five. You decided it on Tuesday. The AI answering customers kept promising five all week.

InsteadWhen a rule changes, the AI changes with it, and queued work is checked.

The video

Video planned52 secondsHow every video is made
The script
The one point
People heard the change; the AI kept the written rule. One rule in the decision record, and work in flight checked again, carries the change to the AI too.
Why a video
Cause and effect: heads nod in a room while replies stamped with the old promise keep flowing out; then the same queue stopped and checked, and the unsent replies corrected by one person’s click.
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘The AI kept the old rule’ on the site’s background, fading straight into the guide with no black.
    On screen
    The AI kept the old rule
  2. The moment0:03-0:10person

    Picture
    The guide in the usual place and framing. Lower third with first name and ‘Soundly Run guide’.
    Voice
    Delivery now takes ten days, not five. You decided it on Tuesday. The AI answering customers kept promising five all week. Rules change in meetings, but the AI that answers customers reads only what is written.
    On screen
    The AI kept promising five all week
  3. The cost0:10-0:17motion

    Picture
    Example tag top left. A meeting room where heads nod at a card reading ‘10 days’. Outside the room, chat replies stamped ‘5 days’ keep flowing to customer dots, and a queue of order cards approved last week rolls on. No other figures.
    Voice
    People heard. The written rule still said five, and work queued last week ran on it too.
    On screen
    Example: People heard. The AI didn’t.
  4. The mechanism0:17-0:26screen

    Picture
    Drawn Needs you screen, Example tag top left, context ‘Hugo’s crew’. Step band on ‘prepare’. Heading ‘Delivery is now 10 days. 32 tasks still say 5.’ Callout 1 on New rule. Callout 2 on AI that quotes it: ‘4 AI helpers, now reading 10 days from the decision record’.
    Voice
    Hugo decides the change once, in the decision record. Every AI helper reads the rule from there, not from its own copy.
    On screen
    Example: one rule, read from the decision record
  5. The mechanism0:26-0:35screen

    Picture
    Same screen, step band ‘review’. Callout 3 on Waiting replies: ‘23 drafted with 5 days, held before sending’. Cursor moves to Approved orders: ‘9 confirmed at 5 days before the change’, then the two drafted rows: ‘All 23 now say 10 days’ and ‘Kept at 5 days unless you change them’.
    Voice
    Then the work already in flight is checked again. A helper redrafts the 23 waiting replies with ten days. The 9 orders already confirmed are drafted to stay at five days, unless Hugo changes them.
    On screen
    Example: 32 tasks checked again
  6. The decision0:35-0:42person and screen

    Picture
    Step band on ‘decide’. ‘Send the 23 replies’, ‘Change’ and ‘Pass’ all visible. Cursor clicks ‘Send the 23 replies’, held two seconds. Rows update: ‘23 replies sent with 10 days’; ‘9 orders kept at 5 days, as confirmed’. Guide in picture-in-picture.
    Voice
    Hugo owns the rule, so Hugo decides: send the 23 replies, change them, or pass.
    On screen
    Sent. 23 replies say 10 days; 9 orders keep 5.
  7. The difference0:42-0:48person

    Picture
    The guide, same place and framing as the moment, so it reads as a return.
    Voice
    Nobody hunts down every copy of the old rule by hand. The helper drafts; Hugo decides. It does not watch, score or replace anyone.
    On screen
    When a rule changes, the AI changes with it, and queued work is checked.
  8. Outro0:48-0:52sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    The AI kept the old rule

On screen as proof

  • Needs you screen tagged Example: new rule beside ‘4 AI helpers, now reading 10 days from the decision record’
  • Example figures ‘23 drafted with 5 days’ and ‘9 confirmed at 5 days’ only inside the tagged screen and the tagged cost scene
  • Drafted for the 9 orders: ‘Kept at 5 days unless you change them’
  • Send, Change and Pass all visible; click held two seconds

Before and after

Before
Said aloud, so it feels told; the AI reads only what is written
After
The rule changes in the decision record when it is decided
Before
Each AI got its own copy of the rules at setup (configuration drift)
After
Every AI reads the one rule in the decision record
Before
Work approved under the old rule still runs as approved
After
Queued work is checked again against the new rule

How it works

A changed decision reaches the AI through the decision record, and work in flight is checked again.

  1. A change is decided once, in the decision record; every AI helper reads it there.
  2. When a rule or someone's authority changes, every waiting and approved task is checked again.
  3. The rule's owner decides each task that no longer fits: correct, hold or let stand.
Needs youExample

Hugo's crew

Delivery is now 10 days. 32 tasks still say 5.

New rule
Standard delivery 10 working days, from Tue 20 Oct
AI that quotes it
4 AI helpers, now reading 10 days from the decision record
Waiting replies
23 drafted with 5 days, held before sending
Approved orders
9 confirmed at 5 days before the change
Replies, redrafted
All 23 now say 10 days
Orders, drafted
Kept at 5 days unless you change them

Source: decision record and queued work, 20 Oct

Send the 23 repliesChangePass

Built to work in the email, calendar, chat, finance and sales tools you already use.

What it never does

  • Acts alone only inside limits a person sets; asks first for anything else.
  • Reaches only what its job needs.
  • Never watches, scores or replaces anyone.