> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/release-notes/2026/august/22-august.md).
# 22 August
## What's New in This Release
This release completes Superteams by adding full support for Pattern of Life (PoL) content, building on last week's release, which introduced Superteams for MEL.
This release also adds five new ready-to-use Ventura scenarios to the content library, covering supply chain disruption, AI failure, severe weather, and cyber attack themes.
## New Features
### Superteams for Pattern of Life (PoL)
**What's new**
Following last week's release of Superteams for MEL content, this release adds full support for publishing Pattern of Life (PoL) to Superteams. Designers can now run PoL stacks against collections of teams. Facilitators can move teams to Superteams and set Staxs to run to a Superteam during an exercise.
**Why it matters**
For exercise designers, this removes the need to duplicate Pattern of Life content for what is effectively the same audience across multiple teams. For facilitators, it completes dynamic "branching" on a live exercise by moving a team into a Superteam to show the consequences of a decision, with the PoL stack publishing accordingly.
**Key Features**
* Publish PoL stacks to Superteams
* Move teams between Superteams and change a stax to sent to Superteam live
* Superteam PoL queues allocated per licence
> **Licence**
>
> Osprey and Eagle
⚙️How it works
* In a live exercise, teams can be moved, added, or removed from Superteams, but any running PoL stack will continue with the previous setup. Recommended approach: stop the PoL stack, update the Superteams, then restart the PoL stack.
* PoL queue allocation for Superteams is based on the number of teams inside the Superteam. For example, on an Eagle licence, starting a stack ("Angry Customers") targeting a Superteam with 5 teams uses 5 of your available queues.
* Osprey: 16 queues
* Eagle: 25 queues
{% hint style="info" %}
**Use Case Example**
A facilitator moves the "Big Bank" team into the "Challenger Banks" Superteam mid-exercise. Now when the Challenger Banks stax runs, Big Bank will get the content. Note that the stack has to be stopped and then started before Big Bank gets the content.
{% endhint %}
## Technology Improvements
## New Ventura Scenarios
This release adds five new scenarios to the Ventura content library:
**Rolling Blackouts.** A record UK heatwave is pushing the national grid to breaking point. Refrigeration is already failing at several stores as rota power cuts are confirmed for the evening. You're under pressure to act before stock, safety, and reputation take the hit. *(Language: English | Type: Operations, Supply Chain, Reputation)*
**Strait Closure.** Following geopolitical instability, the Strait of Andistan is closed. Working for a manufacturing company in France, the player must manage the disruption to their construction projects, facing pressure from Government to deliver on time. *(Language: English | Type: Supply Chain, Operations)*
**AI Failure.** A major shared AI services provider, embedded across your operations, communications, and demand forecasting tools, has suffered an unknown service degradation. There is no outage and outputs continue to look professional and plausible, but things are starting to go wrong. *(Language: English | Type: Reputation, Supply Chain, Operations)*
**Severe Weather.** Step into the leadership team of a major insurer as a severe weather event triggers a surge in claims at the exact moment a critical digital supplier begins to fail. Customer portals slow, call volumes spike, claims queues grow, and an AI-assisted triage system begins producing inconsistent results. *(Language: English | Type: Reputation, Operations)*
**Data Breach.** An Italian bank suffers a data breach, impacting customer trust and brand reputation as you struggle to maintain normal operations and protect client data. *(Language: Italian | Type: Cyber Attack)*
## Fixes and Improvements
This release also includes a number of refinements.
---
# 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://helpdocs.conducttr.com/release-notes/2026/august/22-august.md?ask=&goal=
```
`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.