The five checks, plus a final look
01 / ASKSay what you are trying to decide.
02 / DEFINEName the account, dates, item, numbers, and answer format.
03 / FINDUse the system that keeps the facts you need.
04 / CHECKMake sure the information is current and fair to compare.
05 / DECIDESuggest a next step, a person, and the approval needed.
06 / LOOK AGAINCheck the live result after an approved change.
Authority map
| Question | Start with | Then add |
|---|---|---|
| How did the ads do? | Xnurta advertising results, such as get_ads_perf. | Campaign details, change history, stock, margin, or listing details when needed. |
| What is this campaign or product? | Campaign details, such as get_entity_metadata. | Advertising results and change history. |
| What changed in the account? | Change history, such as get_operation_log. | Results before and after the change. |
| Can we ship it or make money on it? | Stock, operations, finance, or warehouse records. | Advertising numbers alone cannot answer the whole business question. |
Handoff card
WHERE IT CAME FROMSource, account, dates, when you looked, and how current it is.
WHAT HAPPENEDWhat changed and which number shows it.
WHAT MIGHT EXPLAIN ITPossible reasons and the checks still open.
NEXT STEPSuggested action, person responsible, approval, and expected result.
CHECK AGAINWhen and how you will look at the result after the change.
WHAT WE DO NOT KNOWWhat this look-up did not cover.
Xnurta boundary
The published Xnurta 1.0.0 guide describes a look-up-only service. Use it to see and explain information, then prepare a next step. Make any real change in the approved system and workflow.
Sources: MCP architecture, Xnurta user guide, and Amazon Ads documentation.