Knowledge
Published, reviewed MirrorFirm entries. Each entry states its claim and evidence status.
Content release: r-3c7687664372c00d
Who MirrorFirm is for
- How does MirrorFirm help agent developers?
Connected business tasks, including handovers and dependencies.
- What do environment builders get from MirrorFirm?
Operating patterns translated into roles, records, tools and changing state.
- How can evaluation teams use MirrorFirm?
Evaluations around business decisions, policy boundaries and explicit outcomes.
- What should a licensed reseller look for?
An inspectable release, documented provenance and clear terms.
- What can a model lab use MirrorFirm for?
Richer business-operations material for model training.
Approvals and connected records
- How can an approval limit be turned into an evaluation task?
Test when an agent should act and when it should escalate.
- Why do records need to be connected?
A decision affects an application, its policy and downstream work.
Changing state and environments
- How does changing state shape the next task?
Actions change what comes next, and the consequences can be inspected.
- What is a stateful environment?
Business operations as connected state with actions that affect later outcomes.
The observed business foundation
- What does MirrorFirm provide?
Generated data and simulated environments for AI training and evaluation, informed by observed business operations.
- Is MirrorFirm selling observed business data?
The commercial product is generated data and environments; the observed foundation explains how they are built.
- How can a buyer inspect the grounding of a release?
Separate what was observed, what was modelled and what was generated.
- Where does the realism in MirrorFirm output come from?
Access to real businesses informs what is generated.
Scoping and evaluating a release
- How is a custom scope defined?
Objective, operating patterns, deliverable and evaluation criteria are scoped together.
- What should a dataset buyer inspect first?
A small sample that exposes schema, relationships and business logic.
- What is a sensible first step?
Inspect a sample, discuss the business logic and define what a pilot must demonstrate.
- What is in a task pack?
A business objective with the policies, records and starting conditions to work through it.
Handovers, exceptions and shared context
- Why build tasks around exceptions?
The interesting work often begins when the standard path breaks.
- Why do handovers matter in generated scenarios?
Context, dependencies and responsibility move with the work.
- How are workflows that cross departments represented?
Shared context is retained across departments.