init

Take over a repo that already exists — guest or successor read from the ground, the audit before any touch, findings as one classified list, fixes in batches…

Bring work in from anywhere — a tracker, a spreadsheet, an export, a paste: mode declared once, mapping shown first, items created unassigned.

Call another craft to look — a request with a status and an age.

Ask the audience — personas built and consulted with the signal pyramid kept honest.

What work cost — measured at the run, summed, with the leaks named.

Run one decision loop: frame, search, compare, choose, check, record.

Cut a feature into tasks — each workable from itself, with the seams named.

Grow the roster — a role born from a need, hired with its bars and budget.

Move a project between machines or runtimes — the repository travels, sessions do not.

Park or offboard a role — archived with a note, never deleted.

The product as a map: the moves through it, in its own words — not the file tree.

A recurring job becomes an automation with a real trigger, or an honest manual one.