Welcome page A

This is the dashboard. Notice that no SMTP form lives on this page -- it is on the Settings page (page B). Yet the autopilot below can satisfy the intent "configurar SMTP" by reading the sitemap, planning the navigation, and continuing the work after the page break.

Open the browser console on both pages to follow the NAC events. The log box at the bottom of each page narrates the autopilot decisions.

Autopilot trigger

Click the button. The autopilot will:

1. Inspect describe_v2()'s visible tree (no SMTP slug present here).
2. Read describe_v2().sitemap and find settings.system.smtp.
3. Walk the path's affordance_to_navigate and dispatch the cross-page click.
4. Page B picks up ?nac_autopilot=smtp_demo and finishes the form.

Autopilot log

Newest entries on top. Each line shows the step the runtime took. STEP 1 will report "tree contains settings.system.smtp? false" -- correctly -- and STEP 4 will print the affordance_to_navigate from the sitemap.

(idle -- click the button)

What this proves

• Tree is authority. The intermediary NEVER invokes a slug not in the visible tree at dispatch time. Sitemap is metadata.
• Plan before act. Cross-page navigation is a planned sequence: each step re-validated on its own page.
• No client-side state. The intent transfers via a URL query (HTTP-native). Sticky session / localStorage / cookies optional.
• LLM contract. The same sitemap that the autopilot reads here is what a chatbot sees in its system prompt -- both classes plan identically. Equality of access (RFC sec 0a).