# Information & Workflow Standard v1.0 Adopted for this ecosystem from Jet's supplied text and visual-selection image, 31 October 2026. This supplements Roadmap v1 and Visual & Tool Map Standard v1.0; it does not reorder milestones or claim configured integrations. ## One primary home per item; link everywhere else Local system means the computer and its folders. Google Drive owns shared file artifacts; the local system is a workbench and may hold managed backup copies; Supabase owns live app records; Notion owns the operating handbook; Linear owns execution control. GitHub continues to own source code, reviews and release history. A five-tool information rule does not relocate code into Drive or Notion. An approved reference, export or backup is labelled with its owning record, source version and snapshot date; it is not a competing editable master. Link to current sources and preserve access boundaries. Team-shared Drive availability depends on the actual Workspace edition, configuration and permissions. Never infer an account entitlement from the product's capabilities. ## Tool roles — supplied wording ### Google Drive — shared files Best use cases: Contracts, proposals, presentations, spreadsheets, recordings, design assets, client deliverables. Collaborative editing through Docs, Sheets, and Slides. Worst use cases / avoid: Tracking task progress through folders; storing several competing “final” copies; using spreadsheets as the permanent database behind your apps. ### Local system — workbench Best use cases: Coding, testing, video/audio production, large working files, offline work, temporary downloads, independent backup copies. Worst use cases / 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. ### Supabase — live app records Best use cases: Customer accounts, organization permissions, bookings, orders, referrals, transaction records, app uploads, and data your automations read/write. Worst use cases / avoid: Everyday team documentation; manually managing project tasks in database tables; giving nontechnical staff database access for routine work. ### Notion — operating handbook Best use cases: Strategy, decisions, roles, onboarding, training, SOPs, policies, meeting notes, and people development. Worst use cases / avoid: Duplicating Linear’s task board; storing large media collections; using it as the transaction engine behind your customer apps. ### Linear — execution control Best use cases: Projects, assigned tasks, deadlines, priorities, blockers, bugs, milestones, and delivery reviews. Worst use cases / avoid: Course libraries, personnel files, contracts, company handbooks, or treating an ongoing department as a project with no finish line. ## Zuporta client onboarding — supplied mapping 1. Notion: the onboarding procedure and quality checklist. 2. Linear: the client's assigned onboarding tasks, owners, and deadlines. 3. Google Drive: their signed agreement and deliverables. 4. Supabase: their account and live onboarding status displayed in your app. 5. Local system: working files used to produce the deliverables. Apply the prepared handoff pattern: 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. ## Automation and status ownership — implementation guidance Task completion and a customer's app status may be connected by automation, but define the business acceptance conditions first. Completing any one Linear issue cannot automatically mark every customer onboarded. The staff task status belongs to Linear; the live customer state belongs to the app. A link/projection shows the other record without introducing a second manual status master. Before implementation, name the workflow and actual owner, trigger, business conditions, current source and version, stable client ID, Linear issue ID, Drive file ID/link and app record ID, allowed fields and permissions, expected destination acknowledgement and rollback/correction path. Keep personal documents out of issue descriptions when a permitted Drive link is sufficient. Operators use the app rather than routine database-console access. Use one writer for each field, revision/conflict checks, idempotency, bounded retries, audit evidence, reconciliation and a failure alert. Process reopen/reversal/correction events with the same discipline; do not let delayed events overwrite newer accepted states. Pending/failed synchronization remains visible. Reuse the existing transaction/outbox/handoff owner; do not add a second sender. If automation is unavailable, choose one accountable manual reconciliation owner and label projections pending; do not require every staff member to maintain both stores. Acceptance before calling the connection live: demonstrate a valid completion, unmet prerequisites, duplicate event, retry after failure, revoked/wrong-organization access, stale update, corrected/reopened task and missing acknowledgement. Confirm only permitted customer fields appear in the app and that one official persisted result exists. This is a prepared workflow contract; no integration was activated by writing it. ## Team front door — navigation guidance Reuse an existing Notion home page as a single starting point with links to the current handbook, assigned Linear work, shared Drive artifacts and customer/operator app. Keep access permissions intact. A department is an ongoing team/function, while a Linear project needs a defined outcome and finish. Store courses, SOPs and people-development knowledge in Notion; assigned course-production or training-delivery tasks can link to it from Linear. No Notion home-page creation, migration, company-wide sync or live-account setup is claimed in this update. The repository holds the versioned implementation/review candidate; this app is a readable projection. Linear holds execution and a handoff reference, not a replacement company handbook. ## Supplied image — exact transcription | Need | Best starting point | | --- | --- | | Organize knowledge and courses | Collapsible taxonomy tree | | Show connections across ventures | System map / network graph | | Explain execution and responsibility | Swimlane diagram | | Guide someone toward a choice | Decision tree | | Control ongoing work | Kanban board | | Monitor business results | Dashboard | Your recording combines three concepts: a hierarchical tree layout, expandable/collapsible interaction, and a taxonomy of personal development topics. The final sentence is image content, not evidence that the recording was inspected. Source image is preserved with the private project reference snapshots. These six rows are adopted visual-selection guidance. Their implementation uses native collapsible reading sections; an actual system graph, decision tree, swimlane, Kanban board or dashboard is added only when the subject needs that format. Dashboards require real metric definitions, sources, dates and known limitations. Do not manufacture measurements or duplicate Linear's board to fill a screen. ## Provenance and current verification The five allocations and best/avoid examples are user-supplied operating choices. Vendor docs establish available capabilities; they do not mandate this exact division or prove your account is configured. Official references checked 31 October 2026: - [Google Workspace: shared drives](https://support.google.com/a/users/answer/7212025?hl=en) - [Supabase: application architecture](https://supabase.com/docs/guides/getting-started/architecture) - [Notion: wiki and knowledge guidance](https://www.notion.com/help/guides/category/wiki) - [Linear: issues, projects, teams and milestones](https://linear.app/docs/conceptual-model) The existing Roadmap v1 order, ecosystem image, shared-service boundaries and Lemuel/AI handoff remain in effect. The new image is the visual-selection table, not a replacement for the ecosystem architecture image. Earlier backend/QA limitations remain open until separately verified. No company files were moved, permissions broadened, runtime backend changed, workflow scheduled or transaction executed by this documentation update.