Key Concepts
Live knowledge: Data the agent looks up right now, through a connected tool or by reading a public web page. What it sees is true as of this minute.
Stored knowledge: Anything saved for the agent to read, such as brand guidelines or the result of its last run. It lives as a document in a Knowledge Base, put there by you, a teammate, or the agent itself at the end of a previous run. An agent does not remember anything on its own, so if it is not saved where the agent can read it, it will not be there next run.
Baseline: The saved version the agent compares against. Each run replaces it with today’s version, so the baseline slides forward.
Quick Reference
The three ways an agent gets knowledge
- Connected tool: the agent asks another platform for specific data
- Web read: the agent reads a public page, like a competitor’s pricing
- Stored knowledge: anything saved for the agent to read, like brand guidelines or its last run’s output
Live vs. stored
- Live only: tells you what is there. A weekly snapshot of three pricing tiers, which you could have found yourself.
- Live plus stored: tells you what changed. It compares last week’s page to this week’s and flags a new tier. Change is usually where the insight lies.
How an agent notices change (four moves)
- Gather the current data
- Read what it saved last time
- Compare the two and decide what is different
- Save today’s version to a Knowledge Base, replacing the old one
What to put in the instructions
- Where the older version lives
- Where to save the new one
- The right references if you want it to write in your voice
Find the data your agent needs
- List every tool you log in to for work (analytics, CRM, and so on)
- Remember each interface is the tip of an iceberg, with far more data underneath than any dashboard shows
- Ask what is available and how to use it. Example: Google Search Console shows a short keyword list, but holds every keyword you rank for, by page, by day, by country.
Common failure to avoid
- An agent that returns one snapshot a week. The team stops reading it and misses the real change when it finally happens.
Notes
- The memory behind change detection can be as simple as one saved page in a Knowledge Base.
- An agent is only as good as what it knows, so describing an agent is partly the work of pointing it at the right things.