# Northstar Office Supply: invoice intake

**Synthetic demonstration data.** Northstar Office Supply, its invoices, source
records, and decision are fictional. They are authored fixtures, not customer
evidence, recorded interviews, or an observed business outcome.

## Source PS-SRC-01: fictional walkthrough notes

The intake team receives a USD invoice and looks for an accountable team. Missing
owners cause the invoice to return for clarification. Owned invoices over $1,000
need manager review; other owned invoices enter standard review. No invoice is
approved or paid by this example.

## Source PS-SRC-02: fictional invoice-review policy

Rule **PS-RULE-01**, version 1:

1. A missing, empty, or whitespace-only owner means `needs_information`.
2. Otherwise an amount strictly greater than USD 1,000 means `manager_review`.
3. Otherwise the result is `standard_review`.

The USD 1,000 boundary belongs to standard review. Missing owner takes precedence
over amount. Inputs in this bounded example have valid nonnegative numeric amounts
in USD. Currency conversion and malformed amount handling are outside its scope.

## Source PS-SRC-03: fictional invoice export

| Invoice | Amount (USD) | Owner | Expected queue |
| --- | ---: | --- | --- |
| INV-101 | 750 | Operations | standard_review |
| INV-102 | 1,250 | Operations | manager_review |
| INV-103 | 1,250 | empty | needs_information |
| INV-104 | 1,000 | Operations | standard_review |
| INV-105 | 750 | three spaces | needs_information |

The machine-readable export is `invoices.json`. These expected results are test
oracles, kept separate from the runtime's actual output in `run-result.json`.

## Traceability boundary

PS-SRC-01 and PS-SRC-02 support PS-RULE-01; PS-SRC-03 supplies five acceptance
cases. `decision.md` explains the selected design. The IR was manually authored
from that rule. The existing ProcessScout compiler generated the native workflow.
This is not a recording of automatic evidence extraction or a product UI journey.