What should a lab put in a request for a review sample?
A sample brief should specify the model's operating conditions and intended learning objective, helping the generated material address a concrete capability gap rather than generic business realism.
Use this checklist to turn a broad interest in business reviews into a concrete sample request.
- State the target model behaviour. - Name the business domain and reviewer role. - Describe the agent's available context window. - Specify document-reading and tool capabilities. - Identify acceptable human intervention points. - Describe the baseline used for comparison. - State the evidence needed for a proceed decision.
The operating conditions affect what a sample can demonstrate. A model receiving a complete evidence bundle faces a different task from an agent that must discover records through tools. A sample intended for supervised training also needs a different presentation from a hidden-answer evaluation episode.
Include one failure the lab wants to understand, such as losing an obligation after a handover or drawing a conclusion from insufficient evidence. That gives the sample a specific learning objective without prescribing its entire construction.
A buyer can ask MirrorFirm to respond with a proposed generated sample design and any assumptions that need agreement. The first inspection can then compare the design with the intended experiment before the lab decides whether to broaden the scope.
Give the supplier enough information to design a sample that fits the lab's actual experiment.
- Audience:
- Model labs
- Content type:
- Checklist
- Buyer question:
- Scope and getting started
Content release: r-a220eb6e099b243b
Related questions
- Which licence questions should agent developers resolve before using a generated release?
- What can a focused pilot reveal about handling a challenged review finding?
- How should a buyer choose the scope of a first review pilot?
- What should a sample request specify so a buyer can judge fit without overextending the pilot?
- What technical handover should be agreed before connecting a generated release to an agent?
- Which integration boundaries should be agreed before a pilot starts?