PROFESSIONAL WORK · Reporting & operations
Operational chat
A chat assistant that answers leadership’s operational questions from curated data snapshots, using defined business terms.
BuiltExecutive pilotDocumented August 28, 2026
My contribution
Built the chat service and domain integrations, including invoice-state interpretation and snapshot handoff paths.
Tools
FastAPI · PostgreSQL · Domain-specific tools · Snapshot integrations
How it works
- PersonOperational questionAsked by someone in the leadership pilot
- StepRoute to a domainScheduling, invoices, sourcing, or finance
- InputCurated snapshotSaved by each source system, not a live call per question
- StepApply business definitionse.g. approved-unpaid vs. payment initiated vs. paid
Missing timing → no invented overdue age
- OutputGrounded answerBased on the snapshot and its freshness
Decisions that mattered
Status words need a contract
Approved-unpaid, payment initiated, and paid are different states. When approval timing is missing, the assistant doesn’t invent an overdue age.
Read questions stay reads
An inventory question doesn’t quietly draft a collection reminder. Invoice questions use saved snapshots instead of a live accounting request for every prompt.
A copy should not break its source
Financial and invoice tools can save successfully even if copying their snapshot into chat fails.
Capabilities are per tool
Some sourcing tools can offer action cards; the financial tools are read-only. Each tool’s capabilities are defined separately.
Results
The August 2026 pilot records document corrected invoice-state behavior and a suite of 273 passing tests (one skipped).
Scope & limits
The pilot covers the supported domains below. Answers are only as current as the latest snapshot.