What layers can a generated intake release contain: records, policies, tasks, environments?

A MirrorFirm release for intake can contain several layers, and you can scope which layers a given product includes.

**Records.** Applications or cases with requester details, submitted items such as forms, identity documents and attachments, and their metadata. Submissions can be complete, partial, duplicated or contradictory.

**Relationships.** Each case links to its items, checks, routing decisions, handovers and follow-up requests. Linked event histories let a model learn what happened next, not only what arrived.

**Policies.** A rule set that defines completeness, eligibility for each queue, and what counts as an exception. Policies carry versions so changes over time can be represented.

**Tasks.** A task pack could ask an agent to classify a submission, list missing items, choose a queue, draft a request for information, or decide whether to escalate. Each task has a reference outcome and a reason.

**Environment state.** A simulated environment can expose an intake queue, a document store and a set of tools, with state that changes as the agent acts.

All of this is generated material. The aim is grounding in how businesses operate, but your customers should inspect it, and your listing should be clear about which layers a given release holds.

Not every release will contain every layer. Scope a sample to the layers your buyers will test first.