> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usefluency.com/llms.txt
> Use this file to discover all available pages before exploring further.
# July 24, 2026 | Fluency Product Update
We have been working on giving you a clearer map of how work happens across your business, direct control over what Fluency understands, and a way to commit automations the moment Fluency finds them worth building.
***
## Map Value Streams Down to Individual Tasks
Fluency now automatically maps every layer of work across your business, from a **high-level value stream** like the full lifecycle of a loan down through the processes underneath it (KYC, intake, treasury management, principal and interest collection) to the individual tasks people do inside them. No integrations or manual setup required, and the map gets more accurate the longer Fluency runs.
This maps onto the same five-level hierarchy used in frameworks like [APQC's Process Classification Framework: category down to task](https://www.simplifyingprocesses.com/blog/process-framework). You can zoom into any level without losing sight of the ones above or below it, so you're never stuck choosing between the high-level view and the operational detail.
**What this means for you:** you can start at the level that matters to the business, a value stream, and drop straight into the exact task causing friction, in the same view. And because Fluency isn't looking at one process in isolation, it surfaces automation opportunities that cut across teams and systems, the kind that stay invisible if you're only looking at one workflow at a time.
***
## Edit What Fluency Maps
You can now edit what Fluency maps directly inside Work Explorer: rename a process, regroup how something rolls up, or correct a task that's been misclassified.
These edits aren't just cleanup. They update the same live map that every recommendation and automation draws from, so your team's expertise directly sharpens what Fluency surfaces next, not just how the current map looks.
**What this means for you:** you're not stuck with Fluency's first read of your business. You can shape it directly, and every correction compounds, making the next recommendation more accurate than the last.
***
## Commit Automations Directly Into the Stream of Work
You can now commit an automation opportunity directly from the platform. Once you do, a Fluency engineer picks it up and builds it, using an agent built on your company's ontology rather than a generic script or template, so it can reason across the systems and teams the work actually touches, not just the one task in front of it.
That foundation is what makes these automations durable. Most automation, RPA or otherwise, is built against how a process worked at one point in time, and breaks the moment something changes: a new system, a new field, someone leaving. Fluency's agents check the live ontology at decision time instead, so they act on what's true in your business right now and adapt as it changes instead of quietly breaking.
**What this means for you:** less time spent finding out an automation broke, and less rework keeping it current. You commit the opportunity, we build it, and it keeps working as your business and priorities evolve.
***
## What's Coming Next
Finding automation opportunities is great. But deciding where to start is the difficult.
In the coming weeks, we'll share the framework we use to help teams prioritize automation opportunities by impact and feasibility, so you can start with the highest-value work that gives your team the most leverage.