04 Procedure: Drive & GitHub Navigation Guide

First full draft – replaces the earlier “Drive & GitHub Navigation” placeholder with a hands-on tour of the entire Solo-Team tool stack (Drive, Trello, Clockify, Insightful, Telegram, Ops Sheet).

Big-Picture Overview§

Block	Content
Purpose & Scope	Hand newcomers a one-stop atlas that answers three questions: ① Where do I click? (boards, drives, sheets, chats) ② What lives there? (rules, tasks, evidence, approvals) ③ How do the pieces snap together? (daily loops & data hand-offs) The guide is read-only training material referenced by onboarding checklists, `/map` and `/drivepath` bot commands, and the Self-Help Checklist.
Map / Flow	Start here → skim Digital-Stack Map (ASCII) → jump to the tool section you need (Drive · Trello · Telegram · Clockify · Insightful · Ops Sheet) → use quick-nav tips & “What to store / NOT store” tables → follow cross-links back into live SOPs.
Roles / RACI	Freelancer Operator R · Systems-Ops Lead A · Ops Manager C · GPT Assistant I
KPIs	100 % operators complete atlas during Day-0 onboarding · < 2 support questions per operator in Week 1 about “where do I find …?”
Tools	Google Drive (Shared Drives) · Trello workspaces & boards · Telegram folders & bots · Clockify · Insightful · Ops Google Sheet
Risks	Docs drift from reality · Sensitive folders exposed by mistake · Operators save files in wrong Drive branch
Controls	• Quarterly System-Retro verifies atlas diagrams (SOP SYS07-Retro). • Drive ACL & GPT `/drivepath` lookup exclude 00-ADMIN & HR.

Quick ASCII Map of the Digital Stack§

┌───────────────────┐          ┌───────────────────┐
│ 01-SYSTEMS Drive  │<─SOPs──┐ │ 02-OPERATIONS     │
│  (Markdown LIVE)  │        │ │   Drive (assets)  │
└─────────┬─────────┘        │ └─────────┬─────────┘
          │                  │           │ (png proof, reports)
          │                  │           │
          ▼                  │           ▼
   ┌──────────────┐  cards   │   ┌───────────────────┐
   │ Trello Boards│──────────┘   │  Ops Google Sheet │
   │  • Personal  │                 (row evidence)   │
   │  • Ops Team  │<──────────reports───────────────┘
   └──────┬───────┘
          │ 🔴 / ✅
          ▼
   ┌────────────────┐
   │ Telegram bots  │
   │  & channels    │
   └────────────────┘

(a cleaner SVG lives in the repo; bot /map shows this diagram)

Section Cheat-Sheet§

Tool	Where it lives / how to open	What you store / do here	What never lives here	Quick-nav / pro-tip
Google Drive Shared Drives	Chrome → drive.google.com → “Shared Drives”	• LIVE Markdown SOPs (`01-SYSTEMS/01-SOPs-&-Playbooks/`) • Reference diagrams & templates	Finance PDFs (→ 00-ADMIN)	Star the folders you visit daily (`Shift+S`).
Personal Trello board	`Operators Hub` workspace → board named `OP-<Name>`	Inbox / Q1-Q3 lists, Daily Hygiene, Blocked	Channel tasks (they stay on Ops board)	`B` key → instant board switcher.
Operations Trello board	`Channel Ops` workspace (`<Channel> Ops`)	Ready ⏳ cards to copy into Personal	Personal backlog	Right-click card → “Copy → My Board”.
Ops Google Sheet	Link inside Ops board Read-Me card	Row-level process data, auto KPI formulas	Personal notes	`Ctrl+/` opens sheet search by named range.
Clockify	Desktop app / web dashboard	Timers tagged with card link or SOP step	Idle 1 h+ chunks (split & label)	`Alt+C` hotkey → quick start.
Insightful	Agent in taskbar	30-sec screenshots (idle guard 1 min desktop / 5 min mobile)	Personal browsing	Green status = recording ok; red ▶ restart agent.
Telegram folders	Ops, Reports, Systems	🔴 alerts, Daily Digest, approvals, system updates	Long discussions (use Slack or call)	Pin `/help` bot message for command list.

(6 bullet sections; ≤ 7 bullets each)

Drive Orientation (Markdown SSOT)
Open 01-SYSTEMS → 01-SOPs-&-Playbooks.
Use 🔍 Drive search with type:markdown SOP04.
Copy path (⇧Z) to reference in PRs.
View-only outside OP-<Name> and 02-OPERATIONS.
NEVER drag files out of shared drive (breaks links).
Personal & Ops Boards
Personal board WIP caps; Ops board is the source of truth for team work.
Copy flow: Ops card → Personal Inbox → Q1 Doing.
Butler mirrors 🔴 cards to Blocked list.
Archive done cards Monday 08:00 (auto).
Ops Google Sheet
Tabs: Input, KPI, Exceptions.
Row status drives badge on Ops card.
If sheet row needs follow-up → paste link in Trello comment, not a new card.
Clockify + Insightful … (existing TT-SOP-1 rules condensed)
Telegram Traffic Rules … (Digest, Blocker, Kaizen, Systems Kitchen)
Troubleshooting & Gap Escalation … (points to Self-Help Checklist & Gap-Patch PR)

❌ Miss	✅ Meets	⭐ Exceeds (shareable win)
Saves files in wrong drive / asks mgr	Uses guide → finds correct spot unaided	Posts new `/drivepath` suggestion PR
Copies Ops card but leaves link broken	Card copied with back-link & moved to Q1	Adds `"Copied-by:<name>"` label for metrics
Time entry w/out link	100 % timers include card/SOP link	Proposes Clockify workspace tag automation

ArchitectureSnapshot JSON (excerpt, new r1)§

{
  "version_id": "2025-05-15-r1",
  "system_level": "Procedure",
  "lifecycle_state": "DraftSOP",
  "target_name": "KQ-SOP-4 – Drive & Digital-Stack Navigation Guide",
  "parent_name": "Knowledge Query & Self-Learning",
  "last_updated": "2025-05-15T01:20:00Z",

  "overview": {
    "purpose": "Give operators a single atlas of all tools (Drive, Trello, Telegram, Clockify, Insightful, Ops Sheet) and show how data flows between them.",
    "flow": [
      "Open atlas (markdown)",
      "Review ASCII map then jump to needed tool section",
      "Follow quick-nav table and rules of what to store / avoid",
      "If location unclear run /drivepath or /map in GPT",
      "If still lost escalate via Self-Help Checklist & Knowledge-Gap tag"
    ],
    "roles": ["Freelancer Operator","Systems-Ops Lead","Ops Manager"],
    "kpis": [
      "Day-0 atlas completion 100%",
      "Week-1 'where is X' questions <2 per operator"
    ],
    "tools": [
      "Google Drive Shared Drives",
      "Trello workspaces",
      "Telegram channels",
      "Clockify",
      "Insightful",
      "Ops Google Sheet"
    ],
    "risks": [
      "Docs drift from stack changes",
      "Misplaced evidence",
      "Exposure of admin paths"
    ],
    "controls": [
      "Quarterly Doc ↔ Stack audit",
      "drive_paths.yml whitelists safe directories"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Knowledge/KQ-SOP-4_Digital_Stack_Navigation_v0.1.md"
  }
}

(procedure_core to be authored after sign-off on content outline.)

— End of KQ-SOP-4 r1

04 Procedure: Drive & GitHub Navigation Guide

DraftSOP · Procedure · KQ-SOP-4 — Digital-Stack Navigation Guide · 2025-05-15-r1§

Big-Picture Overview§

Quick ASCII Map of the Digital Stack§

Section Cheat-Sheet§

Detailed SOP — Navigation & Best-Practice Walk-through§

WGLL (Navigation)§

ArchitectureSnapshot JSON (excerpt, new r1)§