Lite close

A lighter close for two kinds of work: a live demo, and docs, research or UX-mockup work. You turn it on for a ticket.

The Cockpit calls it Lite. Under the hood the ticket flag is still demo: true and the terminal command is still tkt demo, and canon's reports still say "demo mode". They all mean the same thing.

What changes

Turn it on

In the Cockpit, either of these:

  1. New ticket: choose the Lite option when you create it.
The New Ticket form with the Lite option selected, outlined in purple, and a tooltip that reads Lite close — for live demos or docs/research/UX-mockup work: sprint complete runs security-review + the binding evaluator only (forced Haiku), skipping the advisory reviewer + rest of wrapup. Never drops below the evaluator.
Lite selected on a new ticket. The tooltip says what it changes.
  1. Ticket window: use the Lite switch in the row of chips at the top, after Ready. It is green when on, and it locks once the ticket is closed. Hover over it for what it changes.
The top of a ticket window for a Todo ticket in progress: the chip row reads Status In Progress, Type Feature, Priority P2, Tags + Add tag, Age 3m ago and Ready unchecked items, and the Lite switch after it is on, in green, with a tooltip below it that reads Lite close — for live demos or docs/research/UX-mockup work: sprint complete runs security-review + the binding evaluator only (forced Haiku), skipping the advisory reviewer + rest of wrapup. Never drops below the evaluator.
The Lite switch in the chip row, turned on, with its tooltip.
Prefer the terminal?

Run tkt demo with the ticket id:

tkt demo t-1234 on tkt demo t-1234 off tkt demo t-1234

The last one prints the current state.

A Lite ticket's card on the board carries a LITE badge: amber capitals with an outline, beside the type label.

A board with a ticket card in the Open column for Add timestamp to each Todo, with a FEATURE label, an outlined amber LITE badge beside it and a Start button. The Done column holds a card without a badge.
A Lite ticket's card on the board.

The model

The evaluator runs on Haiku. A Gate model set on the ticket beats that. See Model tiers.

Where it does not apply

Headless and CI runs never skip a gate for it. sprint-headless ignores the flag. sprint-headless-eval runs every gate and only defaults its evaluator to Haiku. See Headless CI.

It is your call

Canon does not check the flag against what the ticket changed. It is meant for docs and demos, but it is honoured on a ticket that changes code too, so use it for the work it is meant for.

Maintenance tickets (those with a skills: line) follow what actually changed: a run whose whole output is Markdown reports takes the light close, and one that changes any other file gets the full close.

What it looks like

These rows are from the Wrapup Gates table of a real Lite close in this repo, .tickets/t-633f/acceptance.md. The security-review row, which reads ran, is left out.

| code-simplifier | skipped | demo mode | | code-reviewer | skipped | demo mode | | reviewer | skipped | demo mode (advisory reviewer not dispatched) | | repo-check | skipped | demo mode | | doc-audit | skipped | demo mode | | eval | ran | verdict: pass — `eval-report.md` written, run-id 1791060527-18217 (model: haiku — demo mode (fallback: Plan)) |

For the full close, see Sprint and gates.