- Start new GPT instance o3
- Copy paste the Oracle prompt, send it to GPT
- Copy Data 1 the Oracle prompt, send it to GPT
- Copy Data 2 the Oracle prompt, send it to GPT
- Repeat for all data.
- Type "COMPILE KNOWLEDGE" and send
Quick Tutorial — Running the “SOP Business Oracle” entirely inside ChatGPT§
Use-case: you don’t host a bot; you simply paste the prompt and your SOP chunks into one ChatGPT thread and let it do the merging.
1 · Load the Oracle “System Prompt”§
- Open a new ChatGPT chat.
- Copy–paste the full Oracle prompt (the long instructions that define INGEST, COMPILE KNOWLEDGE, etc.) into the very first message and hit Send. ChatGPT will reply “Ready to ingest your SOP resources.”
2 · Feed the data chunks, one message each§
Keep the order logical (e.g., top-level README first, then subsystems).
| Sequence | What you paste | After you press Send ChatGPT should reply… |
|---|---|---|
| 2-1 | Data 1 (e.g., 00 README / Orientation file) | Summary ⟦1⟧ stored. |
| 2-2 | Data 2 | Summary ⟦2⟧ stored. |
| 2-3 | Data 3 | Summary ⟦3⟧ stored. |
| 2-4 | Data 4 | Summary ⟦4⟧ stored. |
If anything overwrites an existing section you’ll see “Update stored.” instead.
LIKE THIS 1. Start new GPT instance o3 2. Copy paste the Oracle prompt, send it to GPT 3. Copy Data 1 the Oracle prompt, send it to GPT 4. Copy Data 2 the Oracle prompt, send it to GPT 5. Repeat for all data. 6. Type "COMPILE KNOWLEDGE" and send
3 · Trigger the cheat-sheet§
In a fresh message type COMPILE KNOWLEDGE (exact caps).
ChatGPT returns the full deliverable:
- Lightning Overview
- Concept Matrix
- Process Blueprint
- Pitfalls & Misconceptions
- Mini-Case Library
- Open-Questions Register
- Starter Pack
You are now in Q\&A Mode.
4 · Zoom out: get the big picture§
Ask:
Give me a brief (≤150 words) big-picture recap of the Solo-Team OS and list the eight subsystems.
The Oracle will answer from the compiled map.
5 · Deep-dive subsystem by subsystem§
For each of the eight subsystems:
- Prompt
Deep dive on <Subsystem Name>:
• Summarise purpose & flow
• List open questions or fuzzy areas
• Ask me 3 clarification questions if needed
Repeat until every subsystem shows no remaining open questions.
6 · Produce the research deliverable§
After the last subsystem:
Export all my clarification Q&A as Markdown
Copy-paste that block into a new Google Doc named
“Solo-Team OS – Clarification Journal
Share it with the team or attach it to your SOP pipeline card.
7 · Best-practice tips§
- Chunk size: if a paste exceeds ChatGPT’s limit, split at the nearest heading and send in two messages.
- Versioning: note the date in your Google Doc title; rerun
COMPILE KNOWLEDGEafter major updates. - Gap logging: when ChatGPT highlights a fuzzy area, copy it straight into your “Open-Questions Register” column so it feeds the Gap-Fix loop.
- Never mix new SOP text and Q\&A in the same message—keep ingestion and conversation separate.
Follow these steps and you’ll have a fully-merged knowledge base, subsystem clarity, and a documented research trail—all from a single ChatGPT conversation. You are “SOP Business Oracle.” Mission Hold a continuously-growing map of every Standard Operating Procedure (SOP) resource I feed you—manuals, flow‑charts, video or call transcripts, slide decks, templates, and learner insights. Merge, deduplicate, and track provenance so you can • orient absolute beginners • compile an authoritative cheat‑sheet on command • coach users through a mastery path (study prompts, reflection questions, progress checks) • adapt answer depth as the learner’s mastery grows • answer questions with SOP‑level citations • log gaps and contradictions for follow‑up refinement. ──────────────────────────────────────────────────── 0 · Workflow INGEST – Each time the user sends a chunk (JSON or prose) you must a) parse it into the Internal Schema (see § A) b) merge with existing data, deduplicating by concept name c) reply only Summary ⟦n⟧ stored. (or Update stored. if overwriting).
COMPILE KNOWLEDGE. – When the user types this exact phrase you a) build the deliverables in § 3, using the merged map b) emit them once, then switch to Q&A Mode (see § 4).
REFRESH CHEAT‑SHEET – Re‑run step 2 after new material arrives.
Add insight: – If a user message begins with this tag, extract the text that follows, store it in the insights array with an automatic timestamp source:"chat-{YYYY-MM-DD}", then reply Insight stored.
──────────────────────────────────────────────────── 1 · Ingestion rules (flexible version) • A user message may contain any combination of: - a well‑formed JSON object - a “loose” JSON fragment (missing keys, extra keys, wrong names) - plain‑language prose - both JSON and prose in the same chunk • Detection & parsing order 1. Isolate JSON‑looking segments – Anything between json … or triple‑backticks, or – the first top‑level { … } block in the message. 2. Attempt strict parse into the Internal Schema. 3. If strict parse fails → fuzzy map: – Match obvious keys (title, steps, purpose, etc.). – Stash unrecognised keys under extra_fields. 4. Prose remainder → treat as authoritative summary for that SOP section. – Use the first H‑style line as title if missing. – Extract bullets that look like steps or definitions. • Storage behaviour - Merge structured data into the map, deduplicating by term / name. - Append any prose that didn’t map cleanly to the summary field (or insights if it reads like reflection). - Discard the raw chunk after parsing to save tokens. • Acknowledgement syntax - If any new data stored → reply Summary ⟦n⟧ stored. - If an existing SOP section is overwritten or expanded → Update stored. ──────────────────────────────────────────────────── 2 · Deduplication logic • Key fields for uniqueness – term in terms array – name in frameworks / processes • When a duplicate arises, append the new source + section_id to the sources list for that item and merge any nuance. • Keep official wording in quotes/stories; keep plain language in plain_english. ──────────────────────────────────────────────────── 3 · Deliverables (Cheat‑Sheet) – output only on COMPILE KNOWLEDGE. 3‑A Lightning Overview – ≤ 120 words, plain English. 3‑B Key Concepts / Terms / Frameworks / Processes Matrix | Item | Core Idea (≤ 15 words) | Practical Payoff | Source(s) | 3‑C Process Blueprint – numbered path (foundation → mastery) with 1‑line value‑add each step. 3‑D Pitfalls & Misconceptions – Mistake → Prevention tip (cite source). 3‑E Mini‑Case Library – ≥ 4 scenarios (2 low‑stakes, 2 high‑stakes). 3‑F Open‑Questions Register – missing detail / contradiction → section(s). 3‑G Starter Pack – • Three core SOP domains (Operations, Sales & Marketing, Finance & Admin) • First recommended SOP (Client Onboarding) • Suggested initial reading order for beginners. ──────────────────────────────────────────────────── 4 · Q&A MODE (activates after first cheat‑sheet) Voice Concise, encouraging coach. Citations source‑slug‑section, e.g. (OPS‑ONB‑03). Depth control “brief” → ≤ 3 bullets · “deep dive” → step‑by‑step. Beginner trigger • If user says they are new or asks “What is this about?”, reply with Beginner Mode: – plain‑English definitions of SOP, Process Map, and RACI Matrix – invite them to read/paste their Operations Manual or summaries – mention Starter Pack section. Progress checks • Pop quiz: “Pop quiz on X” → ask 3–5 questions drawn from stored data; score answers. • Mastery check: “Progress report” → list milestones achieved (see insights tagged example done). • Update learner_state.mastery_level based on quiz / check results (≥ 80 % ⇒ +1, max 2). • Default reply depth by mastery_level: 0 = plain English ≤ 3 bullets · 1 = richer ≤ 6 bullets · 2 = advanced cross‑SOP synthesis + subtle caveats. • Manual override: “Set level n” (n = 0‑2). When new JSON arrives → Update stored. then merge and update Register (do not re‑emit cheat‑sheet unless asked). ──────────────────────────────────────────────────── 5 · Quality‑Control Checklist (run before sending cheat‑sheet) ☑ Every term / process / caveat / question appears somewhere. ☑ No duplicate rows or headings. ☑ Lightning Overview ≤ 120 words. ☑ Starter Pack filled. ☑ Open‑Questions Register lists all unresolved items. ──────────────────────────────────────────────────── §A · Internal Schema (Extractor schema + provenance + insights + learner state) { "source": "", "section_id": "", "title": "", "summary": "", "plain_english": "", "terms": [ { "term": "", "definition": "", "sources": [""] } ], "frameworks": [ { "name": "", "definition": "", "sources": [""] } ], "processes": [ { "name": "", "purpose": "", "roles_responsible": "", "steps": [ "" ], "example": "", "time_estimate": "", "sources": [ "" ] } ], "mindsets": [ "" ], "strategies": [ "" ], "caveats": [ "" ], "stories": [ "" ], "quotes": [ "" ], "templates": [ "" ], "exercises": [ "" ], "questions": [ { "q": "", "a_summary": "", "type": "", "sources": [""] } ], "insights": [ { "note": "", "sources": [""] } ], "learner_state": { "mastery_level": 0 }, "last_compile_timestamp": "", "reminders": [ { "time": "", "text": "" } ] } Arrays may be empty; keep keys intact. ──────────────────────────────────────────────────── 6 · Extended Commands (optional add‑ons) • Export CSV / Markdown — Export {array name} {format} → Output the named array (terms, frameworks, processes, questions, quotes, templates) in CSV or Markdown table. • Export knowledge — EXPORT KNOWLEDGE. → Print the entire internal map as one JSON object (version snapshot). • Draw tip — Draw tip → Pick a random entry from quotes or templates and output it. • Make schedule — Make schedule {n weeks} → Turn the Process Blueprint into a week‑by‑week study plan spanning n weeks. • Show map — Show map → Emit a Mermaid graph (Markdown fenced block) showing frameworks → processes relationships. • Spaced quiz — Spaced quiz {n cards} → Select n items the learner has not answered recently (track timestamps in insights), ask them, then reveal answers. • What’s new? — What's new? → Compare current timestamp with last_compile_timestamp; list concepts, processes, or insights added since the last cheat‑sheet. • What next? — What next? → Analyse open questions, mastery gaps, and insights to propose the very next SOP, process, or reflection exercise. • Set daily reflection — Set daily reflection hh:mm → Store a reminder entry and output a VEVENT block that schedules a daily reflection question at the specified time. • Advanced search — Search {criteria} → Filter arrays using simple conditions (e.g., time<10, role=Finance) and return a table. (Add more bullets here when you invent new shortcuts.) ──────────────────────────────────────────────────── Begin listening for summaries, JSON, Add insight: notes, and the extended commands now. (Acknowledge storage only until the user types COMPILE KNOWLEDGE.)
Solo-Team OS — Operator Orientation§
v 1.3 · 2025-05-17 (bookmark or print—blue links open the deeper guides)*
1 Why this OS exists → mission & payoff§
Ship client value every day, solo. Ideas → Trello cards / Ops-Sheet rows → timed work → evidence → weekly pay-outs. You stay in flow, managers stay out of your way, and every minute is auditable.
2 The 8-Subsystem Map§
Work-Intake & Prioritisation
(Personal Q1/Q2/Q3 ⥃ Ops board & Sheet)
│
┌────┬────────┬─────────┴─────────┬────────┬─────┐
│ │ │ │ │ │
│ Time-Tracking Daily Hygiene Meeting Sync Knowledge
│ & Proof & Close-out & Action Cap Query/Learn
└────┴──────────┴──────┬────────┴────────────┴─────┘
│
Weekly / Monthly Rituals & Invoicing
│
Gap-Fix & Continuous-Improvement loop
│
IT-Security & Compliance backbone
(ASCII version: /map ascii full-os in the Coach)
3 Your daily rhythm (Mon – Fri, local time)§
| Time | Action | Core SOP |
|---|---|---|
| 09 : 00 | Open Personal board → drag ≤ 3 cards into Q1 Doing | Daily Work-Cycle |
| Work blocks | Work each card / Ops-Sheet row → stop timer, start next | — |
| — | Stuck > 15 min? label 🔴 & run /alert in Telegram |
Blocker Escal. |
| 16 : 45 | Stop all timers → export Clockify CSV + Insightful % PNG | Evidence Export |
| 17 : 00 | Inbox-Zero triage → be sure Q1 To-Do ≤ 3 for tomorrow | Daily Work-Cycle |
| 17 : 05 | Send Daily Digest (W↑ C↓ T→ M) in /manager |
Daily Digest |
| 17 : 15 | Self-check → no unlinked minutes; Learning-Log updated | — |
4 Non-negotiables / SLAs§
| Rule | Metric / Consequence |
|---|---|
| Q1 Doing ≤ 3 always | Butler badge turns red if you exceed cap |
| Inbox-Zero before clock-out | 100 % weekdays |
| Digest sent ≤ 17 : 30 | No next-day work if missing |
| Manager reacts ✅/❌ ≤ 24 h | You ping until done |
| Blocker escalated ≤ 15 min | 🔴 label + /alert |
| 100 % minutes linked | Unlinked < 3 % / week |
5 Master resource kit§
| Asset | Where it lives* | Purpose |
|---|---|---|
| This Orientation | 04-OPERATORS-INDEX/orientation/ |
One-pager reference |
| Phase A → E specs | 04-OPERATORS-INDEX/boot-camp-phases/ |
Click when a phase gate opens (A,B,C,D,E) |
| Start-Here Board template | Trello Template Gallery | Pre-loaded 🚀 Learning Loop + 🛠 Sim-Day |
| Personal Board template | Trello Template Gallery | Eisenhower cockpit, Butler rules |
| Clockify Quick-Start.md | linked from Phase A-8 card | 5-min install & naming convention |
| Learning-Log & Time-Ledger templates | Drive › Templates | Store answers + minute evidence |
| Solo-Team Coach (Oracle bot) | GPT workspace | /help, /deepdive, /quiz, … |
| Markdown SOP repo | 01-SYSTEMS/… (mirrored on GitHub) |
Single source of truth |
| WGLL Gallery | 01-SYSTEMS/WGLL_Gallery |
Concrete examples → /tip <domain> |
| Mind-set Snapshot | PDF appendix | Daily habit prompts |
| Sim-Day Boot Loop spec | Phase D doc | One-day competence test |
*All links are pre-bookmarked in the Chrome Work profile you create in Phase A.
6 Day-1 “Start-Here” checklist (flex-paced)§
- Copy Start-Here – Learning Ops Board → rename
OP-<YourName>. - LL-01 Device Setup → run Phase A Steps A-0 … A-7.
- LL-02 Focus Zone → finish Phase A hardening & Focus-mode.
- Start logging every minute (
Setup:tags) in Clockify and Time-Ledger Sheet. -
LL-03 Big-Picture Tour → ask Coach:
-
/explain system map - “Explain how \
fits the whole” - “ASCII map of \
`” - Duplicate Subsystem Study Cycle card 8× and work Phase C (LL-04-1 … 8).
- Run Sim-Day list (Phase D).
- Complete Boot-Retro & Graduate request (Phase E).
- Manager posts 🎓 → you’re cleared for live client work.
(Move at your own pace—but keep timers running).
7 Need help?§
- Open 🤖 COACH FIRST card in 📥 Inbox → try
/find <keyword>or/deepdive <section>. - Work the Self-Help Checklist (KQ-SOP-3).
- Still blocked ≥ 15 min → label card 🔴, post
/alertor 🔴 Knowledge-Gap. - Log that time as
Learn:Coach:PQA – <topic>.
8 Beta notice§
Boot-camp docs & board templates are actively improving.
If a link or screenshot doesn’t match, ask the Coach first.
Log every mismatch with tag Learn:Gap-Log and raise a Knowledge-Gap if the bot can’t solve it — fix lands in ≤ 24 h.
Welcome aboard — your flow-state workstation is open. (And yes, your first timer should already be running.)
Clockify Quick-Start — Solo-Team OS§
v 1.1 · 2025-05-15 – link from card LL-01 Device Setup**
1 · Why log every minute?§
| Reason | Pay-off |
|---|---|
| Proof = Pay-day | CSV + screens feed Daily Digest, WeekMetrics & Invoice. No log → no pay. |
| Flow awareness | Timer forces single-task focus; you’ll spot context-switch drag. |
| Kaizen fuel | WeekMetrics shows time sinks & deep-work ratios to improve. |
2 · First-time setup (≈ 5 min)§
- Join the Solo-Team Clockify workspace (invite link in Telegram).
- Create / verify Projects
Learning Loop– log every onboarding card / SOP step.Client Work– for billable work later.- Install tools on your hardened Work OS profile
- Clockify Desktop Tracker – start at login.
- Insightful Desktop Agent – green dot means capturing 30-sec screenshots.
- Tracker settings – open Clockify Preferences
- Idle detection : 1 min (desktop) / 5 min (mobile).
- Reminder : break prompt every 90 min.
- Browser pin – keep
clockify.me/trackernext to Trello tab. - (Optional) Generate a read-only API key for Coach
/next.
3 · Daily habit loop§
| Moment | Action |
|---|---|
| Before starting any card / row / SOP step | Copy its URL / ID into Timer Description.[LL-04] Read Subsystem-X Overview |
| Work in focus | Timer runs; Insightful grabs 30-sec shots. Touch keyboard/mouse ≤ 5 min. |
| Pause / switch | Stop timer immediately & start the next. Overlaps = ❌. |
| 16 : 45 | Check all entries: link/ID present + correct project. Fix now, not tomorrow. |
4 · Link-naming cheatsheet§
| Source | Paste exactly in Description |
|---|---|
| Trello card | https://trello.com/c/abc123 |
| Ops-Sheet row | SheetRow-42 https://docs.google…#gid=0&range=A43 |
| Learning-Scaffold SOP step | LL-SOP-Step-3 (Reflect Subsystem-X) |
| Ad-hoc task (no link) ⚠️ | Write a verb + 5-word purpose and tag NoLink. Manager will question it. |
Rule of thumb: If you can link it, link it. Only use
NoLinkas last resort.
5 · What Great Looks Like (WGLL)§
| ❌ Miss | ✅ Meets | ⭐ Exceeds |
|---|---|---|
| Empty description / wrong project | Correct link/ID + project | Adds concise verb: Draft Digest – LL-06 |
6 · FAQ§
- Forgot timer? Start when you notice, tag
Late-Start; never guess past time. - Multi-task? Stop → start next timer; keep cards atomic.
- Breaks? Timers off; idle detector will auto-trim.
- Mobile work? Manual screenshots every 30 min until Insightful mobile lands.
- Green dot missing? Insightful paused → restart agent before continuing.
7 · Next step right now§
- Open Learning Loop board (copied from template).
- Start a timer on card LL-01 Device Setup (
Learning Loopproject). - Complete SEC-SOP-1 screenshots → move card to Waiting for Approval.
Timer already running? Nice — you’re on the clock.
Default Time Doctor “Project ➜ Task” Buckets for the Solo-Team OS§
How to read this table • Project = the top-level entry you (or the TD admin) create once in Projects & Tasks. • Typical Tasks = quick templates operators create ad-hoc under that project (one per Trello card / Sheet row / SOP step). • Why it exists = the subsystem or ritual it maps to, so reports stay meaningful.
| # | Project (top-level) | Typical Tasks operators create (examples – they’ll swap the ID/link in description) |
Why it exists / Subsystem tie-in |
|---|---|---|---|
| 1 | Learning Loop (non-billable) | LL-01 Device Setup · Learn:Time-Tracking:P1A – System Overview · Teach-Back Work-Intake |
Covers the entire onboarding boot-camp scaffold so study minutes are traceable. |
| 2 | Daily Work-Cycle (billable once live) | SIM-001 Update FAQ · Card https://trello.com/c/abc123 · SheetRow-42 Update |
All task execution that comes from Work-Intake & Prioritisation (cards/rows). |
| 3 | Admin & Hygiene (non-billable) | Evidence Export · Daily Digest · WeekMetrics PDF · Invoice Draft |
Anything driven by Time-Tracking & Proof / Daily Close-out / Rituals & Invoicing. |
| 4 | Meetings & Sync (billable)* | Daily Stand-up · Client Kick-off Call · Meeting Actions Processing |
Ties to Meeting Sync & Action Capture subsystem. |
| 5 | Blocker Escalation (non-billable) | BLK-123 Waiting for Manager |
Quick visibility in TD reports; isolates time lost to blockers (SOP-5). |
| 6 | Kaizen / Continuous Improvement (non-billable) | Mini-Retro Note · Promote Kaizen Card · PR SOP Fix |
Maps to Gap-Fix & Continuous-Improvement efforts. |
| 7 | Security & Compliance (non-billable) | Quarterly Device Audit · Focus-Zone Self-Check · Incident Response Drill |
Logs time spent on IT-Security & Compliance SOPs. |
| 8 | Sim-Day / Training (non-billable) | SimDay:Q1.1:SIM-001 · SimDay:Hygiene · SimDay:Invoice |
Used only during onboarding refreshers or future fire-drills. |
Admin Tip Daily Work-Cycle will hold most of the billable effort; grant project-level “billable ON” there. Everything else can stay non-billable unless you need to invoice training time to the client.
Usage Rules to Keep the Data Clean§
-
One Task = One Work Unit • If it has a Trello card, Sheet row, or SOP step ⇒ make it a new Task the first time you touch it. • Stop timer immediately when you switch.
-
Description Format (copy into TD description field)
<URL or RowID> – <Short Verb Phrase>
Examples:
https://trello.com/c/abc123 – Draft outline
SheetRow-42 – Enter prices
Learn:Knowledge:P4 – Deep-Dive Q&A
-
No orphan tasks • Only use
NoLink – …when genuinely no system artefact exists (rare). • Manager will question anyNoLink> 10 min blocks. -
Self-audit 16 : 45 • Reports ▸ Timeline – every entry must show the right Project and a hyperlink or RowID in the first line. • Fix before you export the “Today” CSV for TT-SOP-2.
Follow these buckets and naming rules and the switch to Time Doctor will be seamless—reports, Evidence Export, WeekMetrics, and invoices continue to work exactly as before.
DraftSOP · Procedure · LS-SOP-0 — End-to-End Learning-by-Doing Boot-camp · 2025-05-17-r2§
This file is the “executive spine” of the boot-camp. Each phase now lives in its own spec (A–E). LS-SOP-0 tells you why and in what order; the phase specs tell you exactly how. Links below jump straight to the phase documents in Drive ▸ 04-OPERATORS-INDEX ▸ Boot-camp Phases.
1 · Purpose & Scope§
Give new operators a time-tracked, manager-light onboarding journey that
- provisions a secured, focus-only workspace
- installs Clockify + Insightful habits from minute 1
- teaches the OS mind-sets & eight subsystems
- proves competence with a compressed Sim-Day
- finishes with a Boot-Retro → Kaizen → Graduation hand-off
— all inside ≤ 5 calendar days and with zero unlinked minutes.
2 · Master Resource Kit (handed over on Day-0)§
| Asset | Where it lives | Purpose |
|---|---|---|
| Phase Specs (A – E) | Boot-camp Phases/Phase-<X>.md |
Step-by-step check-lists & Trello/Butler config |
| Operator Orientation v1.2 (PDF) | 04-OPERATORS-INDEX/Orientation |
One-pager: mission, 8-subsystem map, daily rhythm, SLAs |
| Start-Here Board Template | Trello Template Gallery | Lists: 🚀 Learning Loop + 🛠 Sim-Day Sandbox |
| Personal Board Template | Trello Template Gallery | Q1/Q2/Q3 cockpit, Inbox-Zero list, Butler rules |
| Solo-Team Coach (Oracle bot) | GPT workspace | /help, /map, /deepdive, /quiz, /reflect … |
| Markdown SOP repo | Drive 01-SYSTEMS (→ GitHub mirror) | Single source of truth |
| Clockify Quick-Start.md | Linked from Phase A – Step A-8 | 5-min desktop install & naming convention |
| Mind-set Snapshot | Orientation PDF appendix | Daily habit reminders |
| WGLL Gallery | 01-SYSTEMS/WGLL_Gallery |
Concrete examples for every SOP |
| Learning-Log Docs + Time-Ledger Sheet | Auto-generated per operator (OP-<Name>/Learning-Log) |
Store answers, screenshots, scores, reflections |
| Beta Notice & Gap-Log rule | Pinned in 📘 BOARD GUIDE + Orientation PDF §2 | How to log mismatches while the OS is in public-beta |
(All links are pre-bookmarked in the Chrome Work profile that Phase A creates.)
3 · Phase Timeline (high-level)§
| Day / Phase | Target outcome | Clockify tag prefix | Detailed spec |
|---|---|---|---|
| D-0 · Phase A – Device & Core Stack | Secure laptop + phone, Oracle bot live | Setup: |
Phase-A v A-1.1 |
| D-0 · Phase B – Orientation & Mind-sets | 120-word OS overview, ASCII map, quiz ≥ 80 % | Orient: |
Phase-B v B-1.0 |
| D-1→D-3 · Phase C – Subsystem Mastery | 8 × 9-step learning cycles, all quizzes ≥ 80 %, teach ≥4/5 | Learn:<Subsys>: |
Phase-C v C-1.0 |
| D-4 · Phase D – Sim-Day Boot Loop | Full daily ops chain executed in ± 3 h | SIM:<StepCode>: |
Phase-D v 1.0 |
| D-4 · Phase E – Boot-Retro & Graduate | Reflection, Kaizen card, Graduate ✅ | BootRetro, GraduateReq |
Phase-E v 1.0 |
Everything you touch ⇒ a Clockify timer. Tag patterns are defined inside each phase spec.
4 · Pass / Fail gates§
| Gate | Must be true before you enter the next phase | Checker |
|---|---|---|
| Phase A ✓ | LL-01 & LL-03 cards approved; Oracle bot live | Manager |
| Phase B ✓ | Orientation card LL-03 green; 5 linked Orient:* timers |
Manager |
| Phase C ✓ | 8 Learning-Log docs green; no open Gap? lines |
Systems-Ops Lead |
| Phase D ✓ | All green boxes in Sim-Day rubric; no running timers after 12:00 | Manager |
| Phase E ✓ | Graduate card moved to Approved; first live timer started | Manager |
5 · Non-Negotiables (apply across all phases)§
- Work only from the Work OS profile + Focus mode you created in Phase A.
- Every action time-tracked & linked; Insightful green dot must show.
- Ask the Oracle first. If still blocked → follow Beta Gap-Log rule.
- No live client boards until you see the 🎓 comment on your Graduate card.
6 · Where to dive deeper§
- Phase spec files (A → E) hold exact Trello card names, Butler automations, SOP calls, proof screenshots & minute estimates.
- Trello Templates list on your personal board mirrors those check-lists for drag-and-drop duplication.
- Orientation PDF gives the folded-map view on one page; keep it pinned.
- Solo-Team Coach answers 90 % of “where is…?” questions in under 5 s.
7 · ArchitectureSnapshot JSON (excerpt)§
{
"version_id": "2025-05-17-r2",
"system_level": "Procedure",
"lifecycle_state": "DraftSOP",
"target_name": "LS-SOP-0 – End-to-End Learning Bootcamp",
"parent_name": "Knowledge Query & Self-Learning",
"overview": {
"purpose": "Self-paced, evidence-rich onboarding from device hardening to live production hand-off.",
"flow": [
"Phase A Device & Core-Stack Setup",
"Phase B Orientation & Mind-sets",
"Phase C Subsystem Mastery Loop",
"Phase D Sim-Day Boot Loop",
"Phase E Boot-Retro & Graduation"
],
"roles": ["Freelancer Operator","Systems-Ops Lead","Ops Manager","GPT Assistant"],
"kpis": ["Bootcamp ≤5 days","All quizzes ≥80%","Teach-backs ≥4/5","0 unlinked minutes"],
"doc_link": "Drive:/01-SYSTEMS/Onboarding/LS-SOP-0_Bootcamp_v1.1.md"
}
}
8 · Quick-links (update URLs before publishing)§
- Phase-A spec — link • Phase-B — link • Phase-C — link • Phase-D — link • Phase-E — link
- Start-Here Board template — link
- Learning-Log folder template — link
- Clockify Quick-Start.md — link
- WGLL Gallery index — link
- Solo-Team Coach workspace — link
How to use this document§
- Skim sections 1-3 to grasp the big picture.
- Open Phase-A spec and start Step A-0 — the board guide and timers will lead you from there.
- Keep this SOP open in a pinned tab; it’s your north star whenever you wonder “where am I in the boot-camp?”.
— End of LS-SOP-0 v 1.1
PHASES
Phase A — Device & Core-Stack Setup§
updated to v A-1.1 – includes Oracle Bot sign-in (Step A-9)
| # | Action & Owner | Clockify tag | Where it lives / Trello mapping | SOP / Quick-Start | Proof to attach |
|---|---|---|---|---|---|
| A-0 | Guarantee live comms on phone – install Telegram → join /manager & /security-alerts channels (Operator) |
Setup:PhoneTG |
Checklist-item 1 on LL-01 Device & Focus-Zone Setup card (🚀 Learning Loop list) | SEC-SOP-1 §0 | Screenshot of phone channels |
| A-1 | Create work-only Gmail / Workspace account (Operator) | Setup:WGmail |
Checklist-item 2 on LL-01 | SEC-SOP-1 §1 | Screenshot of inbox + 2-FA ON |
| A-2 | Create non-admin Work OS profile & login | Setup:Profile |
Checklist-item 3 | SEC-SOP-1 §2 | OS users panel screenshot |
| A-3 | Install Telegram Desktop immediately – confirm comms in /manager |
Setup:DeskTG |
Checklist-item 4 | SEC-SOP-1 §3 | Desktop “Device online” msg |
| A-4 | Run Hardening Checklist – encryption, firewall, AV, Bitwarden | Setup:Hardening |
Checklist-item 5 | SEC-SOP-1 §4 | BitLocker/FileVault ON shot |
| A-5 | Install core stack – Trello, Drive, MarkText, Clockify, Insightful | Setup:Apps |
Checklist-item 6 | SEC-SOP-1 §5 + Clockify Quick-Start | Screenshot installer list |
| A-6 | Configure projects & Proof-of-Life test – start 2-min “TEST – Device Ready” timer, verify ≥ 4 Insightful shots | Setup:PoL |
Checklist-item 7 | SEC-SOP-1 §6 | Timer link + Insightful PNG |
| A-7 | Set up Focus-Zone & phone Work Focus (desktop DND + SEC-SOP-2 phone rules) | Setup:Focus |
Separate card LL-02 Focus-Zone Checklist (🚀 list) | SEC-SOP-2 & SEC-SOP-3 | Two screenshots: OS Focus + phone Focus page |
| A-8 | Clockify Quick-Start – join workspace, idle = 1 min, pin tracker | Setup:CloQS |
Card LL-03 Clockify Quick-Start (🚀 list) | Clockify Quick-Start.md | Clockify dashboard link in card |
| A-9 | Sign in to Solo-Team Coach (Oracle Bot) – open workspace URL, SSO with work Gmail, run /help & /map |
Setup:Coach |
NEW checklist-item 8 on LL-01 Device & Focus-Zone Setup | KQ-SOP-1 | PNG of /help & /map replies pasted on card |
| A-10 | Submit Day-0 approval – move LL-01 & LL-02 to Waiting for Approval, ping manager | — | Action list on board | SEC-SOP-1 end step | Manager ✅/❌ comment |
Phase A deliverables§
- LL-01 Device & Focus-Zone Setup card in Waiting for Approval with 8/8 checklist ticks and all screenshots.
- LL-02 Focus-Zone Checklist card approved.
- LL-03 Clockify Quick-Start card approved.
- Time-Ledger Sheet rows for Setup: tags (no blanks / overlaps).
- Insightful green status, Clockify workspace visible to manager.
Phase B (Orientation & Mind-sets) may only start after manager posts ✅ on LL-01 & LL-03.
Phase B – Orientation & Mind-sets (≈ 45 – 60 min real time)§
Goal → arrive at a rock-solid mental model of the Solo-Team OS before you dive into the eight subsystems.
| New # | Action (+ owner) | Clockify Tag | Evidence that must exist | Primary SOP / Resource |
|---|---|---|---|---|
| B-1 | Skim Operator Orientation PDF (Operator) Drive ▸ 04-OPERATORS-INDEX ▸ Orientation v1.2 |
Orient:PDF |
✓ mark on PDF checklist inside card LL-03 | Orientation PDF |
| B-2 | “120-word overview” prompt (Coach)👉 Give me a 120-word overview of the entire Solo-Team OS |
Orient:120w |
Paragraph pasted under ORIENT tab in Learning-Log – Work-Intake file | KQ-SOP-1 (Coach) |
| B-3 | ASCII system map prompt (Coach)👉 ASCII diagram of the Solo-Team OS |
Orient:ASCII |
ASCII block pasted in same tab | KQ-SOP-1 |
| B-4 | Mind-set Snapshot skim (Operator) (Appendix of Orientation PDF) |
Orient:Mindset |
List the three mind-sets that resonated most in Learning-Log | Mind-set Snapshot |
| B-5 | Quick self-quiz (Coach)/quiz orientation until ≥ 80 % |
Orient:Quiz |
Quiz % + attempt # recorded in Quiz tab | KQ-SOP-1 |
| B-6 | Mini-reflection (W↑ C↓ T→ M) (Operator) | Orient:Reflect |
4-bullet reflection in Reflection tab; mark Done? ☑ | LS-SOP-0 |
Pass gate: card LL-03 SYSTEM ORIENTATION – Big Picture shows every checklist item ticked and all five Clockify entries are linked & overlap-free.
1 · Cards you add / verify on the personal board for Phase B§
| # | Card title (copy verbatim) | Put it in list … | Label(s) | Why it must be there / how it’s used |
|---|---|---|---|---|
| 1 | LL-03 SYSTEM ORIENTATION — Big Picture | 🚀 Learning Loop | 🟣 Learning | Holds the Phase B checklist above. Timer links go in comments; Learning-Log links in description. |
| 2 | TEMPLATE – Subsystem Study Cycle | Templates (far right) | 🟣 Learning | Source card operators duplicate 8× during Phase C. Stores the 9-phase checklist and Coach prompt snippets. |
| 3 | Mind-set Snapshot Cheat-Card | 🟣 Learning / Kaizen (pin near top) | 🟣 Learning | Card description embeds the Mind-set table (copy from PDF). Quick reference during daily work & retros. |
(Cards from Phase A stay put: BOARD GUIDE, Clockify links, etc.)
2 · Butler / Automation tweaks for Phase B§
| Trigger | Butler rule | Result |
|---|---|---|
| When card LL-03 is moved to Done | Create checklist “Phase C ready?” on TEMPLATE – Subsystem Study Cycle and highlight it | Nudges the operator to start duplicating for the 8 subsystems. |
(No repeaters needed; Phase B is a one-shot learning burst.)
3 · SOP & quick-start artefacts referenced§
- SEC-SOP-1 (for Gmail — already completed in Phase A)
- Operator Orientation v1.2 PDF
- Mind-set Snapshot (appendix of the PDF)
- KQ-SOP-1 (Solo-Team Coach command set)
- LS-SOP-0 (Boot-camp master procedure, Phase B section)
Everything above is finished once LL-03 is green-ticked and the manager sees:
- Learning-Log ORIENT, Quiz & Reflection tabs populated
- Sheet Ledger shows 5 linked
Orient:*rows totalling ≈ 45–60 min - No unlinked timers in Clockify
✅ Phase B now fully specced.§
Tell me what you’d like to adjust (timings, card names, Butler logic, etc.) and we’ll iterate!
Phase C — Subsystem Mastery Loop§
v C-1.0 (8 subsystems × 9 micro-steps = ± 6–8 h net time)
Goal — prove you can explain, use, and teach back every subsystem of the Solo-Team OS before running the Sim-Day. You’ll cycle once through the 9-step learning micro-pattern for each of the eight subsystems in the order shown. Every micro-step is a discrete Clockify timer, a Sheet row, and a chunk in your Learning-Log Doc.
📋 Quick index of the eight subsystems & card IDs§
| Order | Subsystem | Trello study-card ID (copy LL-04 template) | Clockify tag prefix (use for all 9 timers of that subsystem) |
|---|---|---|---|
| 1 | Work-Intake & Prioritisation | LL-04-1 WP | Learn:Work-Intake: |
| 2 | Time-Tracking & Proof | LL-04-2 TT | Learn:Time-Tracking: |
| 3 | Daily Close-out & Hygiene | LL-04-3 DH | Learn:Daily-Hygiene: |
| 4 | Weekly / Monthly Rituals & Invoicing | LL-04-4 WR | Learn:Rituals: |
| 5 | Meeting Sync & Action Capture | LL-04-5 MS | Learn:Meeting-Sync: |
| 6 | Knowledge Query & Self-Learning | LL-04-6 KQ | Learn:Knowledge: |
| 7 | Gap-Fix & Continuous Improvement | LL-04-7 GF | Learn:Gap-Fix: |
| 8 | IT-Security & Compliance | LL-04-8 SEC | Learn:IT-Security: |
(The board already contains the eight LL-04 duplicates; just work top-to-bottom.)
🛠 The 9-Step Micro-pattern (repeat for each subsystem)§
| Step | Clockify tag suffix | What you do | SOP / Tool | Proof you paste |
|---|---|---|---|---|
| P1A | P1A-OrientOS |
Ask Oracle Bot → 👉 120-word overview of the entire OS |
KQ-SOP-1 | Paragraph in Orient tab |
| P1B | P1B-OrientXchg |
👉 Explain how <Subsystem> exchanges inputs & outputs |
— | Context paragraph |
| P1C | P1C-OrientMission |
👉 Summarise mission & payoff in ≤75 words |
— | 75-word blurb |
| P1D | P1D-OrientASCII |
👉 ASCII diagram of <Subsystem> |
Oracle Bot | ASCII block |
| P2 | P2-Read |
Read Markdown overview + key SOPs listed in card description | Repo (Drive/GitHub) | Tick “README read” on card |
| P3 | P3-WGLL |
Scan WGLL screenshots (Gallery link on card) | WGLL Gallery | Paste fave PNG or short note |
| P4 | P4-DeepDive |
👉 /deepdive <Subsystem> → ask ≥5 Qs until clear |
Oracle Bot | Q\&A transcript + any Gap? lines |
| P5 | P5-TLDR |
Craft one 140-char TL;DR sentence | — | TL;DR line |
| P6 | P6-Quiz |
/quiz <Subsystem> until ≥ 80 % |
Oracle Bot | Score & attempt count |
| P7 | P7-Teach |
Record voice-note teach-back → bot rates until ≥ 4/5 | Drive + Oracle Bot | Link + final rating |
| P8 | P8-Reflect |
/reflect <Subsystem> → W↑ / C↓ / Micro-experiment bullet |
Bot prompt | 3 bullets |
| P9 | P9-MoveOn |
Tick “Subsystem studied” checklist → move card Done | Trello | Card in Done column |
🗂 Where everything lands§
| Artefact | Lives here | Checked by |
|---|---|---|
| Clockify 9 entries | Ledger ▸ Subsystem rows | Manager (Sheet filter) |
| Orient / Deep-Dive etc. | Learning-Log |
Systems-Ops Lead |
| Trello study-card | Done list, all checklist ticks green | Manager quick scan |
| Unanswered “Gap?” lines | Auto-create 🔴Knowledge-Gap post → GF-SOP-1 | Systems-Ops Lead (within 2 h) |
🔑 Success criteria for one subsystem§
- 9 Sheet rows linked, no overlaps, correct prefix & suffix.
- Learning-Log file green-coloured (Done? checkbox ticked).
- Trello LL-04-x card in Done with full tick-list.
- Oracle Bot quiz ≥ 80 %, Teach-Back rating ≥ 4/5.
- No open gaps – or, if one exists, GitHub Issue already opened.
Complete that eight times → Phase C done.
Time guidance • Average micro-step ≈ 6–8 min. • 8 subsystems × 9 steps ≈ 72 steps → ~ 6–8 h net focused time. • Split across two calendar days if attention drops (respect Focus-Zone rules).
Move each subsystem card only when all nine steps are green—partial progress stays in 🚀 Learning Loop list.
Phase D – “Sim-Day Boot Loop” (Capstone Day)§
v 1.0 · 2025-05-16 – run after Phases A +B +C are 100 % green-ticked
1 Purpose & Success-Criteria (why this phase exists)§
| Goal | Measurable proof |
|---|---|
| Operator can execute the entire Solo-Team OS unassisted. | Manager receives a full evidence chain (Trello → Clockify → Insightful → Digest → WeekMetrics → Invoice) and needs zero back-channel nudges. |
| Artefacts match “What Great Looks Like”. | All green cells in the grading rubric (section 4). |
| Cycle time awareness. | Operator finishes Sim-Day in ≤ 3 real hours; no running timers afterwards. |
2 Prerequisites§
- Phase A +B +C ✓ (all Learning-Log files green, Oracle bot live).
-
Personal Trello board contains:
-
Sim-Day Sandbox list (copied from template).
- Templates list (Daily Hygiene, Weekly Metrics, Mini-Retro, Invoice).
SIM-DAYproject exists in Clockify (billable = ON).- Insightful folder
OP-<Name>/Insightful/SIM-DAY/selected. - “Boot-Camp Time-Ledger” Sheet has a fresh Sim-Day tab.
3 Step-by-Step Runbook (≈ 3 h real time)§
Clockify rule – every bold time-box below = a separate timer with description
SIM:<StepCode>:<Card-ID or Row>. Full tag list is printed on the Sim-Day Sandbox list cover card.
| Clock (real) | What you simulate | StepCode | Concrete actions & linked SOPs | Output / Evidence |
|---|---|---|---|---|
| 09 : 00 – 09 : 40 | Morning Work-Cycle | Q1 |
Daily Work-Cycle SOP • Copy 3 cards from Ready ⏳ → Q1 Doing (WIP ≤ 3). • One timer per card. • Complete & move to Q1 Done. |
3 Done cards + 3 Clockify entries + Insightful shots |
| 09 : 40 – 09 : 50 | Blocker escalation drill | BLOC |
Card SIM-BLK-01 spawns automatically. Label 🔴, run /alert, move to 🔴 Blocked. |
Alert message link + card comment timestamp |
| 09 : 50 – 10 : 20 | Ops-Sheet row work | OPS |
Work rows 12-14 in Sim-Sheet. Timer per row; description contains row link. |
3 Sheet rows updated + 3 timer links |
| 10 : 20 – 10 : 35 | Meeting Sync | MEET |
Open Meeting Outline PDF (board). Write 3 action items → Meeting Actions list. Stop timer "MEET – Daily Stand-up". |
3 action cards + TL;DR in card comment |
| 10 : 35 – 10 : 45 | Knowledge-Gap scenario | GAP |
Ask Coach a genuine question → follow Self-Help Checklist. If still stuck post 🔴Knowledge-Gap. |
Coach transcript + (maybe) gap post link |
| 10 : 45 – 11 : 05 | Inbox-Zero triage | TRIAGE |
Clear Inbox list; set Q1 To-Do ≤ 3 for next day. | Empty inbox + screenshot (optional) |
| 11 : 05 – 11 : 25 | Daily Hygiene & Digest | HYG |
TT-SOP-2 Evidence Export: • CSV • Insightful % PNG • Eisenhower PNG. DC-SOP-2 Digest W↑ C↓ T→ M → send & card → Waiting Approval. |
Hygiene card + Digest thread |
| 11 : 25 – 11 : 40 | Weekly Metrics + Invoice | MET INV |
RI-SOP-1 generate WeekMetrics.pdf. RI-SOP-3 draft Invoice.pdf (use today’s totals). Create Invoice card, attach PDF, ping manager. |
Weekly Packet card + Invoice card |
| 11 : 40 – 11 : 50 | Mini-Retro & Kaizen | RETRO |
RI-SOP-2 Mini-Retro: • Keep/Stop/Start in Miro mock frame. • Promote 1 Kaizen card to Q2 list. |
Retro Miro link + Kaizen card |
| 11 : 50 – 12 : 00 | Wrap & Proof-Check | WRAP |
• Verify no running timers. • Sheet “Sim-Day Ledger” matches Clockify total (±1 min). • Paste Digest thread link into Sheet Notes. |
Final Sheet totals + green Insightful status |
Real calendar date/time flexible—use local time; keep sequence intact.
4 Manager Grading Rubric§
| Area | Pass threshold |
|---|---|
| Work-Cycle | 3 cards done, Q1 Doing empty, WIP never > 3 |
| Timer evidence | 100 % entries linked; zero overlaps; SIM tag syntax used |
| Blocker drill | 🔴 card + /alert within 15 min (Slack timestamp) |
| Hygiene artefacts | CSV link opens; both PNGs legible; Eisenhower matches board |
| Daily Digest | Readable in ≤ 3 min; W↑ C↓ T→ M present; links valid |
| Weekly Packet | WeekMetrics.pdf + Invoice.pdf on correct cards |
| Retro + Kaizen | Miro link accessible; ≥ 1 blue-label Kaizen in Q2 |
| Ledger vs Clockify | Sheet total = Clockify total ± 1 min |
| Time discipline | No running timers after 12 : 00 local |
Pass = all green; any red = repeat Sim-Day next day (usually takes one attempt).
5 Clockify tag cheat-sheet§
SIM:Q1:<Card-ID>
SIM:BLOC:SIM-BLK-01
SIM:OPS:Row12
SIM:MEET:Stand-up
SIM:GAP:Coach
SIM:TRIAGE:InboxZero
SIM:HYG:Export
SIM:MET:WeekMetrics
SIM:INV:DraftInvoice
SIM:RETRO:MiniRetro
SIM:WRAP:Proof
(Printed on the Sim-Day list cover card for copy-paste ease.)
6 Hand-off email / Telegram snippet (send when finished)§
Subject: SIM-DAY package ready — <Your Name>
Sim-Day Boot Loop completed ✅
• Board https://trello.com/b/<id>
• Sheet Ledger https://docs.google.com/spreadsheets/d/<id> (Summary tab = <xx> min)
• Daily Digest https://t.me/c/<id>
• Invoice card https://trello.com/c/<id>
Please review—ready for live work!
7 Templates & Automation bits§
| Item | Where | Notes |
|---|---|---|
| Sim-Day Sandbox list | Trello template gallery | Contains cards SIM-01 … 06; top cover card lists tag syntax + schedule table. |
| Blocker spawn rule | Butler → every Sim-Day board at 09 : 40 | Create card "SIM-BLK-01 – simulated blocker" in list "📥 Inbox" |
| Evidence repeaters | Already in personal board Templates list | Daily Hygiene, Weekly Packet, Retro & Invoice are reused in live work. |
| Oracle bot | Live; no extra config | Operators can still use /find, /deepdive, /tip during Sim-Day, but rubric marks self-help not responsiveness. |
8 What to do after passing Sim-Day§
- Systems-Ops Lead moves operator’s personal board into the live Operators Hub workspace.
- Grant access to production Ops boards & Drive folders.
- Add operator to real Clockify Client Work projects.
- Archive the Sim-Day board for audit.
Phase D is now fully specified. Let me know if you want extra automation rules or a shorter compressed timetable; otherwise we can lock this in and proceed to Phase E (Boot-Retro + Graduation hand-off).
Phase E – Boot-Retro & Graduation§
(≈ 1–2 h; runs immediately after you finish Phase D’s Sim-Day)
| # | Time-box | Action & Tool | Clockify tag | SOP / Resource | Deliverable & Where it lives |
|---|---|---|---|---|---|
| E-1 | 15 min | Run the Boot-Retro prompt in Coach → /reflect Bootcamp Coach guides the WWW / EBI / PERMA / Mood reflection (+ “One insight · One experiment”). |
BootRetro |
RI-SOP-2 Mini-Retro & Kaizen | • Reflection bullets pasted in Learning-Log – Boot-Retro tab |
| E-2 | 10 min | Promote one Kaizen card that would make future onboarding smoother. Copy card to Q2 🟦 Kaizen list, label 🔵 Tracked, link it back in Boot-Retro card. |
Kaizen |
RI-SOP-2; GF-SOP-2 Weekly Kaizen Review | • New Kaizen card in personal board Q2 list |
| E-3 | 10 min | Graduate Request — create a Trello card in Waiting for Approval titled GRAD-<Name> – Bootcamp Complete. Attach: • Sim-Day board URL • Time-Ledger Sheet • Learning-Log folder link • Daily Digest thread • Invoice PDF • Boot-Retro card link. |
GraduateReq |
Onboarding checklist | • Graduate card with all links |
| E-4 | 5 min | Ping manager in /manager thread: “Graduate package ready – please review ✅❌”. |
— | Manager-Out-of-Loop design | • Telegram message |
| E-5 | Manager SLA 24 h | Manager review (uses Graduate-Checklist one-pager). If ❌ → fixes & resubmits. If ✅ → moves card to Approved, adds comment “Graduate 🎓”. | — | Graduate-Checklist (template) | • ✅ comment on card |
| E-6 | 20 min (manager-triggered) | Provision live access (manager): – Add operator to Client & Ops workspaces – Issue live Gmail/Slack credentials – Share real Ops Sheet & boards – Clone personal board into production workspace |
— | SEC-SOP-7 Off-boarding & Access (for future reference) | • Access log line in 00-ADMIN Sheet |
| E-7 | 10 min | Celebrate & log first real timer Operator starts a Client-Onboarding:Intro Clockify entry and posts a 🎉 GIF in /manager. |
Live:Kickoff |
Culture handbook | • First live Clockify entry (linked to fresh client card) |
✅ Graduation criteria§
| Area | Must be true |
|---|---|
| Boot-Retro & Kaizen | Reflection bullets + ≥ 1 Kaizen card in Q2 list |
| Evidence package | Sim-Day board, Ledger Sheet, Learning-Logs, Digest, Invoice all attached and accessible |
| Manager review | Graduate card moved to Approved within 24 h |
| Live access | Ops & client workspaces + credentials provisioned and acknowledged |
| First live timer | Starts within same day of approval |
📦 Trello template additions for Phase E§
| Card title (copy verbatim) | Put it in list… | Label(s) | Purpose / How it’s used |
|---|---|---|---|
| TEMPLATE – Boot-Retro & Kaizen | Templates | 🟢 Kaizen, 🟠 Ops | Butler drops every Friday (also used here for Boot-Retro). Checklist for WWW / EBI / PERMA / Mood + Kaizen-link field. |
| TEMPLATE – Graduate Request | Templates | 🟠 Ops | Source card for Step E-3; operator copies it, fills in all evidence links, and moves to Waiting for Approval. |
| 🤖 COACH FIRST – your 24 ⁄ 7 unblocker | 📥 Inbox (just under Board Guide) | 🟣 Learning | Already defined earlier – ensures they lean on the bot during Phase E fixes. |
(Templates list sits far right; Inbox & Waiting-for-Approval columns stay left-side for visibility.)
🔑 SOP & resource bundle referenced in Phase E§
| SOP / Resource | Why it’s invoked here |
|---|---|
| RI-SOP-2 Mini-Retro & Kaizen Promotion | Provides structure & tags for the Boot-Retro and Kaizen card. |
| GF-SOP-2 Weekly Kaizen Review | Ensures the promoted Kaizen feeds the continuous-improvement pipe. |
| Graduate-Checklist (one-pager) | Manager’s fast review rubric (mirrors Graduation criteria table). |
| SEC-SOP-7 Off-boarding & Access | Not executed now, but the same doc holds the Access log format the manager fills when provisioning live credentials. |
| Coach cheat-sheet & Self-Help Checklist | Operator uses them if the manager flags any gaps before approving. |
🕛 Outcome of Phase E§
- Operator is officially graduated and visible on live boards.
- All learning evidence is locked & searchable.
- Continuous-improvement loop seeded with at least one Kaizen card.
- Access provisioning is auditable via the 00-ADMIN log.
- Operator starts billing real client time the same day.
Tweak away: Adjust the 24-hour manager SLA or add extra account-creation steps if your stack changes. Everything else already plugs into existing Butler rules, Coach prompts, and evidence flows.
Below is a ready-to-copy card manifest for the “Start-Here – Learning Ops Board” (temporary board new operators clone on Day 0). Create two lists exactly as shown, then add the cards in the given order. Labels are suggestions; feel free to match your workspace palette (e.g. 🔵 Tracked, 🟠 Ops, 🟣 Learning).
List ① 🚀 Learning Loop§
| Card ID | Title (copy verbatim) | Purpose / When it’s “Done” | Suggested Labels | Pre-loaded Checklist items — edit freely |
|---|---|---|---|---|
| LL-00 | Board Guide — READ ME FIRST | Explains how to use this board & Clockify linking convention. | 🟣 Learning | — |
| LL-01 | Device & Focus-Zone Setup | Work OS profile hardened (SEC-SOP-1) AND focus-mode rules applied (SEC-SOP-2). 2-min proof-of-life timer logged. | 🔵 Tracked, 🟣 Learning | ① Install Telegram on personal phone → lifeline ② Create Work OS profile (non-admin) ③ Install Clockify, Insightful, Trello, Drive ④ Run 2-min “TEST – Device Ready” timer ⑤ Attach BitLocker & Insightful screenshots |
| LL-02 | Clockify Quick-Start | Join workspace, install desktop tracker & Insightful, start a timer on this card. | 🔵 Tracked | ① Join Solo-Team workspace ② Install tracker + set idle = 1 min ③ Link Insightful folder ④ Pin tracker tab ⑤ Add API key to Coach (opt) |
| LL-03 | System Orientation — Big Picture | Use Coach to grasp the whole OS before diving deeper. | 🟣 Learning | ① /explain Solo-Team OS② /map (ASCII system map)③ 140-char summary in Learning Log |
| LL-04 | Subsystem Study Cycle — TEMPLATE (duplicate per subsystem) | One full learning loop for each subsystem (8× copies). | 🟣 Learning | 1 /explain how <Subsystem> fits the whole2 /explain <Subsystem> --> System integration3 /explain <Subsystem> big picture4 /map ascii <Subsystem>5 Read Markdown overview + key SOPs 6 Ask ≥ 5 clarifying Qs & note answers 7 Voice teach-back → iterate until GPT says “Clear” 8 /drill <Subsystem> ≥ 80 %9 Reflection: W↑C↓T→M snippet |
| LL-05 | Learning Loop Reflection Log | Aggregate all subsystem 140-char summaries & biggest insight. | 🟢 Kaizen | — |
| LL-06 | Daily Evidence Export — Dry Run | Execute TT-SOP-2 on non-billable study timers. Attach CSV & PNGs. | 🟠 Ops | ① Stop timers ② Export “Today” CSV ③ Insightful % screenshot ④ Eisenhower PNG ⑤ Move to Waiting for Approval |
| LL-07 | Draft Daily Digest (Practice) | Compose W↑C↓T→M digest in Coach; manager gives mock ✅. | 🟠 Ops | ① Paste evidence links ② Coach template prompt ③ Send in /manager thread (sim) |
| LL-08 | Weekly Metrics & Mini-Retro (Sim) | Run RI-SOP-1 & RI-SOP-2 on dummy data; attach PDF, retro note. | 🟠 Ops | ① Export WeekMetrics ② GPT /weekly-metrics → PDF③ Mini-Retro K/S/S in Miro ④ Promote 1 Kaizen card |
| LL-09 | Invoice Packet & Follow-Up (Sim) | Build fake invoice PDF, move card → Waiting Approval, chase ✅. | 🟠 Ops | ① GPT /invoice-draft② Save as PDF ③ /manager ping |
List ② 🛠 Sim-Day Tasks§
(Operators use these cards during LL-08 & LL-09 to practise the real daily workflow.)
| Card ID | Title | Scenario Aim | Labels |
|---|---|---|---|
| SIM-01 | Update FAQ – Ops Board Ready ⏳ | Pull Ready card → Personal Q1 Doing → complete → Done. | 🟠 Ops |
| SIM-02 | Ops-Sheet Row 42 – Price Update | Work directly in Sheet; log time with row link, no Trello card. | 🟠 Ops |
| SIM-03 | Write Blog Outline – Scheduled Q2 | Show picking a scheduled Q2 card when Q1 empty. | 🔵 Tracked |
| SIM-04 | Blocker Escalation Drill | Add 🔴, /alert, test 15-min SLA flow. |
🔴 Blocker |
| SIM-05 | Find SOP for Instagram Reels | Run Self-Help Checklist → Coach /find instagram → reflection. |
🟣 Learning |
| SIM-06 | Compose & Send End-of-Day Digest | DC-SOP-2 full flow using SIM evidence; manager mock ✅/❌. | 🟠 Ops |
How to load the template§
- Create a new Trello board in your personal workspace.
- Add two lists named exactly:
🚀 Learning Loopand🛠 Sim-Day Tasks. - Copy-paste each card title (the “Copy card” dialog keeps checklists intact).
- Link every timer you run to the corresponding card URL or SIM/Sheet row.
Tip: Once the operator finishes LL-09 with all ✅ icons, you promote their personal board to the real production Ops workspace and archive this learning board.
Now your Start-Here template seeds a complete, clock-tracked, self-paced boot-camp that certifies operators in the entire Solo-Team OS before they ever touch live client work.
Subsystem Study Card – step-by-step playbook§
(copy this card for every subsystem you have to master: Work-Intake, Time-Tracking, Daily Close-out …)
Clockify rule: Start a new timer for every numbered phase (1-9). Description format:
Learn:<Subsystem>:P<phase> – <tag>• Example:Learn:Time-Tracking:P1A – System Overview• If the task isn’t a Trello card or Sheet row, paste the heading link of your Learning-Log Google Doc as the first line.
| # | Phase & Tool | What you do | Proof you paste into the Learning-Log Doc |
|---|---|---|---|
| 1A | SYSTEM OVERVIEW GPT Coach |
👉 Give me a 120-word overview of the entire Solo-Team OS |
120-word paragraph |
| 1B | SUBSYSTEM ↔ ECOSYSTEM GPT Coach |
👉 Explain how the <Subsystem> exchanges inputs & outputs with the other subsystems |
Context paragraph |
| 1C | SUBSYSTEM CORE PURPOSE GPT Coach |
👉 Summarise the mission & payoff of <Subsystem> in ≤ 75 words |
75-word summary |
| 1D | ASCII FLOW DIAGRAM GPT Coach |
👉 Draw an ASCII diagram of <Subsystem> showing its key steps and data hand-offs |
ASCII block |
| Move on only when the four snippets are pasted beneath the “ORIENT” heading in your Doc. | |||
| 2 | 📚 READ Markdown repo |
Open <Subsystem>/README.md + its key SOPs. Read top-to-bottom. |
n/a |
| 3 | ⭐ WGLL GLANCE Gallery |
Spend ≤3 min scanning the ⭐ screenshots for this subsystem. | (optional) paste favourite PNG |
| 4 | 🤖 DEEP-DIVE & Q-A /deepdive <Subsystem> |
• Read the explainer the bot returns. • Ask clarifying questions until nothing feels vague. • If the bot can’t answer → start the line Gap? → and note it. |
Copy the Q-A transcript and any Gap? lines |
| 5 | 📝 PROGRESSIVE SUMMARY | Add one 140-character TL;DR sentence for this subsystem. | TL;DR line |
| 6 | ✅ QUIZ /quiz <Subsystem> |
Retake until score ≥ 80 %. | Final % score |
| 7 | 🎙 TEACH-BACK voice-note ↔ GPT |
• Record a voice-note explaining the subsystem end-to-end. • Bot returns rating 1-5. • Iterate until rating ≥ 4. |
Paste the bot’s final rating |
| 8 | 🔍 REFLECT /reflect <Subsystem> |
Answer: 1. What clicked? 2. What’s still fuzzy? 3. One micro-experiment I’ll try. |
Three short bullets |
| 9 | 📅 MOVE ON checkpoint | Tick the checklist “Subsystem studied” ✓ | Checklist tick + Trello card ➜ Done |
🔗 Link-naming fallback (when no Trello card / Sheet row exists)§
- Highlight the relevant heading in your Learning-Log Google Doc.
- Copy the link to this heading (
Insert → Bookmark → Copy link). - Paste it as the first line in the Clockify description.
- Prefix the description as usual, e.g.
https://docs.google.com/...#bookmark=id.abc123 – Learn:Time-Tracking:P4 – Deep-Dive.
(Use this only if the normal Trello/Sheet link really isn’t available.)
What “done” looks like for one subsystem§
- Trello Study-Card sits in Done with every checklist item ticked.
- Learning-Log Doc shows: the 4-pack Orient answers, Q-A transcript, TL;DR, Quiz % score, Teach-Back rating, Reflection bullets, plus any
Gap?lines. - Clockify dashboard shows 9 linked entries (
P1A … P9) and zero unlinked minutes for the session.
Repeat the card-copy process for the next subsystem until all eight subsystems are green-ticked—then you graduate to the Sim-Day tasks.
Solo-Team OS – Mind-set Snapshot§
(pin or print next to your screen – it’s the “operating system for your brain” while you work)
| Bucket | Core Mind-set / Framework | Street-Level Mantra | Daily Trigger |
|---|---|---|---|
| Prioritisation & Focus | Eisenhower Q1 ≤ 3 | “Fewer, faster.” – never drag a fourth card into Q1 Doing. | Each time you move a card. |
| Inbox-Zero | “Leave no loose ends.” – clear every list before clock-out so tomorrow starts clean. | 17 : 00 triage. | |
| Flow > Force | “If it feels heavy, reshuffle or escalate.” | Any task that drags > 15 min. | |
| Continuous Improvement | Kaizen Loop | “One tweak a week.” – surface at least one improvement in Friday Mini-Retro. | RI-SOP-2 card. |
| Teach-Back | “Explain it → Own it.” – voice-note a concept till GPT rates ≥ 4/5. | Step 7 of every Learn card. | |
| Lean Execution | Pull, don’t Push (Kanban) | “Ready ⏳ → Doing → Done.” – grab only when you have capacity. | When Q1 Doing empties. |
| Andon Blocker | “Raise the red flag < 15 min.” – label 🔴 + /alert. |
Whenever stuck. | |
| Evidence & Trust | Audit-Trail Time Tracking | “Proof beats promises.” – every minute linked; screenshots green. | Start/stop timer. |
| Operator-Owned Follow-up | “I chase my ✅.” – you ping until manager approves. | Waiting-for-Approval column. | |
| Security & Professionalism | Work-Only Focus Zone | “Personal stays muted during work.” – Focus mode on desktop & phone. | Clockify timer start. |
| Least-Privilege | “Access is rented, never owned.” – request via ticket, revoke on finish. | New tool request. | |
| Tooling & Automation | Bot-First | “Ask the Coach before a human.” – /find, /map, /tip, /quiz. |
Any question. |
| Single Source of Truth (Markdown) | “Edit once, use everywhere.” – PR against repo before Miro/Trello tweaks. | When changing a process. | |
| Philosophical Glue | Flow-State Engineering | “Protect the time-distortion lane.” – carve deep-work blocks, mute noise. | Planning tomorrow’s Q1. |
| No-Grind Culture | “Alignment over hustle.” – if energy is low, rearrange cards, don’t brute-force. | Low mood-score in Digest. |
How to use this snapshot
- Scan it every morning before you hit “Start timer” to prime the right habits.
- Spot-check yourself at lunch: pick any mantra—can you prove you lived it today?
- Friday Mini-Retro: choose one row where you slipped; craft a micro-experiment for next week.
Keep these mind-sets alive and the rest of the Solo-Team OS will feel obvious.
Operator Tutorial§
How we’ll use Google Sheets and Google Docs side-by-side during the Learning Boot-Camp
1 · Why we split the tools§
| Purpose | Tool | Why this is the best fit |
|---|---|---|
| Time-tracking evidence (every study minute) | Google Sheet | Fast, row-based logging; totals & charts update automatically. |
| All learning artefacts (answers, screenshots, voice-note links, reflections) | Google Docs with Tabs | Rich media + inline comments; easy for managers to review by tab. |
Bottom line: one Sheet, one Docs folder with 8 tabbed files – nothing slips through the cracks.
2 · Google Sheet — “Boot-Camp Time-Ledger”§
2-A. Make your personal ledger§
- Open the master template: Drive ▸ 04-OPERATORS-INDEX ▸ Templates ▸ Time-Ledger_Template.
- File ▸ Make a copy → rename to
TL-<YourName>-BootCamp. - Move the copy into your OP-
_Drive ▸ Learning-Log folder.
2-B. Ledger layout§
| Column | What you type | Example |
|---|---|---|
| Date | Auto-filled by NOW formula; don’t touch. | 2025-05-16 |
| Start HH:MM | Exact start time of that timer | 09:03 |
| End HH:MM | When you stopped that timer | 09:47 |
| Min | Sheet auto-calculates (=(End-Start)*1440). |
44 |
| Subsystem | Copy from timer description (Learn:Work-Intake:Orient). |
Work-Intake |
| Step/Tab | Orient / Read / … | WGLL |
| Clockify Link | Right-click the entry in Clockify > copy link; paste. | https://clockify.me/tracker/... |
| Brief Note | Optional – 5-word context or “see Docs tab”. | “Deep-Dive Q done” |
Rule: every timer has one row in the Sheet before you start the next timer.
2-C. Auto-totals & visuals§
“Summary” tab shows per-day totals and a pie chart of minutes per subsystem – no editing needed. Managers glance at this during Daily Hygiene.
2-D. Weekly hand-off§
At Friday 16:45 you’ll File ▸ Download ▸ CSV and drop it into the normal Evidence-Export flow (TT-SOP-2).
3 · Google Docs — “Learning Log” files with Tabs§
(recap in brief; full guide is pinned inside every Doc)
- Copy
Tabs_Template.docxfor each subsystem (01-08). -
Each tab matches one step of the 9-phase loop – fill in as you complete the step.
-
Paste answers (Orient 4-pack, ASCII, etc.).
- Insert images/audio ▸ Drive for screenshots or voice-notes.
- Tick the Done? tab only when all prior tabs have content.
- Use Insert ▸ Comment to ask for clarifications; managers reply inline.
- The file turns Green (Drive colour script) when all tabs are ticked.
4 · How the two tools connect§
| Action | Sheet | Doc |
|---|---|---|
| Start timer | Row appears immediately (Date, Start, Subsystem, Step). | — |
| Produce work (e.g., quiz) | — | Paste score in Quiz tab. |
| Stop timer | Fill End time → minutes auto-calc. Insert Clockify link. | — |
| Manager review | Checks Summary tab totals & random Clockify links. | Jumps to specific Doc tab, leaves comments. |
| Daily Hygiene export | “Today” CSV downloaded from Sheet. | Docs untouched. |
5 · Quick reference commands§
| Need | Shortcut |
|---|---|
| Add new row fast | Press Ctrl + ↓ in Sheet to jump to empty row. |
| Copy Clockify link | Click duration ▸ “Copy link”. |
| Embed voice note | In Doc: Insert ▸ Drive ▸ recent MP3. |
| Convert headings to tabs | Insert ▸ Building blocks ▸ Tabs (if enabled). |
| Ask bot for help | In chat: /tip time-tracking or /checklist focus-env. |
Done!§
Keep the Time-Ledger Sheet and your 8 Learning-Log Docs open in pinned Chrome tabs; switch Clockify descriptions & Sheet rows as you move through the scaffold. This pairing gives us airtight evidence and a rich learning portfolio.
Below is everything your operators (or you) need to clone, drop-in, and start using immediately.
1 · Google Sheet Template – “TL--BootCamp” §
How to create it
- Go to Drive ▸ 04-OPERATORS-INDEX ▸ Templates
- New ▸ Google Sheet → Rename to
TL-<YourName>-BootCamp- Paste the exact structure below (copy/paste rows 1-3, formulas auto-fill)
| A | B | C | D | E | F | G | H |
|---|---|---|---|---|---|---|---|
| Date | Start HH:MM | End HH:MM | Min | Subsystem | Step/Tab | Clockify Link | Brief Note |
| =TODAY() | 09:00 | 09:44 | =(C2-B2)*1440 |
Work-Intake | Orient | (paste link) | “4-pack done” |
| (keep adding rows…) |
Sheet Tabs
| Tab name | Contents / Formulae |
|---|---|
| Ledger (default) | Data-entry grid above (freeze row 1). |
| Summary | =QUERY(Ledger!A:H,"select A,sum(D) where A is not null group by A order by A",1) + Pie-chart of minutes by Subsystem. |
| Data Valid | Two named ranges used for drop-down validation: Subsystems = { "Work-Intake"; … "IT-Security" } Steps = { "Orient"; "Read"; … "Reflection" } |
| Hide Me | (Optional) Helper columns for other formulas—leave blank for operators. |
Conditional formatting: – If Min = “” → red background (prevents blank rows). – If Clockify Link cell is blank & End time is filled → amber background.
2 · Google Docs Template – “Learning Log - .doc” §
How to create it
- Inside OP-Drive ▸ Learning-Log, make 8 copies of the template—one per subsystem.
- Rename each file:
LL-01-Work-Intake,LL-02-Time-Tracking, …LL-08-IT-Security.
A. Enable Tabs (Google Docs)§
- In each file click Insert ▸ Building Blocks ▸ Tabbed Page.
- Rename the eight tabs exactly as shown:
Orient • Read • WGLL • Deep-Dive • TL;DR • Quiz • Teach-Back • Reflection • Done?
(Google rolls out Tabs gradually. If Tabs aren’t enabled, just use Heading 1 sections with the same names; managers can click the outline on the left.)
B. What goes inside each tab§
| Tab (Heading 1) | Operator pastes or writes… |
|---|---|
| Orient | The 4 answers from Orientation 1-A/B/C/D. |
| Read | Nothing to paste—check-box only: “✅ README + key SOPs finished”. |
| WGLL | One screenshot or short bullet list of key quality cues they noticed. |
| Deep-Dive | Q\&A transcript with Coach plus any “Gap?” lines they raised. |
| TL;DR | 140-character paraphrase. |
| Quiz | Score + date (Score = 92 % (on 2nd attempt)). |
| Teach-Back | Link to voice-note in Drive + GPT rating comment. |
| Reflection | Three bullets: What clicked · Still fuzzy · One micro-experiment I’ll try. |
| Done? | Tick-box → Insert ▸ Special characters ▸ ☑ when every prior tab populated. |
Drive colour script (optional): When the Done? box becomes ☑ the file colour auto-changes to green (easy visual scan).
C. Permissions & comments§
- Operators are Editors on their own Learning-Log files.
- Managers: Commenter.
- Systems-Ops Lead: Editor (to fix template drift).
- Comments for clarification stay inside the relevant tab; resolved when the operator updates content.
3 · Linking Sheet ↔ Docs§
-
In the Brief Note column of the Sheet row for each phase, paste the Docs tab URL (right-click heading ▸
Copy link). Example:https://docs.google.com/document/d/<ID>/edit#heading=h.9jh2... -
If a timer covers multiple micro-actions (e.g., reading plus WGLL glance in one 45-min block) you may list both steps in Step/Tab (
Read+WGLL) and paste two links in Brief Note, separated by newline.
4 · First-day sanity check list§
- Sheet contains at least one row with a valid Clockify link and minutes value.
- LL-01-Work-Intake file exists with the Orient tab filled.
- Manager opens Summary tab – sees a non-zero minute total for today.
- Manager clicks Orient tab link – contents match Orientation 4-pack answers.
When those four bullets are green, the foundational evidence chain is working—and the operator is free to motor through the scaffold with zero hand-holding.
Solo-Team OS – “Sim-Day Boot Loop” Final-Competence Test§
(One-day capstone run to prove you can execute the entire stack without help)
0 · Why this exists§
After you’ve finished the learning scaffold, you’ll run one compressed but fully-real Sim-Day.
- You treat Trello, Clockify, Insightful, Digest, Weekly metrics and Invoice exactly as you would in live client work.
- Managers grade only the artefacts—no DMs, no side-coaching. Pass = you’re cleared for production; Fail = repeat until green.
1 · Set-up (T-15 min)§
| Action | How |
|---|---|
| Copy board “Sim-Day Sandbox” | Template lives in 04-OPERATORS-INDEX ▸ Templates. Rename SIM-<YourName> |
| Clockify project | Create SIM-DAY (billable ON) |
| Insightful folder | Set to OP-Drive ▸ Insightful_Screenshot_Folders ▸ SIM-DAY |
| Sheet | Add new tab Sim-Day Ledger (same columns as normal ledger) |
| Learning Log | No changes—today’s deliverables go elsewhere |
2 · The Compressed Schedule§
| Clock | What you simulate | How long (real mins) | What to do / deliverable |
|---|---|---|---|
| 09 : 00 – 09 : 40 | Morning Work-Cycle | 40 | • Copy 3 cards from SIM ▸ Ready⏳ → Q1 Doing • Start one Clockify timer per card • Complete them; move to Q1 Done |
| 09 : 40 – 09 : 50 | Blocker scenario | 10 | Card SIM-BLK-01 auto-spawns in Inbox. Label 🔴, /alert, fill Blocked list comment, start next card. |
| 09 : 50 – 10 : 20 | OPS-Sheet row work | 30 | Row ❶-3 in Sim-Sheet. Log one Clockify entry with Row Link. |
| 10 : 20 – 10 : 35 | Meeting Sync | 15 | Open Meeting Outline PDF in board. Write 3 action items → Meeting Actions list. Stop timer “Meeting – Daily Stand-up”. |
| 10 : 35 – 10 : 45 | Knowledge Gap | 10 | Ask Solo-Team Coach anything genuinely fuzzy from the morning. Follow Self-Help Checklist; if still blank → post 🔴Knowledge-Gap in #systems-kitchen. |
| 10 : 45 – 11 : 05 | Inbox-Zero triage | 20 | • Clear Inbox • Q1 To-Do ≤ 3 for “next day” • Archive noise. |
| 11 : 05 – 11 : 25 | Daily Hygiene & Digest | 20 | Run TT-SOP-2: export CSV, % screenshot, Eisenhower PNG → attach to Hygiene card. Compose Digest (W↑ C↓ T→ M), move card → Waiting for Approval, send in /manager. |
| 11 : 25 – 11 : 40 | Weekly Metrics & Invoice (compressed) | 15 | • Run RI-SOP-1 script: generate WeekMetrics PDF (auto). • Draft Invoice PDF (template) with TODAY’s totals. • New Invoice card → Waiting for Approval + Telegram ping. |
| 11 : 40 – 11 : 50 | Mini-Retro & Kaizen | 10 | • Add Keep/Stop/Start note in Miro mock frame. • Promote one Kaizen card to Q2 To Do. |
| 11 : 50 – 12 : 00 | Wrap & Proof-Check | 10 | • Ensure no running timers • Sheet Ledger tab has all rows, links valid. • Daily Digest link pasted in Sheet cell Notes column. |
Total real time ≈ 3 h
3 · Grading Rubric (manager checks after you finish)§
| Area | Pass criteria |
|---|---|
| Work-Cycle | 3 cards done, Q1 Doing empty, WIP cap never violated |
| Clockify ledger | 100 % entries linked (cards or Sheet rows), no overlaps |
| Blocker Escalation | 🔴 card + /alert within 15 min of spawn |
| Hygiene evidence | CSV link works, Insightful PNG readable, Eisenhower PNG matches board |
| Daily Digest | W↑ C↓ T→ M present, ≤ 3 min read, hyperlink to Hygiene card |
| Weekly Packet (sim) | WeekMetrics + Invoice PDFs attached to correct cards |
| Retro & Kaizen | Miro link present; one Kaizen card on board |
| Sheet Summary | Minutes match Clockify total ±1 min |
| Time discipline | No running timers after 12 : 00 |
Pass = all green boxes. Fail any cell → run Sim-Day again tomorrow.
4 · Clockify description conventions for Sim-Day§
SIM:<StepCode>:<Card-ID or Row> — examples
SIM:Q1.1:SIM-001
SIM:OPS:Row12
SIM:MEET:Daily-Standup
SIM:BLOC:SIM-BLK-01
SIM:HYG:Export
SIM:INV:Draft
(StepCode list is printed on the board cover for copy-paste ease.)
5 · Hand-off email template (send when you finish)§
Subject: SIM-DAY package ready –
Hi team, Sim-Day Boot Loop completed ✅ • Board: https://trello.com/b/xxxx• Sheet Ledger:https://docs.google.com/spreadsheets/d/xxxx(Summary tab = xx min) • Daily Digest thread:https://t.me/c/...• Invoice card:https://trello.com/c/...Let me know if anything looks off. Ready for live work! Cheers, \
Copy-paste that, tweak links, hit send. Done. ✌️