<!-- Derives from: The River constraint set (the twenty rows and their questions, verbatim) @59ad -->
<!-- rows.md is generated from the constraints file, not edited here; regenerate when it changes. Format: family heading, gloss in italics, then one line per row as "grid label | question". -->

## Workflow and workforce
*How the work gets done, and who does it.*

- Paying less per finished task | What does it now cost to get one piece of work finished to a standard an organization would hand over, counting retries, review and rework?
- Sending agent output as-is | Is agent output usable as it stands, or does it still need finishing before anyone would send it?
- Proving it pays | Is there yet an accepted way to tell whether agentic work pays for itself, or is it still a matter of vendor claims?
- Finding people to run it | Are the experienced people needed to staff and oversee this work available in the market?
- Getting agents into software | Can agents technically operate the software an organization actually runs?
- Getting agents to run machines | Can agentic systems run machines in the physical world, or only software?
- Buying licenses that allow agents | Do the licenses a company buys allow an agent to do the work, or are they written and priced one human seat at a time?
- Getting people to accept agents | Will customers and employees deal with an agent at all, knowing it is one?

## Context
*What an agent knows about an organization, and how far that knowledge extends.*

- Onboarding agents | Can agents absorb how an organization actually works without someone stopping to feed them?
- Switching vendors | When the context that makes agents useful lives inside one product, can a company leave?
- Keeping it contained | Can these systems hold what they learn about an organization without it getting loose?

## Governance
*How much of the work runs without a human, and what catches it when something goes wrong.*

- Bolting rules on afterwards | Can an agent's behavior be bounded by rules applied from outside the work, or does it talk its way past them?
- Getting the rules built in | Are there tools or standards where the rules are part of how the work runs, so the safe path is the default one?
- Catching it in time | Can a failure be spotted before it compounds at machine speed?
- Explaining it afterwards | Can an agent's reasoning be reconstructed afterwards, in a form that survives a regulator or a customer asking?
- Carrying the risk | Is a company answerable for what its agents do, and can that exposure be insured?
- Controlling whether agents work together | Can an organization decide whether its agents work with each other, or do the agents decide?
- Keeping outsiders out | Can a third party make an agent act on their instructions instead of the organization's?
- Giving agents their own identity | Can an agent be authenticated, authorized and audited as its own actor, or does it borrow a person's credentials?
- Knowing what will be required | Are the rules governing agentic work settled enough that a plan made now will still be valid when it lands?