This page is the operator handover: what is complete, what passed, what can be shown now, and what Craig needs to handle before production traffic. The operator date above is when this page was last date-checked; it is not a re-verification date. The live claims below — deploy state from the Cloudflare API and the live domain, lead capture from an endpoint preflight — were last probed on . Counts tagged on this page are re-derived from the tree on every build. The Completed notes and Craig's later list are carried forward and not re-probed since that date.
The current build is usable for local demos, partner conversations, product review and paid-client preparation.
MASNAP, freight, haulage, future transport, M&A, revenue routing and user-view shelves are all represented, plus FormSnap, AddressSnap, HRSnap and ReceiptSnap as the wave-2 partner-replacement layer. Counted from the 22 tool pages in _site/snap/ — 30 files, less index.html and the seven suite shelves (user-view, future, scoreboard, ops, competitors, revenue-plan, leads).
21st.dev, Magic UI, Refero Design, GSAP, Three.js, Rive, Motion, shadcn/Radix and own-code policy are captured in the frontend design standard.
Offer, buyer, proof, CTA, capture, KPI, schema, LLM summary and weekly evidence hooks are enforced through QA.
Paid Client Delivery, Complete Launch Pack, Launch Control and client-ready boards are in place for partner fulfilment.
The restaurant QR menu now stores local order previews, opens WhatsApp or email fallback, and has a campaign/product route in Launch Control.
Incorpwise, Supreme Advisory and Supreme Building now have one.com/Krystal-ready export zips with fallback form handling.
A1 Elite, Proact Security, British Steel Homes, Begbies, Leyton and referral funnels now keep local fallback leads and mail handoff links on static hosting.
The location pages now keep local preview leads and email handoff links instead of relying on Netlify-only form capture.
Demos, client pages and public non-client pages now have JavaScript syntax validation in the main QA chain.
Resolved 15 June, not outstanding. _site/attoh-lead-config.js runs in edge mode against the canonical attoh-capture Supabase function, which writes to ad_leads. It is public by design, so no routing token and no server env vars are needed. Last probed : the CORS preflight answered 200.
Homepage, Snap, restaurant, configurator, partner, client and location leads keep a local fallback copy alongside live persistence, and both remain readable in Launch Control and Snap Lead Preview.
Critical control pages no longer use a tall sticky mobile nav that traps Launch Control actions.
Client pages cannot publish unsourced aggregate rating schema, and public launch pages cannot ship old fake WhatsApp contact numbers.
Demo personaliser, ecosystem, intake, live proposal and Ireland local SEO pages are now revenue-ready and protected by QA.
Pricing, GBP, compare, pipeline, content, ROI, reviews, audit, report, outreach and FAQ routes are now buyer-facing utility pages.
Future apps, transport automation, AI agents, agentic payments and M&A opportunity intelligence are presented as a forward-looking suite.
User View, Future Apps, Scoreboard, toolkit/local, utility and partner export generators were updated so rebuilds do not regress back to old copy.
These require owner access, live accounts, commercial decisions or production infrastructure.
The routing question below was open on 10 September; re-probed 18 September it is resolved. The Cloudflare Pages project attohdigital now serves this repository, not the internal operations repository's _web/portal-netlify/ folder.
/, /products, /robots.txt, /sitemap.xml, /ronaldo-handover, /launch-control, /configurator, /complete-launch-pack and /client-ready all return 200 on attoh.digital, and the content (this page's own attoh:human-verified stamp, the 561-URL sitemap) matches this repo's build, not the operations repository's.main, GitHub source ATTOH-DIGITAL/Attohdigital, build command npm run check:publish, output directory _site. The build command is narrower than the npm run check named here on 10 September — see the corrected trap note below.npm run check:publish (scripts/publish_gate.py), which gates only artifact existence, anti-regression size, secret hygiene and cache-buster correctness — not the full ~110-check npm run check suite. A red npm run check blocks merges to main, but no longer by itself freezes the live site once merged; only a red check:publish does that.Provide logos, colours, phone/email, services, review links and real proof for Incorpwise, Supreme Advisory and Supreme Building.
Confirm Google Business Profile and Trustpilot account access so aftercare can request and track reviews properly.
Confirm pricing bands, deposits, partner commission splits and which paid offers can be sent first.
All 15 routes below resolve in _site/, which the link check re-confirms on every build. On the live probe every one also returned 200 on attoh.digital — the routing question that used to keep them off the apex domain (see the resolved card above) is closed.
Operator date: 19 October 2026