Skip to content
MirrorFirm

What should a buyer request in a generated environment specification?

A checklist of the items to ask for in a simulated environment specification for facility work, covering tables, statuses, tools, policies, case mix, documents and reset.

Ask for these items in writing, because they decide whether an environment can be run, graded and repeated on your side.

- **Tables and keys.** Each table, its identifier style such as FAC-3310, and the foreign keys linking approvals, facilities, parties and security. - **Status model.** The allowed facility statuses, which transitions are legal, and which role may trigger each one. - **Tool surface.** Each action with its inputs, outputs, error cases and side effects on state. - **Policy documents.** The text of the rules the agent must follow, with a version identifier on every case. - **Case mix.** The spread of clean cases, exception cases and cases that should end in escalation. - **Document artefacts.** Whether offers and evidence exist as plain text, structured fields or rendered files. - **Reset method.** How any case is restored to its starting state from a seed, and how that is verified.

Asking for these items up front lets you judge whether an environment is deterministic, complete and gradable before any volume is produced.

Audience:
Model labs
Content type:
Checklist
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Loan booking