How is a release licensed, and what limits should buyers know about?
Covers licence questions on evaluation and training use, publication and derivatives, plus the limits of generated data and why it is not assurance of compliance.
**How is a release licensed?** Licence terms are agreed with MirrorFirm for each engagement. Raise the intended use early, since it shapes the terms.
**What should I ask about use rights?**
- Whether the licence covers evaluation only, or also training and fine-tuning - Whether you may publish results, or share the set with partners and contractors - Whether derived artefacts, such as graders or rewritten tasks, are covered - Whether you may refresh or extend the set later
**Is the data real?** No. The output is generated, and MirrorFirm does not supply real business records. Its structure and behaviour are informed by direct observation of how businesses operate, but that does not guarantee that any record is free of resemblance to real material, and it is not privacy or regulatory assurance. Your own review of grounding and disclosure risk still applies.
**What limits apply to the scope?** Coverage is limited to what is specified and generated. Policies specific to your organisation may need to be provided as inputs. A set built for one workflow will not automatically suit another.
**Can I use it for compliance sign-off?** Treat it as test and training material for agents, not as evidence of regulatory approval. Decisions on deployment remain with you.
**What is a sensible first step?** Ask for a small sample on one case type and review it against your own policies before discussing anything larger.
Raise intended use early, treat the data as generated test and training material, and keep deployment and compliance decisions with your own reviewers.
- Audience:
- Evaluation teams
- Content type:
- FAQ
- Buyer question:
- Scope and getting started
Content release: r-a220eb6e099b243b
Related questions
- How do environment reset, seeds and versioning work for a sufficiency environment?
- What licence terms and limits should I expect for a sufficiency release?
- How should I scope a sufficiency dataset, task pack or environment?
- What does a useful first pilot look like for a team building a utility onboarding agent?
- What should I ask for in a sufficiency sample or pilot?
- What should a first handoff package contain and how do we integrate it?