Evidence backed opportunities, governed approvals and verified results.
Agent is the action layer. It detects opportunities, investigates the evidence and recommends a strategy, each with a defined measurement. Approvals, policies and guardrails govern which action classes need a decision, verification re-runs the affected prompts for a before and after result, and experiments tie that to business impact where connected. A connected CMS that carries out an approved change for you is next; today you or your team make the change.
Agent
What should we do next?
- Opportunities
- Strategies
- Actions and Approvals
- Verification
- Experiments and Impact
- Activity
Quick answer: Agent
Agent is the action layer of BrandWater AI. It detects opportunities, investigates the evidence and recommends a strategy, each with a defined measurement. Agent policies, an approval center, guardrails, verification re-runs, experiments and an append only activity timeline are live. Nothing is applied to your site automatically, with or without approval; a connected CMS that carries out an approved change for you is next.
The agent lifecycle
Recommend first. Execute only with approval, later.
- State 1At launch
Detected
The opportunity engine finds a gap or anomaly.
- State 2At launch
Investigating
Prompts, answers, sources and competitors are traced.
- State 3At launch
Recommended
A structured strategy is produced, with evidence.
- State 4Soon
Approval
A permitted person approves, edits or rejects.
- State 5Soon
Executing
The approved change is applied through a connected system.
- State 6Soon
Verifying
The target state is checked and affected prompts re-run.
- State 7Soon
Completed
The outcome is stored with its evidence.
- State 8Soon
Monitoring
Recurring checks watch for change.
Every recommendation is governed by policy, every approval is guardrail checked, and every completed action gets re-measured against the prompts it was meant to move.
What Agent gives you
6 capabilities, each answering a specific question and labelled with its release stage.
How Agent measures things
Every metric has a definition, so a number always means the same thing.
| Metric | Definition | Capability |
|---|---|---|
| Impact signal | Why it matters, for example high demand and a high competitive gap. | Opportunities |
| Confidence | How strong the evidence is. | Opportunities |
| Owner and status | Detected, investigating, recommended, and later stages. | Opportunities |
| Action class | The kind of change recommended. | Strategies |
| Affected scope | Pages, topics, intents, engines and markets involved. | Strategies |
| Expected measurement | The rates that will be compared after the change. | Strategies |
| Approval record | Who decided, when, and the action's payload and scope. | Actions and Approvals |
| Policy level | Recommend only, needs approval or auto approve, set per action class. | Actions and Approvals |
| Guardrail events | Blocked actions, logged with the reason. | Actions and Approvals |
| Verification outcome | Verified: improved, No improvement, or Unverified: not enough signal. | Verification |
| Affected scope | The topics and prompts re-run for this one action. | Verification |
| Delta | Change in mention, recommendation or citation rate with sample size and interval. | Verification |
| Baseline and current | The two windows compared. | Experiments and Impact |
| Decision rule | The rule that decides the result, stored in advance, never adjusted after the fact. | Experiments and Impact |
| Outcome | Met, not met or inconclusive, with sample size and caveats. | Experiments and Impact |
| Event | One state change with its kind, time and payload. | Activity |
| Event kind | Status changed, action status changed, feedback, policy changed, approval decided, guardrail blocked, verification started or completed, experiment started or completed. | Activity |
| Audit trail | The append only record for every governed decision. | Activity |
How Agent connects
Every recommendation is governed by policy, every approval is guardrail checked, and every completed action gets re-measured against the prompts it was meant to move.
Questions it answers
- Where are the gaps worth acting on first?
- What is the plan to close each gap?
- How will we know whether it worked?
- What did the agent do, and who approved it?
What it is not
- Autopilot
- Nothing executes on your site automatically, even once approved. You or your team make the change.
- Promised outcomes
- An opportunity is a hypothesis backed by evidence, not a guarantee.
- Working without evidence
- Every opportunity states the problem, evidence, scope and expected measurement.
Agent questions
Does the Agent change my website?
No. The Agent recommends, and policies, approval and guardrails govern the decision to proceed, but carrying out the change is still yours. A connected CMS that applies an approved action for you is not built yet.
How will results be verified?
Mark an action done and press Verify now: it re-runs only the affected prompts for a before and after comparison, reported as verified, not improved, or unverified when the sample is too thin.
Which CMS will be supported first?
None yet. Governance is live today; a connected CMS is the next step, chosen from early customer demand.
See Agent on your own brand.
Start with a first audit. We show where you appear, who is named instead, and what to fix first.