Overview
Step-by-step guide for monitoring source, published output, AI-answer, and action-path drift.
- Complete prerequisites before changing public outputs.
- Publish only approved data and action paths.
- Run checks and retests before treating the work as ready.
Prerequisites
You need an Akii account, a client brand, the client website or source material, permission to publish approved client data, and access to any booking, checkout, quote, call, WhatsApp, or form destination you plan to map.
Steps
Follow the steps in order. If a step exposes data publicly, pause until the agency, client owner, or approved operator has reviewed it.
- Review output health.
- Compare public sources against approved graph fields.
- Run AI answer checks for priority journeys.
- Inspect action-path test results.
- Move confirmed mismatches into Fix Queue.
Expected result
The expected result is an approved, versioned, and retestable workflow. A human should understand what changed, and an AI system should have a clean, approved way to read the same facts.
Common errors
Most failures come from missing source proof, stale public pages, ambiguous prices, broken action links, unsupported payment claims, or treating unapproved work as published.
- Missing owner or approval state
- No preferred source for a critical fact
- Action path exists but has not been safely tested
- Protocol readiness is treated as certification
- Private notes are accidentally included in public outputs