Module 4 of 4 · Stage 06
Re-observe & Activate
Objective
Find out whether publishing changed the answer, and make sure a consequential action uses current facts.
Ongoing, recurring plus event time · Produces evidence, and the next set of gaps · Usually marketing, or anyone with a number to hit
In the loop
Re-observation is stage 02 run again after publishing. The difference between the two readings is the only evidence that the work moved anything.
| Do this | Call | Why |
|---|---|---|
| Read the same numbers again | GET /org/analytics/summary | Re-observation is stage 02 run after publishing. The difference is the evidence. |
| Compare against module 2, not against zero | GET /org/analytics/prompts | A number with nothing to compare it to is not a result. |
| Give models time to re-crawl | A same-day reading measures the crawl, not the change. | |
| Feed what you learn into the next Evaluate | The loop restarts at this stage rather than ending here. This module has no CLI. |
What you do
- 1Re-run the same questions on a schedule.Same questions, same models. Changing them makes the comparison meaningless.
- 2Compare against your baseline from module 2.Citation lift, answer quality, and whether agents are crawling what you shipped.
- 3Record model answers as observations.Store them separately from your approved sources. They are evidence, not truth.
- 4Turn what you find into the next set of gaps.Feed them back into module 2. That is what makes this a loop.
- 5Check context before a consequential action.Price, policy, product details, eligibility, terms, and who is authorized. Then attach the receipt.
What you measure
Mention rate
Whether you were named at all.
Citation Rate
Of answers that cited anything, how many cited your tier.
Citation Share
Of all citation instances, what fraction was yours.
Share of voice
Your presence next to competitors.
Average rank
Where you appeared in the answer.
Crawl activity
Whether agents are fetching what you published.
Being mentioned and being cited are different, on different denominators. Improving one does not automatically improve the other. Analytics has the exact math.
What is not promised
That models will cite something new within any fixed period. The claim is narrower: what a model says about you can be traced to something you published, and you can measure whether publishing moved it.
The rule that protects everything upstream
Observation vs ground truth
Your approved records are the source of truth. Model output is an observation. An observation decides what to work on next; it never overwrites a source.
Full definition →A model answer that contradicts your context layer means something needs attention, not that your records are wrong. Write observations into your sources and the context layer degrades into whatever the open web already believed.
Before an action completes
Same context layer, different job. Before a booking, quote, application, product selection or checkout, verify what supports it, then attach the receipt so you can prove afterward what the decision was based on.
How to reach it
/org/analytics/summaryOpen in API reference →The rollup: mentions, citations and share, over a window you choose./org/analytics/citations/domainsOpen in API reference →Citation Coverage per domain. Whether your own pages are the ones cited./org/analytics/citations/pagesOpen in API reference →Down to the individual page, so you can see if what you shipped is working.Done when
- The same questions run on a schedule, so change is measurable
- Model answers are stored as observations, separate from approved records
- A consequential action checks current context before it completes
- The cycle produced the next set of gaps, not just a report