The Brain / Capabilities / Move and assign

ACT

The move proposed, evidence beside it.
A person confirms.

The work moved on Thursday and the card moved on Monday; here the move arrives proposed, with the event that justifies it, for a person to confirm.

Book a demo See it running first

What it looks like on a Tuesday

Three moves, one of them refused

09:05

Three cards, three lines of evidence

A blocking comment answered in a client reply, a dependent document signed, and eleven days of silence past a due date.

09:06 · a person confirms

She accepts two, reasons attached

The moves run on her click, and the sentence that justified each is written beside the card.

09:07 · a person declines

The eleven-day card is declined

It is waiting on a client, not stalled; her one-line decline is kept and shapes the next proposal.

How it works

Three mechanisms

01

Each app reports its own change

A move is proposed because something occurred, not because a nightly job noticed a date going past.

02

The reason is written where the change is

State, owner and the justifying sentence go back together into the system that owns the card.

03

Assignment stops for a person

Anything that sends, deletes, shares or reassigns stops for a human yes, given from a screen where a person clicked.

What it is not

Three honest limits

It does not decide priority for you.

It cannot move work in a system that emits nothing.

It does not reorganise people; an owner is one task's suggestion.

Updated 15 September 2026 · WE_AINA

Book a Diagnostic Sprint

Bring one board and a real week, and confirm the moves.

Book a Diagnostic Sprint