Change Monitoring Test Page
Revision 2 — last updated 14 July 2026
This is an internal test page. It has no marketing purpose — it exists so the team can verify that GLUCOSE automatically notices when a web page it has ingested into a knowledge base later changes, and refreshes the stored copy on its own.
How the test works
First, this page is onboarded as a web-sourced corpus document. GLUCOSE scrapes the content, splits it into passages, embeds them, and starts watching this URL for changes. Later, someone edits the text on this page and publishes it. Within the monitoring window the change is detected and the corpus document is re-scraped and re-embedded in place — no duplicate document is created, and the "last changed" timestamp advances.
Sample content
This paragraph was rewritten in Revision 2 to give the change monitor a clear, meaningful difference to detect. Support teams spend a large share of their time answering the same questions: order status, refund eligibility, appointment rescheduling, warranty coverage, and basic troubleshooting. Our updated guidance is that assistants should always confirm the customer's order reference before quoting a specific refund window, because refund windows now vary by product category.
Keeping that knowledge fresh is the hard part. Product details change, policies get updated, and pages get rewritten — and a stored copy that is never refreshed slowly drifts out of date. Automatic change-monitoring closes that gap by refreshing a document whenever its source page changes, instead of relying on someone remembering to re-import it by hand.
Revision history
Revision 2 (14 July 2026): rewrote the sample content — refund windows now
vary by product category and assistants must confirm the order reference
first.
Revision 1 (13 July 2026): initial version of the test page.
How to edit this page for the test
To simulate a source change, update the "Revision" number and the date in the subtitle at the top, add a new line to the revision history above (for example "Revision 2 (…): updated the sample content"), and change a sentence or two in "Sample content". Publish the change, then check the corpus document in the console — the monitoring status should show a new "last changed" time once the refresh completes.