Give it
The outcome
Stated the way you would accept it, not the way you would prompt it.
Manifest 02 · the work, not the org chart
Jobs, not departments.
Software sold by department ends up owned by nobody. This is the other list: the specific pieces of work people hand over, how long each one tends to take, and the thing that has to be true before it counts as done.
Read the third column
T+00:00Standing work
| The job | Typical horizon | Done means |
|---|---|---|
| Month-end reconciliation | 4 – 30 h | Every exception either cleared or written up with the document that caused it, and the ledger balances. |
| Pipeline hygiene | Standing | No stage older than its own SLA, every stale opportunity chased once in writing, the owner told what changed. |
| Tier-one support | Standing | The queue is answered inside the hour at 03:00 as well as at 15:00, and anything it cannot close is escalated with the history attached. |
| Migration off a deprecated API | 2 – 10 d | Every call site moved, the test suite green, the diff reviewable by a person who was not watching. |
| Competitive and market sweep | 3 – 14 d | A decision memo with each claim carrying the page it came from, and the sources it could not reach named. |
| Candidate screening | Standing | Every application read against the written bar, rejections sent, the shortlist annotated with the evidence. |
| Contract review | 1 – 6 h | Non-standard clauses flagged against your own playbook, with the redline drafted and nothing signed. |
| Data clean-up | 6 h – 5 d | Duplicates merged, formats normalised, a reversible log of every row it touched. |
| Weekly reporting | Standing | The numbers pulled from the systems of record rather than retyped, and the commentary written by something that read the numbers. |
| Onboarding an account | 2 – 8 d | Environment stood up, integrations connected, first workflow running in front of the customer. |
Horizons are the shape of these jobs, not a service level. What a run actually takes depends on your data, your systems and how much of the work needs a person to say yes.
T+11:26Reach
It has to touch
the systems the
work lives in.
Over three thousand tools are reachable. The ones that matter are the ones already holding your data.
| Layer | Where the work already is |
|---|---|
| Where people talk | Chat, mail, calendars, ticketing |
| Where records live | CRM, ERP, HR systems, finance |
| Where code lives | Repositories, CI, issue trackers, cloud consoles |
| Where documents live | Drives, wikis, contract stores, data rooms |
| Where the numbers live | Warehouses, dashboards, spreadsheets |
| The open web | Its own browser, with a session it keeps |
T+01:04:18What you actually hand over
A brief, a
boundary, and
a way to check.
The instruction that works is the one you would give a competent new joiner: what the outcome is, what it must not touch, where the truth lives, and how you will know it went well. Ninja keeps that brief for the length of the run and holds itself to it.
Everything it does is written down as it happens. A run you did not watch is still a run you can read afterwards, step by step, with the inputs it used at each point.
Give it
The boundary
Systems it may write to, money it may not move, people it may not mail.
Give it
The source of truth
Which system wins when two of them disagree.
Give it
The check
The test, the reconciliation, the person who signs.