Can a simulated environment contain information the evaluated agent cannot see?
A simulated environment can separate hidden business state from accessible evidence, allowing buyers to test investigation without exposing the answer inside the task input.
**Can the environment contain information the agent cannot see?**
Yes. A generated environment can maintain internal state for the evaluator while exposing only selected records through agent tools. That separation is useful when the task involves investigation, uncertainty or a response that becomes available only after an authorised action.
**What might remain hidden?**
In an insurance administration case, the environment may hold a pending response to a document request. The agent can see the request, its due date and delivery history, but cannot see the response until it enters the permitted inbox. The evaluator can use the hidden state to drive the episode without making it part of the prompt.
**What should the buyer specify?**
Define each role's accessible objects, allowed queries and visibility transitions. Also define whether an agent can discover missing evidence by asking another role, and what that request costs within the evaluation.
MirrorFirm could generate separate agent and evaluator views. Hidden state should support the task's mechanics rather than excuse an unknowable expected answer. Where decisive evidence cannot be accessed, the accepted behaviour may be an explicit uncertainty report or a request for assistance, not an unsupported final decision.
Specify visibility boundaries so agents must earn conclusions through permitted observations rather than read evaluator labels.
- Audience:
- Evaluation teams
- Content type:
- FAQ
- Buyer question:
- What can be generated
Content release: r-a220eb6e099b243b
Related questions
- What policy material could accompany generated overdue records?
- What does business grounding mean when the delivered material is generated?
- Which fields make generated overdue records useful for temporal reasoning?
- Can generated tasks represent a response that arrives but does not resolve the request?
- What should a generated environment let an overdue-handling agent do?
- How can generated tool contracts prevent duplicate contact during retries?