Skip to content
MirrorFirm

What licence questions should buyers settle before using or redistributing generated packs?

Buyers should clarify permitted training, evaluation, modification and redistribution uses across internal systems, downloadable exports and public agent-facing access.

**Does access to a sample establish permission for every downstream use?**

Do not assume it does. Ask which uses the proposed licence covers, including model training, internal evaluation, hosted agent testing and modification of the supplied material. The applicable rights need to be stated in the licence offered for that release.

**What if the team creates derivative task packs?**

Clarify whether transformed records, added annotations and redistributed subsets are permitted. Also ask how required notices or attribution should travel with those derivatives, if such requirements apply.

**Does public MCP access change the question?**

Publicly readable content and downloadable material can still have different usage conditions. Ask whether automated retrieval, caching, republication and inclusion in another public tool are covered. Technical accessibility alone should not be treated as a statement of licence scope.

**What should procurement and engineering review together?**

Provide the intended deployment and distribution paths, then confirm the rights attached to each. MirrorFirm's commercial deliverable is generated material; a licence request should not presume delivery of underlying real business records or permission to access them.

Match the requested licence to actual engineering and distribution plans rather than assuming access grants every intended use.

Audience:
Agent developers
Content type:
FAQ
Buyer question:
Scope and getting started

Content release: r-a220eb6e099b243b

More on Policy change propagation