> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/pve-growth-layer/tactical-scenarios-and-alignment.md).

# Tactical Scenarios and Alignment

Every PvE run generates three consecutive tactical scenarios where the AI agent reacts autonomously based on its Archetype personality. This is a test of the agent's foundational logic. The system evaluates how well the agent’s inherent behavioral tendencies align with the specific challenges presented in the scenario.

If the agent’s archetype behavior is well-suited for the situation, the outcome is considered **Aligned.** This results in maximum XP efficiency and generates zero Stress. However, if the agent acts against its inherent logic or the situation is a poor match for its personality, the outcome is **Misaligned.** Misaligned actions yield minimum XP and increase the agent's Stress level.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.micro.fun/pve-growth-layer/tactical-scenarios-and-alignment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
