The whole system

Describe the work in one Service({...}). Place people where you want them; by default there are none, and AI delivers every job. Sell it everywhere: the file becomes your API, CLI, MCP server, SDK, site, docs and an app for everyone in the job.

Translation, grown: a sworn translator signs, the registry files it, and a renewal date outlives the job. Each comment names the object a key creates:

export default Service({ // Service
  name: 'Translation',
  input: { document: 'file', to: 'language', client: 'party' }, // Parties
  output: { document: 'file', filing: 'text' },
  rules: rules(), // Rules: sign is reserved
  roles: { translator: { pool: translators(), pay: 30 } }, // Pool, and its Tasks
  deliver: { // Steps, each committed by the Gate
    translate: 'ai',
    harden: { review: 'adversarial', lenses: ['meaning', 'terms'] },
    sign: { by: 'translator', stamp: true }, // Task: a member signs
    file: { submit: 'https://registry.example.test/filings', receipt: 'filing' },
  },
  subject: { kind: 'filing', key: 'filing' }, // Subject
  clocks: { renewal: { due: '1y after file', owner: 'buyer', lives_on: 'subject' } }, // Clock
  price: { usd: 89, release: 'file' }, // Money: charged on the receipt
})

Fourteen lines, and every object on the map is in them or made from them: each order is a Job with its Record, the Surfaces and apps are generated, and the Brand is the one file beside it.

One business, many brands. brand.ts renames the core in the business's words (a job is a matter, a member a signer), and several brands can sell the same Services from one Pool:

npx services.dev check

brand.ts · 10 lines · legal · api.lawyer · words job → matter, subject → asset, task → review, member → signer, pool → network, end → outcome

Every doer proposes, and the gate commits. AI, a person, your code and another Service reach the record the same way. Each one proposes, and the gate checks the proposal before it writes. An AI draft and a licensed signature carry the same kind of evidence, and a key that tries a person's act is refused the same way every time.

Every surface renders one contract. The API, the CLI, the MCP server, the SDK, the site, the docs and the apps are renderings of the same registries. No surface renames anything. Brand.words is the one renaming, and you declare it.

Every Service states its price, and every charge waits for the fact it names: delivery, acceptance, a receipt or a verified outcome. When it releases, one ledger splits it, and the buyer, you and each member read the same lines:

you = charge − tax − processing − AI − pay − pass-through − coverage − placement − nested Services − services.dev's take

services.dev's take falls on the value your brand adds, less on higher plans. It never touches pay, a pass-through, placement or a licensed fee, and an uncharged job pays none. Your plan decides which keys run on live jobs:

check names the plan live jobs need, line by line:

$ npx services.dev check
services/translation.ts · 14 lines · $89 per job, within 48 hours, charged on file's receipt.
  plan    Launch (services.dev) · roles.translator.pool at services/translation.ts:6 · subject at :13 · clocks at :14
          every key runs in test on any plan · deploy --live asks for Launch
  take    your plan's take on each released charge · never on the translator's $30.00

Sign the act yourself, with no pool, keep the clock on the job, and it sells on Free. Money is how a Service earns and pays, line by line.

With input, output and a price, a Service has one AI step and one adversarial review, and it's charged on delivery. No person touches it. Everything else is one key you add:

Services as software: why the finished job is what you sell, and the one question that decides it.