How work flows

One sample build, start to finish. Press Next to walk it through.

Sample: fix the sorter for the call

Example
  1. 1

    You ask

    Julian, in the project chat

    "Show the training groups on the call."

  2. 2

    Build

    Builder chat, on Sonnet

    Builds the sorter on a private page with practice data. Nothing is pushed.

  3. 3

    Review

    Fable reviewer, never builds

    Finds 2 problems: names sit next to dollar totals, and inactive people are included.

  4. 4

    Fix

    Builder chat

    Adds a Presenting view with no dollars and filters to active people. The reviewer checks only what changed.

  5. 5

    Your yes

    Julian

    You see the result with a verdict: Ready. Under 100 credits and private, so it goes ahead and you get a report.

  6. 6

    Ship

    Only on your typed yes

    Anything live, pushed to main, sent or bought waits for your typed yes. MP gives the merge on the CRM.

Lessons log

Example

Every review finding lands here. The same mistake twice becomes a proposed rule for you to accept or reject.

FoundWhereRule that catches itTimes
Names next to dollar totalsSorterAny page shown on a call has a Presenting view with no dollars1
Page states a rule the tool does not followCall Pack, sorterCheck every stated rule against the tool that applies it1
Planned features written as workingCall PackStatus pages split "Working today" from "Coming"1
Text under 14 pxCall Pack, sorterBuilder checks sizes before sending for review2, rule proposed

Daily review report

Example numbers
7builds reviewed
12findings caught
1repeat mistake
1rule proposed
38credits used

What stays the same