Your own team

Who acts at a step when it isn't a member of a Pool? Your own team. AI delivers by default, and staff are the person rung after your own review in who does the step: people you employ, at the steps you keep in house, before you open a Pool.

A role word with no pool is a staff role. With human: 'always' on Translation, the person at the line is yours: every job waits for them, and they approve it or send it back in their own session. dev serves them a portal at /people:

npx services.dev dev

lingua
  translation  A person approves every job before delivery.
  site         http://localhost:8787/translation
  api          POST http://localhost:8787/jobs {"service":"translation"}
  key          sk_test_7Hq2 · a call with no key uses it, on localhost only
  mcp          http://localhost:8787/mcp · stdio: npx services.dev mcp
  cli          npx services.dev translation k=v …
  sdk          connect({ origin: 'http://localhost:8787' }).translation.order(input)
  docs         http://localhost:8787/llms.txt
  buyers       http://localhost:8787/portal
  people       http://localhost:8787/people
  you          http://localhost:8787/console
  AI and money are simulated until you wire them. $0.42 a call is an example.

Staff act the way any person at a step does. Approving commits the step through the gate; sending back hands the job to the AI with a note, and the AI redoes it:

npx services.dev approve job_7Hq2

job_7Hq2 · delivered · document.fr-CA.pdf · $49.00 charged
  record  draft · ai | review · ai · pass | approve · person
  ledger  +$49.00 · AI $0.84 · you $48.16
  next    npx services.dev accept job_7Hq2

npx services.dev send-back job_7Hq2 "Keep the defined terms in English."

job_7Hq2 · waiting · on approval · $49.00 charged
  record  draft · ai | review · ai · pass | approve · person | sent back · buyer | draft · ai · redo | review · ai · pass
  next    npx services.dev approve job_7Hq2

A key or an agent never acts for them. Each act is a person's own, like a member's, as what a person can do lists.

The owner console lists every Task still open across your Pools, with held advice to adopt named as such, beside every job, its ledger and the rules version it pinned. Staff work from it:

A Pool's fill ladder ends on a staff rung: a Task no member claims in twelve hours is offered to your staff roles that hold its credential. A rung never offers a reserved act to someone who doesn't hold it, and fill_bypasses_reserved fails a Pool whose staff rung would.

You invite a teammate by email from the owner console. They sign in with their own session, hold the staff roles you give them, and work from their role's inbox: a query over the open Tasks for that role, with no Pool behind it. Every act they take is on the record under their own name.

A staff role your custom roles allow to hold acts in an incident after your files and your coding agent: who can act.