Lane
Preset
Custom
Oversight
Zoom 100%
Owners
Steps
Wires
Display
Drop the preset file to import it

How a change gets its lane

The Router guesses the lane from the brief, to pick the Worker’s model. When the change reaches READY, the Classifier rates it twice and sets the lane. It can move up or down from the guess. Migrations, user data, credentials, billing, landing and deleting data always stay Safe.

  1. Size: how much there is to read

    • SUp to 80 lines · 5 files
    • MUp to 400 lines · 20 files
    • LUp to 1,500 lines
    • XLMore than 1,500 lines

    Only code counts. Tests, generated files, lockfiles, snapshots and moved files don’t.

  2. Risk: how much it could break

    • TrivialOnly how things look or where they sit: sizes, colours, class names, images, on-screen text, docs, or moving and reordering existing elements
    • LowTests only, or a small change little code depends on
    • NormalOrdinary logic in a normal part of the app
    • HighSensitive files, widely imported code, data or migrations, or files fixed or reverted in the last 14 days

    Mimosa compares the code before and after, so moving a button inside a component still counts as trivial. New state, handlers, data or conditions don’t.

  3. Lane: where the two ratings meet

    Every XL change is Safe, so it always gets the Gatekeeper.
    RiskSMLXL
    TrivialFastLightStandardSafe
    LowLightLightStandardSafe
    NormalStandardStandardStandardSafe
    HighSafeSafeSafeSafe

  4. What each lane runs

    Time from READY to landed, queue waits included.

    FastShown5–10 min
    Review
    None. The screenshot is the check.
    Merge queue
    Type check and quick root tests
    LightShown10–15 min
    Review
    One reviewer on a light model
    Merge queue
    Only the tests that touch the changed files
    StandardShown20–35 min
    Review
    One standard reviewer
    Merge queue
    Affected tests, then a build of the app
    SafeShown45–90 min
    Review
    Two model families, a security pass and the Gatekeeper’s sign-off
    Merge queue
    Affected tests, or the whole suite when shared code changed, then a build of the app
    • In every lane
    • The Worker runs focused tests and the ready check, not the required checks.
    • Approval never waits for a check run.
    • A landing that breaks main is undone.
    • Under Supervised, M changes and up wait for Your approval after review, and then skip Your check unless they need the running app.

    Times are estimates from Mimosa’s run logs for 3–7 Nov. Today the same span spends about 55 min on checks.