Sourced output

The running jobjob_7Hq2 · working · $49.00 held

cite 'source' makes every field a step outputs carry the file and page it came from, and the review fails a field that doesn't trace.

cite: 'source' answers one question: where did each value come from?

services/term-list.ts
  deliver: { terms: { by: 'ai', cite: 'source' } },
Run
npx services.dev check
magic values: none
  steps   terms · ai · cites source → review · ai · adversarial

On a work step

KeyWrittenLeft outDoes
cite'source' | (string & {})none'source': every output field cites the input it rests on, and the review fails a field that doesn't. A string: the authority a calculation follows, recorded on the line.

A cited step's fields arrive as { value, source }, where the source names the input file and the page. The review fails a field that doesn't trace back:

Run
curl http://localhost:8787/jobs/job_7Hq3   # its output
magic values: none
{
  "terms": {
    "value": [
      "Simulated terms 1",
      "Simulated terms 2",
      "Simulated terms 3"
    ],
    "source": {
      "file": "lease.pdf",
      "page": 1
    }
  }
}

On localhost the simulated AI cites the first file the order sent, at page 1. Wire your model, and it names the page it read.

The step's line on the record carries "cite": "source", so the evidence bundle shows which output was cited.

To record the rule a calculation follows, rather than the document a value came from, give cite a string. See your code as a step.

No call of its own: it changes what the job carries, on every surface that reads one.

Operations has every column of every row.

None of its own.

The lines that use it in the example brands, as their files write them, and what check read aloud for each file.

legal · services/demand-letter.ts · 26 lines
// The draft doesn't cite here: under cite: 'source' every output field is { value, source }, which the
npx services.dev check · captured/legal-walk.txt
services/demand-letter.ts · 26 lines · $149 per job, within 48 hours, charged on send's receipt.
  steps   consent · client · consent → draft · ai → attack · ai · adversarial · 3 lenses → sign · attorney · client · stamped · 2-item checklist → send · the recipient → courier · a courier · routed → reply · ai → settle · client · decide

The legal example runs every one of its files, captured.

tax · services/estimate.ts · 17 lines
    compute: { by: estimateFor, cite: 'prior-year safe harbor, cumulative by quarter' },
npx services.dev check · captured/tax-check.txt
services/estimate.ts · 17 lines · $79 per job, within 48 hours, charged on delivery.
  steps   compute · code · cites prior-year safe harbor, cumulative by quarter → approve · owner · decide → review · ai · adversarial → pay · Treasury and states · one for each jurisdiction with an installment → record · code

The tax example runs every one of its files, captured.