# Roadmap v1 — CTO and participating-entity guide Adopted by Jet on 31 October 2026. The nine milestone names, order, value propositions and must-have services below come from Jet's direct request. Preserve that scope. The supplied Ecosystem Map is an additional target-architecture reference. Acceptance checks and implementation instructions are editorial delivery guidance; they do not add approved features, appointments, deadlines or budgets. ## Authority and use This roadmap controls product delivery order. Visual & Tool Map Standard v1.0 controls presentation. Existing contracts, permissions and official records remain authoritative for their own subjects. Reconcile conflicts explicitly; do not silently substitute an older candidate roadmap, shorten the service list or turn a style reference into a dependency. CTO: reconcile current source, services, environment and active work; retain accepted modules and make one bounded milestone plan. Technology and AI/automation workers: execute assigned tasks against the same source/version and record evidence. Participating entities: agree actual responsibility, data contribution, authority and handoff before taking a role. These are responsibility categories, not appointments of named people or agreements with third parties. Jet identifies Lemuel Duyag as the CTO and says he uses AI; the existing Move Team profile already records that role. A dedicated human brief, portable AI task brief, source index and result template are prepared in the project's private `docs/design-system/lemuel-handoff/` folder. They supplement the two existing October 30 CTO packs. Begin with read-only Milestone 1 reconciliation, then let Lemuel select one bounded implementation task under actual authority. The packet being prepared does not mean it was sent, read or executed; the implementation prompt and private source index are not public website assets. Follow Milestones 1 through 9. Preparatory technical dependencies may be completed earlier when necessary, but do not launch, relabel or declare later milestones complete out of order. Existing commitments remain in force. Keep later products in discovery until their brief and acceptance conditions exist. A change to milestone order, product scope or architecture needs a recorded adoption decision from Jet. ## One foundation and explicit boundaries The image contains seven groups: MOVE; Zuporta + Talent Desk; Plain Decision; Prutas and Utanon; Laag; Wayfarer; Dagan. They consume sixteen shared services under one governance spine. Build a reusable service once, with per-app policy/configuration and authorized consumers; do not build nine disconnected backends or confer ecosystem-wide access by default. Wayfarer remains worldwide-travel architecture context without a numbered milestone. Milestone 9 remains Utan v1; the image says Utanon. Treat this as an unresolved naming relationship before changing identifiers/domains. Milestones 6–9 have names but no complete user-supplied MVP specification. Image context does not fill that gap automatically. Trust and verification appears in Milestones 2 and 3 deliberately: implement the shared foundation for Move, then extend/revalidate its permitted SME usage for Plain Decision. Basic identity security, operational logs and existing required transactions cannot be deferred just because a fuller module is scheduled later. M1 support can use authorized manual assignment until the M2 dispatch capability is accepted. New MVP scope must still respect the ordered roadmap. Plain Decision is the SME PWA/SaaS owner and owns the native Preuve-style validation dashboard. Hercules, Preuve, Cameo and Burning Man describe the supplied product/style references; no commercial relationship, API dependency or account entitlement is established. Fully unlocked means the customer's authorized features/results, never unrestricted internal or other-customer access. ## Existing tool and operating guidance Reuse approved tool roles: Supabase defaults for a new pilot's identity, records and files; one identity system across customers/support/admins with different permissions. Retain a working or justified Clerk installation. GitHub owns source/reviews/checks/releases; the established tracker owns delivery tasks. Notion owns handbook/procedures/decisions. n8n handles necessary handoffs with retries, duplicate protection and alerts. ChatGPT/Codex builds and verifies; Claude reviews when requested, with a receipt. No mandatory Claude code-review gate is added. Cloudflare's approved role does not require migrating the working Vercel site. Use Google/Gemini for suitable documents/research. Add email or specialist providers for demonstrated requirements only. Verify current docs, compatibility, entitlement and cost before actual implementation; no new spending is authorized by this guide. ## Task and automation contract Use the existing tracker, with a milestone link, agreed scope, accountable owner (unassigned until agreed), source/version, app/organization/access scope, dependency, acceptance criteria, evidence links, release authority and next action. Keep statuses separate: required → prepared → implemented → locally tested → hosted tested → reviewed where commissioned → accepted → live verified. A policy being adopted does not move every feature to implemented. An automation handoff needs its official record ID and source version, an exclusive writer/claim where concurrent runs could overlap, scoped credentials, an idempotency key, bounded retries/backoff, failure/dead-letter state, audit receipt, destination acknowledgement and a human stop/override. Do not replay ambiguous money, messages or grants blindly. Query the original result first. An operator may override only within assigned authority; being a founder is not an implicit grant. A 72-hour approval timeout escalates or expires, never approves silently. This guide creates no timer or workflow. ## Acceptance and data choices Suggested milestone checks below make scope reviewable; agree numerical performance targets, pilot users, actual owners and any commercial criteria in each milestone brief. For each must-have service, demonstrate its declared interface and permissions, one successful business path, denied/invalid input, failure/recovery, an official persisted record and the relevant operational evidence. Test customer, assigned support and authorized administrator paths as applicable. Attach release/source IDs and date/environment. Mobile-first/PWA claims require a phone journey, installation/update/offline behavior appropriate to the app and field acceptance evidence. For Milestone 3, Jet's data-source requirement is: "Most suitable/fit/reliable ideally free or at least minimal setup and sustainable long term". Compare fit, provenance, rights/consent, quality, refresh/freshness, geography/coverage, availability, setup effort, total recurring cost, quotas, export/portability and fallback. Prefer an existing suitable source over a duplicate subscription. Mark unknown cost/rights/quality as unknown. No vendor selection or free entitlement is established here. For Move v2, preserve the RWA/NFT-as-ID goal but commission a design that distinguishes asset representation, credentials, identity and authorization. Suggested safeguards: keep raw identity documents and sensitive personal data out of immutable public tokens; prove issuer authority, status/revocation and recovery; review custody, transferability, consent, cost and applicable obligations before real issuance. No asset/token issuance or wallet integration was implemented or authorized by this documentation task. ## Reconciliation with final QA Jet labels Design System Done. Preserve that user-reported status alongside the independently verified scope: the Move visual preview passed conditionally, forty pages returned 200, seven source regressions passed and the tested keyboard/mobile/demo/filter interactions worked. This is not acceptance of a complete shared design-system/PWA service in every app. The design guide's sixteen service contracts remain requirements/partial source, not sixteen live integrations. The review preview's /api/angelo returned 503 (Dashboard connection is not configured yet). Backend/shared-account acceptance remains unestablished. The skip link works but has one moderate axe landmark advisory. Private flows, real customer transactions, live automations, provider entitlements and physical-device/screen-reader acceptance need their own evidence. The earlier 21 browser tests concern the smaller replacement artifacts, not 21 Move-site journeys. Preserve originals and their inventories. First bounded next action: inventory Milestone 1's seven services against the current owning sources and existing CTO handoffs; record implemented/tested/live evidence and missing dependencies in the established tracker, then select one guarded customer-support pilot path. Do not claim that this planning document completes that inventory or implements those services. This change prepares the guideline in the existing isolated source candidate. Production publication, provider migrations, new access, billing, live automation and messaging retain their action-specific authority requirements. ## Milestone source wording Milestone 1: Zuporta v1 US sme’s support Core Value Prop: One-stop US sme’s service based business solutions. Focus on speed, mobile-first (PWA), and convenience. Must-Have Features (MVP Scope): Shared Services • Identity & Accounts • Rewards & referrals • Design System • Support Desk • Operator Console • Messaging & Consent • Agent Gateway Milestone 2: Move v1 Core Value Prop: pH workforce mobilization & global training competency. Must-Have Features (MVP Scope): Shared Services • Reviews & ratings • Workforce & Dispatch • Trust and verification • Contracts, e-signature Milestone 3: Plain Decision v1 Core Value Prop: sme PWA Saas(hercules.app-style) + (preuve.ai-style)Fully Unlocked Validation/Analytics and metrics Dashboard Must-Have Features (MVP Scope): Shared Services • Analytics and metrics • Trust and verification • Credentials (W3C VC) • Search and AI visibility • Payments and ledger • Catalog, orders, claims Milestone 4: Zuporta v2 Core Value Prop: Talent, operations, creators, business/leasure events[from local to global] and campaigns (Style: Cameo + burningman) Milestone 5: Move v2 Core Value Prop: Credentials: RWA on NFT as ID Milestone 6: Laag v1 Core value proposition and MVP scope not supplied. Milestone 7: Dagan v1 Core value proposition and MVP scope not supplied. Milestone 8: Prutas v1 Core value proposition and MVP scope not supplied. Milestone 9: Utan v1 Core value proposition and MVP scope not supplied. Data Source (Milestone 3): Most suitable/fit/reliable ideally free or at least minimal setup and sustainable long term Identity & Accounts: Handles user authentication, login providers (Google, email/password), session management, and user profiles across your apps. Rewards & referrals: Manages loyalty points, discount codes, user referral tracking, and invite incentives to drive user growth. Design System: (Done): https://moveteam.plaindecision.com/design-system Support Desk: The ticketing and help system where users submit bug reports, questions, or requests, and where you manage support responses. Operator Console: Central command center and human-in-the-loop dashboard where founders / authorize personnel monitor, manage, and override all automated workflows, apps, and agent systems. Messaging & Consent: system module that governs how your apps communicate with users and ensures you have explicit, logged permission to do so. Agent Gateway: The centralized API routing and security layer that manages communication between your autonomous AI agents, external LLM providers, and internal backend services. Reviews & ratings: The reputation and feedback module that aggregates customer ratings, star reviews, and text testimonials for your services Workforce & Dispatch: Tracks staff profiles, roles, availability, and permissions. Automatically or manually assigns incoming jobs, support tickets, or field tasks to the right person based on their skills and availability. Trust and verification: The security and compliance module that validates user identities, verifies business documents, and runs compliance or fraud checks across your platform. Contracts, e-signature: The legal and agreement execution layer of your ecosystem. Analytics and metrics: The telemetry and tracking layer for your apps. Credentials (W3C VC): The decentralized identity module that issues, holds, and verifies W3C-compliant Verifiable Credentials (digital badges, certificates, or verifiable proofs like professional licenses or completion certificates). Search and AI visibility: The optimization and tracking layer that ensures your apps, products, and services are discovered, indexed, and accurately cited by search engines and conversational AI models (like ChatGPT, Gemini, and Perplexity). Payments and ledger: The financial engine and system of record for tracking money movement, balances, and transactions across your apps. Catalog, orders, claims: The e-commerce and transaction management engine for your products or services. ## Suggested milestone completion checks ### Milestone 1: Zuporta v1 A customer signs in, submits a support request and receives a permitted acknowledgement. Assigned support resolves it; an authorized operator can inspect and stop the automation. Prove consent, referral attribution, duplicate prevention, failure handling and denied access. Record a phone/PWA journey and actual speed measurements. ### Milestone 2: Move v1 An authorized person verifies a worker, records training/competency evidence, obtains the required agreement, assigns a suitable available worker and records completion plus permitted feedback. Prove reassignment, document-access boundaries and the dispute/correction path. ### Milestone 3: Plain Decision v1 One SME completes an agreed PWA workflow and sees its own source-backed validation and metrics with dates and definitions. Verify credential issue/verification/status, discovery evidence, and a scoped order/payment/ledger/claim journey including retries, duplicate prevention and reconciliation. Unknown metrics stay unknown. ### Milestone 4: Zuporta v2 Define one expansion pilot, audience, delivery owner, consent, operating capacity, commercial terms and measurable outcome before building. Reuse accepted shared services. This description does not establish a Cameo or Burning Man partnership. ### Milestone 5: Move v2 Prepare the credential/asset model and prove issuer authority, holder control, verification, status/revocation, recovery, privacy and interoperability. W3C credentials and NFT identity are distinct mechanisms. Review ownership, transferability, custody and costs before any real issuance; the roadmap alone does not authorize minting or financial activity. ### Milestone 6: Laag v1 Agree the MVP user journey, accountable owner, data source, commercial/operational boundaries and acceptance evidence before implementation. Philippine travel is image context, not a complete product specification. ### Milestone 7: Dagan v1 Agree the MVP user journey, accountable owner, data source, commercial/operational boundaries and acceptance evidence before implementation. Vehicles and drivers is image context, not a complete product specification. ### Milestone 8: Prutas v1 Agree the MVP user journey, accountable owner, data source, commercial/operational boundaries and acceptance evidence before implementation. Reuse the shared catalogue, payments, trust and support contracts where required. ### Milestone 9: Utan v1 Preserve the requested name Utan v1. Confirm whether Utan and Utanon are the same product before changing domains, identifiers or records. Agree the MVP journey and acceptance evidence; do not silently rename the existing group.