A business workflow is more than a prompt. Each environment describes its own records, rules, documents, actions and correct outcomes—so an agent can be tested in context.
Reusing the engine does not mean pretending every profession works alike. A new environment needs new knowledge and new evidence.
What exists, how records connect and which fields matter.
What a practitioner would check, and when the normal path changes.
What an agent may read, write and infer from permitted evidence.
What earns credit, what is unsafe and who has reviewed the judgement.
Finance is a functioning development environment. The others below are directions for future research and partnerships, not downloadable or expert-verified packs.
Linked suppliers, purchase orders, invoices, payments and bank entries. The agent can investigate mismatches, repair links, stage approvals and leave a replayable trail.
Movement of goods, documents, handoffs and exceptions. Scope and rules need practitioner input before a pack exists.
Administrative workflows with careful boundary and safety design. No clinical claim or patient data use is implied.
Seasonal records, trade evidence and operational decisions may become a track after domain discovery.
Documented approvals, supplier checks and accountability could form a separate environment with its own review.
Every pack needs clean data, correct planted cases, a solvable task, answer-safe tools, shortcut checks and practitioners who can challenge its realism. A finance result does not automatically transfer to another domain.
Read the benchmark method