1,000 medical equipment catalog entries
Unique IDs and simulated serials; stable model/type/skill, owner, area and coverage records; exactly five tickets reference every asset
Current local source tests
Executed on October 18, 2026 against the expanded source engine:
- `node scenario-lab-source/test.cjs`: PASS, 353,714 assertions.
- `node scenario-lab-source/review-oracles.cjs`: PASS, 65/65 independent boundary/invariant groups.
- Cross-view identity check against `generated-test-fixtures`: PASS for all 1,000 equipment records, 20 type/model/skill definitions, 50 accounts, 20 engineers and 5,000 ticket-to-asset/account references, including case-sidecar fields.
- Engine SHA-256: `b1d081046037aac017c03289f646639c0a6c3f7e24d29edd360e039c0892dad8`.
These commands do not write generated files by default. No generated `dist` rebuild, browser run, deployment, private database mutation or live operational action is implied by this evidence. Older checked-in result files are historical until explicitly regenerated.
Exact topology and referential integrity
50 accounts / five existing areas / 20 engineers
Ten accounts, 200 owned assets and four home engineers per area; unique IDs; each engineer receives assignments
Exactly 5,000 ticket identities
All 5,000 IDs are unique in each projection; balanced, surge and acceptance preserve identity, account, asset, work type, skill, priority and offer kind
Account and asset integrity
Twenty equipment units and 100 tickets per account; every ticket references an existing owned asset; detached snapshot equals catalog; mutation tests prove snapshot independence
Stable coverage catalog
Warranty/contract/neither kinds; five assessed coverage bases; independent derivation from fixed catalog dates; contract entitlement flag retained
Work-type diversity
All 24 configured labels and all 96 work-type × priority combinations in each projection
Balanced and surge are alternative workload projections of the same 5,000 tickets, not 10,000 additional tickets. Acceptance repeats balanced event times with a different SLA clock. A separate 15-item reusable continuity pool is not counted as customer-owned medical equipment. Application Test and financial/report projections consume the same canonical equipment and ticket-to-asset/account identities. Operational and financial outcomes remain explicit projection-specific fixtures, not synchronized live records.
Scheduling, stock and SLA evidence
Demand distribution
Balanced 200 × 25 requests; surge 100 × 50; every account has 100 requests in each view
Eligibility and ranking
Independently replayed daily batch priority, receipt, availability, area, skill, remaining capacity and deterministic load ranking; selected engineer must match replay
No overbooking
Every assigned interval is after acceptance, inside shift, correct service-plus-travel duration, non-overlapping and within daily capacity; unavailable engineers have no bookings
Hand-derived first dispatch
Engineer 1 is on leave; Monitoring-qualified engineer 2 receives the first ticket at 08:15–09:00 UTC
Escalation
Balanced: 5,000 assigned / zero unassigned. Surge: 2,164 assigned / 2,836 unassigned. No unassigned ticket fits a remaining eligible gap
Diagnostic parts ledger
Independently reconstructed opening 30, daily receipt 30, reservation, issue and unused returns; no negative balances or over-return; 322 balanced and 2,030 surge shortages
Reusable continuity equipment
Compatible real pool reference, accepted simulation before release, 48-hour return plus 12-hour inspection; no overlapping hold in any projection
SLA agreement snapshots
One versioned simulated agreement per account; detached per-ticket snapshots cannot mutate other tickets or the account agreement
Coverage boundaries
Inclusive start/end, one millisecond before/after, epoch zero, missing dates, invalid dates and interval rejection
SLA arithmetic
Before/at/after deadline; overlapping/duplicate/clipped waits; chained waits; late waits cannot retroactively extend deadline; nonfinite/reversed/negative inputs rejected
Clock modes
Identical balanced underlying events and dispatch; first response is 1 hour from receipt or 0.75 hours from acceptance; response never pauses
Balanced's zero queue is a result of the expanded staffing fixture. Surge still exercises capacity/availability escalation; no assertion assumes that adding engineers must preserve the old smaller dataset's queue count. The figures are test coverage, not forecasts of staffing or supply adequacy.
Lifecycle and quotation evidence
The focused source suite projects all 5,000 tickets at the full horizon and checks:
- Open, pending, in-progress, resolved and closed cases exist in every view.
- Quotation pending, accepted, rejected and not-required cases exist.
- Parts on order, included and paid loaners, backup delivery, and scheduled/completed reinstallation are represented.
- Paid loaner release requires an accepted positive-price quotation; rejected quotations never release equipment.
- Closure requires a resolution event and submitted report; parts quantities remain nonnegative.
- The independent diagnostic continuity ledger reserves compatible reusable items only after acceptance and honors return/inspection holds.
Full-horizon status counts, balanced: 416 open, 2,908 pending, 843 in progress, 417 resolved, 416 closed. Surge: 416 open, 2,921 pending, 830 in progress, 417 resolved, 416 closed. Each sums to exactly 5,000. Quotation values are illustrative estimates, not invoices or revenue.
The lifecycle narrative and diagnostic stock/SLA arithmetic are separate fixture models. A narrative loaner or backup reference does not prove a reservation in the diagnostic pool, and a diagnostic restoration boundary does not claim that a pending lifecycle ticket is restored. Twelve representative lifecycle patterns are not exhaustive combinations. Additional full event-boundary/UI/integration suites must be run during the integration build.
Historical baseline evidence
The existing `results/` directory and older `test-results.json` contain evidence from the earlier 20-account, six-engineer, 1,440-per-profile fixture and prior application baselines. Previously recorded workspace, inventory, dispatch, trial, client setup, extension, marketing, connected-intelligence, preview/export, form and notification suites are not fresh passes for this expansion.
Historical limitations included a missing optional Resend SDK in one backend test, an absent unrelated Title project in a cross-project script, and a Chromium launch restriction. Current browser availability must be checked anew; this source-only task claims no browser/device screenshots or pass.
Not established by these tests
Production account authentication or tenant isolation; private route security in a browser; live server/database migration; transactional/distributed calendar or inventory locking; real contract acceptance; real quotations, invoices, payment, email or native sharing; SAP/SSO; iOS/device QA; clinical suitability or manufacturer entitlement; optimal routing; exhaustive combinations; production readiness. Client-view selectors hide presentation detail but do not enforce privacy.