Design system / Guides

Use the right structure.

Architecture, account boundaries and security acceptance

Adopted visual standards, tool roles and workflow examples from the reviewed guide.

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

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.

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.

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.

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.

Roadmap v1 and CTO handoff · Sixteen service contracts

Install Ecosystem

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