# LIMITATIONS — forge-pm-work-order-sim

> **FICTIONAL / SYNTHETIC DEPLOYMENT MODEL.** Read this first. Everything below is a
> disclosed seam — a place where this study is simulated rather than live.

## DISCLOSED_SEAM — Fictional customer
"Forge Property Management" does not exist. There is no real customer relationship,
contract, deployment, or case study. This is a synthetic deployment model built to
size an opportunity honestly, not a record of real work.

## DISCLOSED_SEAM — Synthetic data
All 100,000 work orders are machine-generated by a seeded PRNG
(`src/enterprise-synth.mjs`) with a ground-truth answer key. Properties, units,
tenants, vendors, timestamps, costs, and descriptions are invented. Reported
accuracy is measured against the synthetic key; real tenant text is messier and more
varied, so absolute accuracy in a real deployment would differ.

## DISCLOSED_SEAM — Simulated operations & ROI
Manual handling time (8 min/order), exception review time (5 min/order), coordinator
cost ($38/h), implementation cost, and platform cost are **stated illustrative
assumptions** (`assumptions.json`), not measured production figures. The ROI is a
transparent model driven by the measured auto-action rate plus those assumptions —
it is not a realized financial result.

## DISCLOSED_SEAM — In-process infrastructure
Persistence uses the real PostgreSQL engine via PGlite (in-memory for this run), and
dispatch crosses a real gRPC/HTTP2 wire to a Node service on localhost. An external
managed PostgreSQL (`DATABASE_URL`) and a Go gRPC dispatch service implementing
`proto/dispatch.proto` are wire-compatible, but are **not** exercised here.

## DISCLOSED_SEAM — Lexicon classifier, not an LLM
The classifier is a deterministic keyword-lexicon model chosen for auditability. The
production design swaps an LLM behind the same interface; that swap and its accuracy
on real text are **unverified** here.

## DISCLOSED_SEAM — Enterprise non-functional controls not in scope
Identity/SSO, RBAC, tenant isolation, audit retention policy, and security/compliance
review are out of scope for this simulation and would be required (and Proof-Layer
weighed) before any real production claim.

## What is NOT claimed
- No real production performance.
- No realized savings.
- Not `CERTIFIED` and not `PRODUCTION_VALIDATED` (the Proof Layer assigns the state;
  the fictional-customer seam blocks those by design). The simulation-tier label is
  `FICTIONAL_DEPLOYMENT_MODEL_CERTIFIED` — internally validated and reproducible only.
