PLAIN DECISION ECOSYSTEM

Design system

Simple surfaces. Clear actions. Room to focus.

Shared components and guidance. Open the section you need.

Shared services / Design System
One foundation. Each app’s own identity.

ECOSYSTEM DESIGN SYSTEM · VISUAL BASELINE v1.0

One foundation.
Each app’s own identity.

Clear interfaces across the ecosystem. Shared behavior, distinct brands, and access only to the work each person is permitted to do.

Shared reference · ecosystem adoption tracked separately

Updated 31 October 2026. This catalogue distinguishes the Move reference components, existing partial services and planned contracts. Shared login, cross-app adoption and product acceptance require separate evidence.

Start simple. Open the detail you need.

ADOPTED BASELINE · VISUAL & TOOL MAP STANDARD v1.0

Start simple. Open the detail you need.

Jet approved this baseline on 31 October 2026. Group by purpose, explain the job, and show one concrete example. Use the format that helps the task.

Choose a useful visual
  • Relationships: a system map.
  • Handoffs: swimlanes with owners.
  • Choices: a decision tree.
  • Work: Kanban in the established tracker.
  • Real metrics: a dashboard with sources and dates.

A small list can stay a small list. Do not invent work, metrics or a second tracker to fill a visual.

Read the state before relying on it
Proposed
An idea or example awaiting a decision.
Prepared
A reviewable change or guide exists.
Tested
Named checks passed under recorded conditions.
Live
Deployed behavior has been verified.

Official records hold the decision or transaction. A link points to a record; a notification tells someone about it. Neither creates a second official record.

Improve the standard with evidence

A replacement version must demonstrate better understanding, usability, accessibility, reliability, cost or maintenance effort. Document the comparison, tradeoffs and adoption decision. Retain v1.0 for comparison.

Policy adoption does not establish live implementation. This preview awaits release authorization.

Read the complete v1.0 standard · Open tool guidance · Follow a handoff

What each tool is here to do.

PURPOSE BEFORE PROVIDERS

What each tool is here to do.

Approved roles, not a claim that every account or connection is enabled. The existing Move site remains on Vercel.

Run → build → guide. Add another tool only for a clear gap. Open a purpose, then a tool.

Run the apps Serve the app and protect its records.
Cloudflare
Job
Deliver pages, apply configured traffic protection and host compatible apps.
Example
Serve a pilot app and apply the traffic rules the team has actually configured.

Approved role. Move Team currently uses Vercel; no hosting move is implied.

Official documentation for Cloudflare ↗
Supabase
Job
Provide new-pilot login, records, files and enforced organization, app and role permissions.
Example
A customer sees their requests; assigned support sees permitted cases; an admin manages only their authorized organization.

Default for new pilots: one identity system, different access. Database and file policies enforce the boundary.

Official documentation for Supabase ↗
Build and improve Make changes, check them and release deliberately.
GitHub
Job
Keep source, reviews, checks and releases together.
Example
Review a branch, run checks and retain the commit behind a release.

Source and release history remain here; this does not replace the established project tracker.

Official documentation for GitHub ↗
ChatGPT / Codex
Job
Build the change and verify how it behaves.
Example
Build a request form in a preview and check narrow screens and denied access.

A generated answer or passing local test is separate from a verified live result.

Claude
Job
Review a prepared change or plan.
Example
Review a preview and its evidence; record findings and fixes.

Review role preserved. Review is claimed only when a receipt exists; it is not an automatic publication gate.

n8n
Job
Move work between approved systems with retries, duplicate protection and failure alerts.
Example
After an official request is saved, send one permitted handoff; retry safely and alert the owner if it fails.

Prepared pattern. A diagram is not a running workflow. Verify credentials, idempotency and failure handling before activation.

Official documentation for n8n ↗
Guide the team Keep decisions understandable and work easy to follow.
Notion
Job
Keep the handbook, procedures, training and decisions.
Example
A teammate opens the current procedure and records an agreed decision.

Retain the established project tracker. A new map does not create a second tracker.

Official documentation for Notion ↗
Google / Gemini
Job
Prepare suitable working documents and research.
Example
Compare sources in a working document, then link the adopted decision from the handbook.

Keep drafts and research distinct from approved records. Respect source permissions.

Official documentation for Google / Gemini ↗
Add only when needed Fill a demonstrated gap without duplicating working tools.
Clerk
Job
Use as an alternative identity provider when already working or justified.
Example
Keep an existing working Clerk app while assessing whether a migration has a real benefit.

Choose one identity approach for the app across customers, support and admins. Do not split providers by user type.

Official documentation for Clerk ↗
Email provider
Job
Send required account or service messages through a suitable provider.
Example
Deliver a recovery message or a permitted request receipt, then check delivery and retry behavior.

Select only when required. Verify sender/domain setup, consent, account entitlement, limits and billing.

Specialist provider
Job
Supply a capability the current tools cannot meet well.
Example
Add a payment or scheduling provider only when the pilot needs that capability.

Document the gap, compatibility, permissions, cost and exit path before adding it.

Proposed example

One customer request, one official record.

Illustrative new pilot. This is a handoff pattern, not evidence of a running customer service.

  1. Customer · request

    Sign in and save a request in the app. Supabase supplies the pilot identity, request record and file permissions.

  2. Assigned support · work

    Open only the cases permitted for this organization and app. Add an update to the official request record.

  3. Automation · handoff

    n8n uses the request ID to avoid duplicate work, retries safely and alerts the owner on failure. Email contains a permitted link or notification.

  4. Authorized admin · resolve

    Review exceptions within their assigned scope. The official app record holds the outcome; a notification is not the record.

Customers, support and admins share one identity system. Their organization, app and role permissions differ. Notion holds the procedure and decisions; the established tracker keeps delivery work.

Prepared guide

Prove one useful flow before adding more.

  1. Agree the outcome

    Name the user, one useful task, accountable owner, official record and acceptance evidence. Keep work in the established tracker.

  2. Check the current setup

    Inspect existing hosting and identity. Check current documentation, compatibility, billing, account entitlements and limits. Keep working infrastructure unless a change has a documented benefit.

  3. Build one guarded path

    Use the Supabase default for a new pilot unless a working or justified alternative fits better. Enforce organization/app/role access for records and files; test denied access too.

  4. Add reliable handoffs when needed

    Add n8n only for a needed handoff. Test retries, duplicate protection, failure alerts and the official record. Add email or a specialist only for a real requirement.

  5. Verify, review and release

    ChatGPT/Codex builds and verifies. Claude reviews when commissioned; retain its receipt. Check touch, keyboard, phone widths and the complete affected flow. Release only within the current authorization and record live evidence.

Nine milestones. One shared foundation.

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.
Lemuel and his AI: start here.

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.

One primary home per item. Link everywhere else.

INFORMATION & WORKFLOW STANDARD v1.0 · 31 OCTOBER 2026

One primary home per item. Link everywhere else.

Local system means the computer and its folders. These are the adopted jobs for the five tools; account setup, entitlements and live synchronization need separate evidence. GitHub remains the source-code and release-history owner.

Read the complete standard and image transcription · Follow client onboarding · Choose a visual

Google Drive — shared files
Best use cases
Contracts, proposals, presentations, spreadsheets, recordings, design assets, client deliverables. Collaborative editing through Docs, Sheets, and Slides.
Avoid
Tracking task progress through folders; storing several competing “final” copies; using spreadsheets as the permanent database behind your apps.
Zuporta onboarding example
Their signed agreement and deliverables.
Local system — workbench
Best use cases
Coding, testing, video/audio production, large working files, offline work, temporary downloads, independent backup copies.
Avoid
Keeping the only copy of company files; making teammates depend on access to your computer; running essential services that stop when your laptop shuts down.
Zuporta onboarding example
Working files used to produce the deliverables.
Supabase — live app records
Best use cases
Customer accounts, organization permissions, bookings, orders, referrals, transaction records, app uploads, and data your automations read/write.
Avoid
Everyday team documentation; manually managing project tasks in database tables; giving nontechnical staff database access for routine work.
Zuporta onboarding example
Their account and live onboarding status displayed in your app.
Notion — operating handbook
Best use cases
Strategy, decisions, roles, onboarding, training, SOPs, policies, meeting notes, and people development.
Avoid
Duplicating Linear’s task board; storing large media collections; using it as the transaction engine behind your customer apps.
Zuporta onboarding example
The onboarding procedure and quality checklist.
Linear — execution control
Best use cases
Projects, assigned tasks, deadlines, priorities, blockers, bugs, milestones, and delivery reviews.
Avoid
Course libraries, personnel files, contracts, company handbooks, or treating an ongoing department as a project with no finish line.
Zuporta onboarding example
The client’s assigned onboarding tasks, owners, and deadlines.

Use an existing Notion home page as the team’s front door, linking to the current handbook, Linear, Drive and app. A front door is navigation; it does not copy their records. This guide does not establish that the Notion page or any integration has been configured.

One client. Clear records and handoffs.

PREPARED WORKFLOW · ZUPORTA CLIENT ONBOARDING

One client. Clear records and handoffs.

  1. Notion

    Read the current onboarding procedure and quality checklist. Link the procedure version to the client’s Linear work.

  2. Linear

    Track the assigned onboarding tasks, owners, deadlines, blockers and acceptance evidence. Link the app record and Drive deliverables.

  3. Google Drive

    Keep the signed agreement and deliverables under the agreed access. Use their stable file links rather than copying “final” versions into every tool.

  4. Supabase / app

    Keep the account and authoritative customer-facing onboarding state in the app. Change it only when the defined business completion conditions have been verified.

  5. Local system

    Produce and test working files. Save accepted company deliverables in their shared home and keep managed backups; local work is not the team’s only accessible copy.

Connect task completion to app status without double entry

Define the required business checks first. A completed Linear task does not by itself prove customer onboarding is complete. An authorized automation may use stable client, issue, file and app-record IDs, verify the evidence, update the official app record, and acknowledge the result.

Choose a single writer for each field; keep scoped access, consent where needed, revision checks, duplicate protection, bounded retries and a failure alert. Display pending/failed synchronization honestly. Reconcile reversals and corrections with an audit trail. Staff update the owning record rather than maintaining two status fields manually. If automation is unavailable, use one accountable manual reconciliation owner and mark the linked view as pending.

Prepared design only: no n8n workflow, database write, consent grant or live synchronization is activated by this diagram.

Choose the visual by the need.

SUPPLIED IMAGE · EXACT TRANSCRIPTION

Choose the visual by the need.

Organize knowledge and courses

Best starting point: Collapsible taxonomy tree

Show connections across ventures

Best starting point: System map / network graph

Explain execution and responsibility

Best starting point: Swimlane diagram

Guide someone toward a choice

Best starting point: Decision tree

Control ongoing work

Best starting point: Kanban board

Monitor business results

Best starting point: Dashboard

Image note: Your recording combines three concepts: a hierarchical tree layout, expandable/collapsible interaction, and a taxonomy of personal development topics.

The note above is transcribed from the supplied image; it is not a claim that this review inspected the recording. Application guidance: use taxonomy trees for navigation, system maps for relationships, swimlanes for handoffs, decision trees for choices, Kanban in Linear for work, and dashboards only with real defined metrics and dated sources.

Source and implementation status

The five-tool roles and one-home rule come from Jet’s supplied text; the six visual rules and recording note come from his supplied image. Vendor documentation supports the capabilities; this allocation is the ecosystem’s operating policy. Prepared implementation notes are separate from observed live outcomes.

No files were migrated, access expanded, Notion home created or database/automation activated by this standards update.

Customers stay in their app.

DISTINCT EXPERIENCES

Customers stay in their app.

Customers register and work through their public app. The restricted operations portal manages shared services for approved strategic partners, team, support and internal roles. Shared infrastructure does not grant access to another app’s records.

Website purpose and access boundary
Website Experience Access boundary
business.zuporta.com Zuporta public and customer experience App-specific onboarding, membership and records
plaindecision.com Plain Decision public and customer experience The customer’s authorized results and features
ecosystem.plaindecision.com Restricted operations Explicit grants, active scope, native MFA and session checks
accounts.plaindecision.com Proposed neutral account address Not assumed provisioned or approved for callbacks
Other ecosystem apps Dedicated customer experiences Same service contracts, separately assigned permissions
How an app chooses its brand and policies

The server resolves a registered app from its fixed deployment configuration and validated origin. That configuration supplies stable app ID, approved domains, brand wording, callbacks, return destinations, onboarding, versioned terms, service settings and app policy. A browser-supplied app ID, role, tenant or return URL never grants authority.

Unapproved callbacks and incomplete terms keep account activation unavailable. Identity remains mapped by verified issuer and subject. Matching email addresses do not merge accounts.

Readable. Responsive. Ready for recovery.

REUSABLE BEHAVIOR

Readable. Responsive. Ready for recovery.

Use Move’s existing semantic tokens, original chess artwork, typography, spacing and Light / Dark / System controls. Public apps retain their own approved brand assets. Share form behavior, focus, feedback and permission states.

Try a sample form

Component demonstration only. Use fictional text. Nothing is saved or sent.

Required. Try leaving this empty to check the error summary.

Explore feedback states

Keep the next action clear, preserve the user’s input and explain permission limits.

Example ready

Choose a state or check the sample form.

Show the permitted working scope

Sample organization · Sample venture · Sample role

Internal screens must show the current organization, venture and permitted role. A partner sees only explicitly assigned functions and records. Displaying this sample does not create a role or grant access.

Accessibility and PWA acceptance

Use native controls, visible keyboard focus, linked error summaries, associated hints, accessible status messages, readable contrast and at least 44 × 44 CSS-pixel targets. Test reflow at phone widths and 200% zoom, both themes, reduced motion and keyboard navigation. WCAG 2.2 AA applies to complete processes; automated checks do not certify conformance.

Only explicitly approved public assets belong in an offline shell. Never cache tokens, authenticated responses or private files. Preserve the Book’s existing device saves and scoped service worker. Install, old-worker upgrade, assistive-technology and physical-device checks remain separate evidence.

The earlier research clarification for DS-027 and DS-033–035 remains: required accessibility behavior stays required even when a suggested implementation is optional. Media alternatives and motion preferences need their own checks.

The ecosystem map stays intact.

SEVEN GROUPS · ONE GOVERNANCE FOUNDATION

The ecosystem map stays intact.

Each group keeps its purpose and customer experience. The shared layer supplies permitted functions through secured interfaces.

  • MOVE
  • Eld
  • Zuporta
  • plain.decision
  • Prutas and Utanon
  • Laag
  • Wayfarer
  • Dagan
Dedicated apps → secured service interfaces → 16 shared services

Central governance supplies common controls. Each app supplies its own policy values. Every protected action checks the person, app, organization, venture and permission.

Preuve.ai is the native validation dashboard within Plain Decision. “Fully unlocked validation dashboard” means the customer’s authorized results and features; it does not unlock internal operations or other customers’ records.

A 72-hour approval timeout escalates or expires the request. It never approves automatically.

Sixteen services. Explicit boundaries.

CONTRACTS BEFORE EXPANSION

Sixteen services. Explicit boundaries.

Operation names below describe proposed interfaces, not deployed endpoints. “Partial” means relevant source exists; production operation and each app’s adoption still need evidence. This update does not authorize building every missing service.

Identity/accounts Partial

Interface: register · login · recover · revoke

Permitted consumers: Authorized customers in each public app; native-MFA staff through a separate boundary.

App settings: Issuer, callback allowlist, session lifetime, onboarding and terms version.

Existing Clerk mapping, staff guard and separate customer-account preparation. Cross-domain SSO unverified.

Trust/verification Partial

Interface: requestCheck · submitEvidenceReference · decide

Permitted consumers: Record owner and explicitly assigned verifier; consented public projection only.

App settings: Evidence class, expiry, reviewer and jurisdiction.

Existing governance and evidence controls; full provider verification not established.

Credentials Partial

Interface: request · review · publishProjection · revoke

Permitted consumers: Eligible holder and assigned reviewer; public display requires consent.

App settings: Eligibility, expiry, display consent and revocation wording.

Existing credential modules; real issuance and acceptance remain separately gated.

Payments/ledger Partial

Interface: quote · journal · reconcile · requestHumanAction

Permitted consumers: Scoped customer read models and assigned finance roles.

App settings: Merchant, currency, integer minor units, effective prices and manual approval.

Existing ledger models and reconciliation source. No payment execution added.

Rewards/referrals Partial

Interface: attribute · claim · evaluate · reverse

Permitted consumers: Assigned introducer, recipient and approved finance/operator roles.

App settings: Attribution window, single-level terms, rate, eligibility and refund rules.

Existing referral/shared-credit source and guarded RPCs; app activation needs evidence.

Workforce/dispatch Partial

Interface: requestAssignment · accept · updateStatus

Permitted consumers: Assigned worker, scoped coordinator and requesting customer.

App settings: Eligibility, availability, consent, escalation and assignment scope.

Existing recruitment/learning preparation; complete dispatch integration unverified.

Catalog/orders/claims Planned

Interface: listPublic · requestOrder · fileClaim

Permitted consumers: Public catalog readers and authorized order/claim participants.

App settings: Catalog ownership, currencies, stock, claim windows and allowed transitions.

Contract preserved; no new order, fulfillment or claims backend in this task.

Messaging/consent Partial

Interface: recordConsent · checkSuppression · draft · requestSend

Permitted consumers: Consenting recipient and explicitly assigned sender/support role.

App settings: Channel, purpose, terms, suppression, retention and approved delivery.

Existing consent, nurture and email preparation; real delivery remains gated.

Reviews/ratings Partial

Interface: requestEligibleReview · submit · reply · project

Permitted consumers: Eligible completed-service customer, scoped owner and public approved output.

App settings: Completion evidence, display consent and abuse handling.

Existing review modules and public sourced feedback. No fabricated ratings or AggregateRating.

Search/AI visibility Partial

Interface: projectPublic · sitemap · metadata

Permitted consumers: Public visitors and approved crawlers; authorized publisher.

App settings: Approved domains, indexing, source attribution and publication consent.

Existing public metadata and sitemap; no private indexing or new export.

Agent gateway Planned

Interface: discoverPermittedTools · requestDraft · requestReview

Permitted consumers: Explicitly authorized agents with bounded tool and record permissions.

App settings: Tool allowlist, data class, cost ceiling and human approval.

Architecture contract only; no gateway activation or access grant.

Analytics/metrics Partial

Interface: recordAllowedEvent · aggregate · scopedReport

Permitted consumers: App owner and assigned analyst; consented pseudonymous events only.

App settings: Event/property allowlists, lawful purpose, retention and denominators.

Existing analytics/KPI modules. Models and targets are distinct from measured results.

Design system/PWA kit Move reference implemented

Interface: tokens · forms · feedback · scopeDisplay · publicShell

Permitted consumers: Each registered app through its own adapter and original branding.

App settings: Theme, original assets, accessibility, app routes and public-cache allowlist.

Move tokens reused; component gallery and form behavior checked. Cross-app adoption and PWA acceptance need separate evidence.

Contracts/e-signature Partial

Interface: prepareExactText · review · recordHumanSignature

Permitted consumers: Named parties and assigned reviewers within the approved document scope.

App settings: Version, jurisdiction, signer authority and retention.

Existing exact-text/sign-off modules; no signature or legal-effect activation.

Support desk Partial

Interface: openTicket · assign · reply · requestDataReview

Permitted consumers: Requester and explicitly assigned support; app/organization/venture boundaries.

App settings: Routing, escalation, retention and authorized disclosure.

Existing support/CRM/chat preparation. No outbound message or live ticket created.

Operator console Partial

Interface: listAssignedScopes · readPermittedRecords · requestAction

Permitted consumers: Approved strategic partner/team/support roles with native MFA and active grants.

App settings: Function/record grants, role, idle/absolute expiry and audit.

Existing guarded portal source and live staff helper; full release acceptance unverified.

Shared request and response contract

A service request carries an operation, app context, tenant and venture scope, input and an idempotency key where needed. The server resolves identity and validates scope against authoritative membership, policy and grants. Browser claims cannot supply authority. Responses return only permitted records, scoped pagination, clear refusal codes and minimal audit references. Sensitive input and tokens stay out of logs and analytics.

Use explicit unavailable, unauthenticated, permission-denied, stale-policy, conflict and retry states. Null commercial policy disables dependent behavior; it never implies a free price or an approved rate.

Register once is the target.

SHARED ACCOUNT · SEPARATE PERMISSIONS

Register once is the target.

For a new pilot, use one identity system for customers, support and admins, with different organization, app and role permissions. Supabase is the default. Branding, onboarding, terms, memberships and records remain app-specific.

Adopted new-pilot default

Supabase: one identity, scoped access

Use Supabase for login, records and files. Enforce organization, app and role permissions for every protected operation. Support and admin capabilities require explicit grants; a role label in the interface never grants access.

Alternative when justified

Retain a working Clerk installation

Use Clerk when already working or when its benefit is documented. Do not split providers by user type. Existing installations remain intact while any proposed migration proves identity continuity, compatibility, current billing and account entitlements, security and rollback.

No new identity provider, automatic migration or account linking is implemented here. Customers and strategic partners do not gain internal privileges through public-app login or business ownership.

Callbacks, sessions and logout

Use provider-supported authorization, exact approved callbacks, state/CSRF protection, PKCE S256 and nonce where applicable. Keep refresh tokens and secrets server-side, out of URLs and frontend bundles. accounts.plaindecision.com remains a proposal.

App logout: clear and invalidate the selected app’s session and private UI state. Ecosystem logout: revoke relevant provider and app sessions across participating apps, then confirm completion. A cleared cookie alone is not proof of global revocation. Existing access-token lifetime and offline tabs may delay complete rejection unless sensitive operations check revocation online.

Internal actions still require the applicable MFA, active-grant and session checks. Preserve existing authorization controls during any transition. Reusing an identity does not reuse another app’s permissions.

Current official documentation
Know what has been checked.

EVIDENCE BEFORE ACCEPTANCE

Know what has been checked.

Implemented in this Move reference

Updated Move Team catalogue, preserved ecosystem map, shared feedback and form behavior, safe scope display and a server-only app configuration contract. Local checks are recorded in the review package.

Requires separate test evidence

Real registration, recovery, cross-domain session reuse, provider logout/revocation, deployment acceptance and physical-device checks. No SSO or production-readiness claim is made.

Required security checks cover guests, internal page/API/database denial, cross-organization and cross-venture isolation, role tampering, callback rejection, revoked sessions and removed staff grants. Existing intake, referral, CRM and shared-service behavior must retain its own regression evidence.

Security advisories need context

Private tables with RLS and no client policies may intentionally deny direct access. Inspect grants and privileged-function authorization before changing a warning. Preserve identity mappings and authorization helpers; never remove a control just to clear an advisory.

Source records and ownership

Source records and ownership

This implementation guide retains the original source permissions and earlier research distinctions. Jet’s direct October 31 adoption of Visual & Tool Map Standard v1.0 defines this update; linked Notion records continue to own their other approved requirements.

This catalogue documents the design foundation. Authentication, data, subscriptions and access retain their separate controls. Human usability studies and independent product acceptance remain separate.

Eight ecosystem groups.

Approved architecture · 5 November 2026. Configuration describes intended ownership; each integration needs separate evidence.

Zuporta: Diagnostic → Action Plan → approved delivery. plain.decision: reusable business-validation software and evidence dashboard. MOVE prepares the workforce; Zuporta delivers business services. Eld owns entertainment bookings and hosted experiences; Laag and Wayfarer own travel.

Reuse sixteen shared services. Separate app permissions and records. No duplicate delivery or billing. Central standards and per-app policy values remain in force. Unanswered gates expire after 72 hours; silence never approves.

For app owners and builders

Use a pinned version.

Import the package into your build and serve its assets from your app’s origin. The gallery uses the same portable modules. Apply component styles beneath .ds-page; map --eco-* tokens to an approved app theme.

<link rel="stylesheet" href="/shared/design-system/v1.0.0/tokens.css">
<link rel="stylesheet" href="/shared/design-system/v1.0.0/components.css">
<!-- Also load visuals.css when using the view-switcher patterns. -->
<link rel="stylesheet" href="/shared/design-system/v1.0.0/visuals.css">
import {bindForm, setFeedback, displayScope, bindViewSwitcher}
  from '/shared/design-system/v1.0.0/components.mjs';

The server must provide authorized scope and enforce access. Scope text is presentation only. This package does not install authentication, data synchronization, offline caching or a service worker.

Read the service contract and asset entry points

Install Ecosystem

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