# Jet's approved Visual & Tool Map Standard v1.0 Status: **ADOPTED BASELINE**. Authority: Jet's direct implementation request, 31 October 2026, Asia/Manila. Scope: `moveteam.plaindecision.com`. This version is distinct from practice Sequence #3 v1.0 and research QA revision 1.2. No standard attachment or approved-example attachment was available in this chat's accessible attachment directory. The instructions supplied directly by Jet are sufficient authority. Related earlier local research is not treated as an approved example. ## Inspect before changing Open the site, locate its actual source project, and read applicable agent instructions, design system, components, navigation and existing workflows. Inventory accessible sections and relevant nested pages. Record inaccessible areas without inventing coverage. Preserve working infrastructure and unrelated changes; continue accessible work when one area is blocked. ## Choose the useful format Use compact interactive collapsible trees with a simple overview and deeper details. Group by purpose. Tool maps use **Run the apps**, **Build and improve**, **Guide the team**, and **Add only when needed**. Give every tool a plain-language job and concrete example. Where useful, separate **Tool map**, **Customer example**, and **Build order** views. Use system maps for relationships, swimlanes for handoffs, decision trees for choices, Kanban for work, and dashboards only for real metrics. Inspect onboarding, training, procedures, roles, projects, tool guidance, automation and roadmap sections; apply only the formats each section needs. ## Approved tool roles | Tool | Role | | --- | --- | | Cloudflare | Delivery, configured traffic protection and compatible hosting. | | Supabase | Default new-pilot login, records, files and enforced organization/app/role permissions. Customers, support and admins use one identity system with different access. | | Clerk | Alternative if already working or justified; do not split providers by user type. | | GitHub | Source, reviews, checks and releases. | | n8n | Automatic handoffs with retries, duplicate protection and failure alerts. | | ChatGPT/Codex | Build and verify. | | Claude | Review. Do not claim review without a receipt. | | Notion | Handbook, procedures, training and decisions; retain the established project tracker. | | Google/Gemini | Suitable working documents and research. | | Email and specialist providers | Add when the task requires them, after checking current documentation, compatibility, billing and account entitlements. | Assess infrastructure changes on actual benefits. This baseline changes guidance; it does not itself migrate authentication, install providers, buy subscriptions or activate automations. Existing working infrastructure remains until a separately authorized change is justified and verified. ## Durable integration and accessibility Record this baseline in the existing design system and link it from project agent guidance. Reuse the product's brand and styling. Support mobile, touch, keyboard, visible focus and accessible expansion states. Keep official records, links and notifications distinct. Label **Proposed** (idea), **Prepared** (reviewable implementation/configuration), **Tested** (named checks and conditions), and **Live** (verified deployed behavior) separately. Adoption of a policy is not proof of live implementation. ## Verification and release Implement in an isolated branch/preview. Check interactions, narrow screens, navigation, affected workflows and relevant existing checks. Report changed sections, skipped/inaccessible areas, evidence and remaining dependencies. Leave a reviewable preview. Publish only when authorized. ## Replacement rule A replacement must name its version and demonstrate a benefit in understanding, usability, accessibility, reliability, cost or maintenance effort. Record baseline and candidate, task and device conditions, observed evidence, regressions and tradeoffs, and Jet's adoption decision. Retain this v1.0 file and comparison evidence. A new visual preference or untested proposal does not supersede this standard.