Direct answer
Source material is the original supplied evidence or context. Derivative reports are intermediate extraction, evidence, claims, workflow and retrieval outputs used to build safely. Final knowledge-pack files are the curated buyer-facing or internal deliverables that preserve useful knowledge while applying rights, caveats and packaging rules.
Why this matters
This helps stop a common packaging mistake: treating every intermediate file as a customer deliverable.
How to use it
- Classify original inputs as source material.
- Use derivative reports as build intelligence, not automatic customer files.
- Apply route, rights and evidence gates before final packaging.
- Include only buyer-facing outputs in the customer ZIP.
- Keep internal QA and process prompts out of public products.
Example
A NotebookLM claims table may guide the final pack, but it does not automatically belong in the customer ZIP unless the product intentionally includes it and rights allow it.
Caveats and limits
Derivative reports can be valuable, but they may contain private labels, raw source traces, unresolved contradictions or unsafe wording that should not be shipped directly.