Apogy Health

Last run

Extraction

—

target < 20s · gate 90s

Stages passed

—

of 12

Total wall-clock

—

upload → cleanup

Runs recorded

history depth

Extraction latency over time

Nothing to plot yet. Two runs draw a line — and the line is the point: the regression that took extraction from one LLM call to five, and made it three times slower for two months, would have shown here as a rising trend long before anyone noticed.

Stages

#	Stage	What it proves	Result

Run it

# one-time per day — the smoke reads role passwords from SSM aws sso login --profile apogy # run against the deployed sandbox with a real contract # (sandbox.apogysolutions.com — the ALB routes /api/* here. # apogy-booking.* serves the web app only and has NO api route.) python3 smoke.py --contract "/path/to/a/real/contract.pdf" --publish

NetSuite push stays dark (--netsuite dry) until Greg's Sales Order form lands. A withhold with an actionable reason is a pass — a silent success would be the bug.
Real contracts only. There is no fixture fallback, and there never will be.

Not yet wired

Check	Why it belongs here	Status
Deployed version vs `main`	Tells you at a glance whether the box is running what we think it is.	To build
Extraction regression gate	LLM calls per contract. Merged as PR #721 — surface its last result.	To build
Gold corpus integrity	27 cards, sha256-verified against the canonical store.	To build
Env drift on the box	The 2026-07-13 outage was one env value that never got applied.	To build

Apogy Health

Never run