Design system / Companion guides

Roadmap v1.

Preserved delivery context. The roadmap is a companion to the design service.

JET’S ROADMAP v1 · ADOPTED DELIVERY GUIDELINE · 31 OCTOBER 2026

Nine milestones. One shared foundation.

For the CTO, technology and AI/automation delivery, and participating entities. Follow Milestones 1–9 in order. Each milestone reuses the shared foundation; services are built once and extended for permitted consumers. Requirements are adopted; completion needs its own evidence.

Read the CTO guide and source wording · Inspect the 16 service contracts · Tool roles and build method

Architecture reference supplied by Jet
Target architecture: eight ecosystem groups consume sixteen shared services above one governance spine. The milestone sequence is listed separately below.

Target architecture, not a verified live inventory. Wayfarer remains the worldwide-travel group; no numbered milestone was assigned to it. The image uses Utanon; Milestone 9 retains Jet’s requested Utan v1.

  1. Milestone 1: Zuporta v1

    US sme’s support

    Jet’s scope: One-stop US sme’s service based business solutions. Focus on speed, mobile-first (PWA), and convenience.

    Must-have shared services:

    • Identity & Accounts
    • Rewards & referrals
    • Design System
    • Support Desk
    • Operator Console
    • Messaging & Consent
    • Agent Gateway

    Suggested completion evidence: 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.

    Scope adopted · milestone acceptance not established. Design System: Jet reports Done; visual-preview QA passed conditionally. This is not evidence that the entire ecosystem design/PWA service is live.

  2. Milestone 2: Move v1

    Jet’s scope: pH workforce mobilization & global training competency.

    Must-have shared services:

    • Reviews & ratings
    • Workforce & Dispatch
    • Trust and verification
    • Contracts, e-signature

    Suggested completion evidence: 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.

    Scope adopted · milestone acceptance not established.

  3. Milestone 3: Plain Decision v1

    Jet’s scope: sme PWA Saas(hercules.app-style) + (preuve.ai-style)Fully Unlocked Validation/Analytics and metrics Dashboard

    Must-have shared services:

    • Analytics and metrics
    • Trust and verification
    • Credentials (W3C VC)
    • Search and AI visibility
    • Payments and ledger
    • Catalog, orders, claims

    Suggested completion evidence: 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.

    Scope adopted · milestone acceptance not established.

  4. Milestone 4: Eld

    Jet’s scope: Entertainment-talent bookings, celebrity requests, events, festivals, tickets, memberships and hosted paid experiences. Generic business support remains under Zuporta; travel remains under Laag and Wayfarer.

    Reuse the shared foundation. Additional service scope awaits the milestone brief.

    Suggested completion evidence: 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.

    Scope adopted · milestone acceptance not established.

  5. Milestone 5: Move v2

    Jet’s scope: Credentials: RWA on NFT as ID

    Reuse the shared foundation. Additional service scope awaits the milestone brief.

    Suggested completion evidence: 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.

    Scope adopted · milestone acceptance not established.

  6. Milestone 6: Laag v1

    Jet’s scope: Value proposition and MVP details not yet specified.

    Image reference: Philippine travel

    Reuse the shared foundation. Additional service scope awaits the milestone brief.

    Suggested completion evidence: 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.

    Scope adopted · milestone acceptance not established.

  7. Milestone 7: Dagan v1

    Jet’s scope: Value proposition and MVP details not yet specified.

    Image reference: Vehicles and drivers

    Reuse the shared foundation. Additional service scope awaits the milestone brief.

    Suggested completion evidence: 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.

    Scope adopted · milestone acceptance not established.

  8. Milestone 8: Prutas v1

    Jet’s scope: Value proposition and MVP details not yet specified.

    Image reference: Produce marketplaces (Prutas and Utanon group)

    Reuse the shared foundation. Additional service scope awaits the milestone brief.

    Suggested completion evidence: 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.

    Scope adopted · milestone acceptance not established.

  9. Milestone 9: Utan v1

    Jet’s scope: Value proposition and MVP details not yet specified.

    Image reference: Image names the group Prutas and Utanon

    Reuse the shared foundation. Additional service scope awaits the milestone brief.

    Suggested completion evidence: 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.

    Scope adopted · milestone acceptance not established.

Shared-service requirements in Jet’s wording

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.

Milestone 3 data-source requirement: Most suitable/fit/reliable ideally free or at least minimal setup and sustainable long term

Rules for CTO and automation delivery
  • Keep the numbered order. Technical prerequisites may be prepared earlier without declaring a later milestone launched or complete. Record scope changes and Jet’s decision.
  • Reuse one shared service contract with organization, app and role boundaries. Revalidate Trust and verification in Milestone 3 rather than building a second identity system.
  • Keep the current project tracker. Link each task to its milestone, owner, source, dependency, acceptance evidence and release authority.
  • Run bounded automation with an official record ID, scoped credentials, duplicate protection, retries, failure alerts, audit history and an authorized human stop/override. Timeout after 72 hours escalates or expires; it never approves.
  • Fully unlocked means the customer’s authorized features and results. Plain Decision owns its native Preuve-style dashboard; style references do not establish external partnerships.
  • For data/provider choices, record provenance, rights, quality, freshness, coverage, integration cost, recurring cost, entitlement, export and fallback. Free is a preference, not verified availability.
  • Carry the final-QA limits: preview dashboard API is unconfigured (503); the skip link works with a moderate landmark advisory. No shared-account or production acceptance follows from visual QA.

ROADMAP v1 · PREPARED HANDOFF

Lemuel and his AI: start here.

Lemuel Duyag is the CTO. This handoff connects the adopted roadmap, architecture reference and QA evidence with his technical delivery and chosen AI assistant.

Open the CTO + AI handoff in Linear ↗ · Open ELD-28 and the handoff ZIP ↗

Linear workspace access is required. In ELD-28, open Resources → Lemuel + AI — Roadmap v1 handoff pack. The private AI brief and source index stay in the handoff package.

For Lemuel

Read 00-START-HERE.md. Reconcile the two existing CTO handoffs and current source before reopening work. Choose one bounded implementation task with an owner, acceptance evidence and actual release authority.

For his AI assistant

Use the complete package and 01-AI-TASK-BRIEF.txt. First reconcile Milestone 1’s seven services read-only, then return 02-RESULT-AND-DECISION-TEMPLATE.md with evidence and one recommended customer-support pilot. Missing source access stays explicit.

What is included and what happens next

Human brief, AI task brief, seven-service worksheet, result template, source index, roadmap, architecture image, visual standard, final-QA evidence and the two earlier opening briefs. The ZIP’s integrity and thirteen file hashes were checked.

Prepared and available in Linear does not mean received, accepted or executed. Follow the nine milestones in order, reuse the sixteen services, and keep one tracker and one writer per checkout. Production and live automation retain their actual authorization and acceptance requirements.

Install Ecosystem

Installation is optional. Account access still needs an internet connection. Offline mode shows guidance only.