—— 04 Subsystem: Rituals & Invoicing/RI-SOP-2 - Mini-Retro & Kaizen Promotion (well-being).md ——§

DraftSOP · Procedure · RI-SOP-2 — Weekly Mini-Retro & Kaizen Promotion + Personal Pulse · 2025-05-14-r3§

Big-Picture Overview§

Block	Content
Purpose & Scope	Close every work-week with a compact 10-minute ritual that: 1⃣ captures Keep / Stop / Start insights in Miro, 2⃣ promotes one Kaizen idea to the Q2 backlog, 3⃣ logs a short Personal Pulse (WWW ✦ EBI ✦ PERMA ✦ Mood) so the manager can spot burnout trends early, and 4⃣ bundles everything into the Weekly Packet for Monday approval.
Map / Flow	`16 : 55` Card Repeater ➞ Mini-Retro Trello card drops → operator fills Miro K/S/S → copies summary & Pulse block into card → creates/updates 🔵 Kaizen card in Q2 To Do → attaches links to Weekly Packet card → `/sendMessage` “📦 Packet ready” in `/manager`.
Roles	Freelancer Operator · Ops Manager · Systems-Ops Lead · GPT Assistant
RACI Snapshot	R Operator · A Manager · C Sys-Ops Lead · I GPT
KPIs	Retro finished by 17 : 15 Fri (100 %) · ≥ 1 Kaizen/week · 100 % Pulse response rate
Tools	Trello (card repeater, Q2 list) · Miro retro frame · GPT `/pulse` prompt · Telegram `/manager`
Risks (ISO 31000)	Ritual skipped ⇒ process drift · No Kaizen ⇒ stagnation · Low PERMA scores unnoticed
Open Question	Pipe Pulse scores automatically to a Sheet dashboard?
Next Action	Run pilot this Friday; measure actual operator time (< 10 min).

Detailed SOP — Weekly Mini-Retro & Kaizen + Personal Pulse§

(≤ 7 high-level bullets)

#	Step & Owner	Key points / Controls
1. Card Spawn (16 : 55) Trello Butler	Card Repeater drops Mini-Retro card in Hygiene list.
2. Capture K / S / S Operator	Open Miro ▸ Retro frame → add three bulleted columns: • Keep (what worked) • Stop (waste / pain) • Start (new ideas).
3. Personal Pulse Operator	In Mini-Retro card description, paste template & fill: `WWW (What Went Well):` … `EBI (Even Better If):` … `PERMA P/E/R/M/A:` _ / _ / _ / _ / _ `Mood word:` … (optional) run `/pulse` GPT prompt for guided questions.
4. Promote Kaizen Operator	Turn the strongest EBI insight into a Kaizen card: • Title = specific change • Place in Q2 To Do, label 🔵 `Tracked` • Link new card back in Mini-Retro card.
5. Bundle Weekly Packet Operator	Attach: • Miro link to Retro frame • Kaizen card link to already-spawned Weekly Packet card (from RI-SOP-1).
6. Manager Ping Operator	Telegram `/sendMessage` in `/manager`: `📦 Weekly Packet ready – please review.`
7. Manager Review (Mon) Manager	• Skim Packet + Pulse (any PERMA score < 3 ⇒ check-in). • Tap ✅ or ❌ and choose Kaizen to action. • Move Packet card ➞ Archive after pay-cycle.

SLA — Retro & Packet ping sent by 17 : 15; manager review by 09 : 15 Mon.

WGLL (“What Great Looks Like”)§

Criterion	❌ Miss	✅ Meets	⭐ Exceeds
Timeliness	After 17 : 15	By 17 : 15	By 17 : 05
Kaizen idea	0 ideas	1 card in Q2	Card includes acceptance tests + ETA
Pulse completeness	Blank fields	All fields filled	Trend note & self-action added

Full reference screenshots live in Drive → 01-SYSTEMS/WGLL_Gallery.

ArchitectureSnapshot JSON§

{
  "version_id": "2025-05-14-r3",
  "system_level": "Procedure",
  "lifecycle_state": "DraftSOP",
  "target_name": "RI-SOP-2 – Weekly Mini-Retro & Kaizen + Personal Pulse",
  "parent_name": "Weekly / Monthly Rituals & Invoicing",
  "last_updated": "2025-05-14T22:35:00Z",

  "overview": {
    "purpose": "Provide a concise weekly reflection that surfaces improvements and well-being signals while feeding the Weekly Packet for approval.",
    "flow": [
      "16:55 Card Repeater spawns Mini-Retro card",
      "Operator records Keep / Stop / Start in Miro",
      "Operator fills Personal Pulse (WWW, EBI, PERMA, Mood)",
      "Operator promotes one Kaizen card to Q2 backlog (label 🔵)",
      "Attach Miro & Kaizen links to Weekly Packet card",
      "Send Packet ready message in /manager Telegram",
      "Manager reviews Monday, logs ✅/❌, selects Kaizen"
    ],
    "roles": ["Freelancer Operator", "Ops Manager", "Systems-Ops Lead", "GPT Assistant"],
    "kpis": [
      "Retro completed by 17:15 every Friday",
      "≥1 Kaizen card/week",
      "100% Pulse completion"
    ],
    "tools": [
      "Trello (card repeater, Q2 list)",
      "Miro",
      "GPT Telegram bot (/pulse)",
      "Telegram /manager"
    ],
    "risks": [
      "Skipped retros ⇒ process decay",
      "No Kaizen ideas ⇒ stagnation",
      "Low PERMA scores go unseen"
    ],
    "controls": [
      "Card Repeater enforces schedule",
      "Manager checks PERMA <3",
      "Kaizen cards tagged 🔵"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Personal-OS/SOP-04_Mini-Retro_Pulse_v0.3.gdoc"
  },

  "procedure_core": {
    "procedure_id": "RI-SOP-2",
    "name": "Weekly Mini-Retro & Kaizen + Personal Pulse",
    "purpose": "Ten-minute Friday ritual to reflect, improve and report team well-being.",
    "trigger": "Every Friday 16:55 local (Trello Card Repeater).",
    "inputs": [
      "Mini-Retro Trello card",
      "Miro Retro frame",
      "GPT /pulse prompt",
      "Weekly Packet Trello card"
    ],
    "responsible_role": "Freelancer Operator",
    "steps": [
      "Open Miro and add K/S/S bullets",
      "Copy summary into Mini-Retro card",
      "Fill Personal Pulse template (WWW, EBI, PERMA, Mood)",
      "Create or update Kaizen card in Q2 list (label 🔵) and link it",
      "Attach Miro & Kaizen links to Weekly Packet card",
      "Send Packet ready ping in /manager Telegram"
    ],
    "outputs": [
      "Completed Mini-Retro card with Pulse data",
      "Kaizen card in Q2 backlog",
      "Weekly Packet ready for review"
    ],
    "sla": "Packet sent by 17:15 Fri; manager reviews by 09:15 Mon.",
    "controls": [
      "Trello Card Repeater schedule",
      "Manager watches PERMA scores",
      "Kaizen label for easy tracking"
    ],
    "tools": [
      "Trello",
      "Miro",
      "GPT bot",
      "Telegram"
    ],
    "kpis": [
      "On-time completion",
      "Kaizen card created",
      "Pulse completion"
    ],
    "risks": [
      "Retro skipped",
      "No Kaizen ideas",
      "Well-being issues missed"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Personal-OS/SOP-04_Mini-Retro_Pulse_v0.3.gdoc"
  },

  "children": []
}

— End of RI-SOP-2 r3

—— 04 Subsystem: Rituals & Invoicing/RI-SOP-3 - Invoice Generation & Manager Approval.md ——§

DraftSOP · Procedure · RI-SOP-3 — Invoice Generation & Manager Approval · 2025-05-14-r1§

Big-Picture Overview§

Block	Content
Purpose & Scope	Convert the past week’s approved minutes & evidence into a PDF invoice and obtain manager approval so the next bi-weekly bulk payout can happen on time—regardless of which payment processor (PayPal, Wise, Crypto, etc.) is in use.
Map / Flow	Fri 17 : 05 duplicate Invoice-Template → fill totals & screenshots → export PDF → Trello Invoice card → `/sendDocument` in Telegram → manager ✅/❌ by Mon 09 : 15 → two approved invoices trigger Mon/Tue payout → manager pastes TxID / payment ref → operator confirms receipt → card → Archive.
Roles	Freelancer Operator · Ops Manager · Finance Admin · Systems-Ops Lead · GPT Assistant
RACI	R Operator · A Ops Manager · C Finance Admin · I Systems-Ops / GPT
KPIs	100 % invoices sent by 17 : 15 Fri · 100 % manager action by 09 : 15 Mon · 0 re-submits after 2nd attempt · Payout released by Tue 17 : 00
Tools	Google Docs Invoice-Template · Google Sheets WeekMetrics & Exceptions · Insightful · Trello · Telegram
Risks (ISO 31000)	Mis-totaled hours · Wrong rate · Missing Insightful proof · Late approval delays cash-flow
Next Action	Pilot run this Friday; validate template fields & manager SLA.

Detailed SOP — Weekly Invoice Loop (≤ 7 bullets, imperative verbs)§

#	Step & Owner	Key points / Controls
1 · Duplicate Template Operator	Open `Invoice_Template_v1.0.gdoc` in 02-Templates/Finance → File › Make a copy → rename `INV_YYYY-WK##_<Name>`.
2 · Fill Data	• From WeekMetrics tab copy: total billable minutes, hourly rate, amount. • Paste Insightful weekly % chart PNG. • Insert Drive link to Exceptions tab (or “None”). • Set Period Covered (Fri–Thu).
3 · Generate PDF	File › Download › PDF → save to 02-OPERATIONS/Reports_Archive. Check filename matches card title.
4 · Create Trello Invoice Card	On Personal board Hygiene list: `Add card` title `INV_YYYY-WK##_<Name>` → attach PDF → label 🔵 Tracked → move to Waiting for Approval.
5 · Notify Manager	In `/manager` Telegram thread: `/sendDocument <PDF>` `Invoice WK## ready for approval`
6 · Approval Loop	Manager SLA: react ✅/❌ by Mon 09 : 15. • On ❌ operator fixes & re-sends (repeat Step 5).
7 · Bulk Payout & Close	After two approved invoices: manager runs bulk payout (processor of choice), pastes TxID or payment ref into card & PDF footer, moves card → Archive. Operator replies “Funds received”, loop closed.

SLA — Invoice PDF in Waiting for Approval by Fri 17 : 15; funds landed by Tue 17 : 00 after second invoice.

WGLL (“What Great Looks Like”) Snapshot§

Criterion	❌ Miss	✅ Meets	⭐ Exceeds
Send time	After 17 : 15	By 17 : 15 Fri	By 17 : 00 Fri
PDF contents	Missing chart / link	All fields present	Includes short insights blurb
Manager reaction	> 09 : 15 Mon	By 09 : 15 Mon	Within 1 h of send
Payout ref	Not added	TxID in card & PDF	Ref + screenshot of transaction

ArchitectureSnapshot JSON§

{
  "version_id": "2025-05-14-r1",
  "system_level": "Procedure",
  "lifecycle_state": "DraftSOP",
  "target_name": "RI-SOP-3 – Invoice Generation & Manager Approval",
  "parent_name": "Rituals & Invoicing",
  "last_updated": "2025-05-14T22:10:00Z",

  "overview": {
    "purpose": "Transform weekly approved work minutes into an audit-ready PDF invoice, obtain manager approval, and ensure on-time bi-weekly payout.",
    "flow": [
      "Friday 17:05 duplicate Invoice-Template and rename",
      "Populate totals, Insightful chart, Exceptions link, period",
      "Export PDF and store in Reports_Archive",
      "Create Invoice card in Trello, attach PDF, label Tracked",
      "Send PDF via Telegram /manager thread for approval",
      "Manager reacts ✅/❌ by Monday 09:15; operator fixes if needed",
      "After two approved invoices manager executes bulk payout, pastes payment reference, card archived"
    ],
    "roles": [
      "Freelancer Operator",
      "Ops Manager",
      "Finance Admin",
      "Systems-Ops Lead",
      "GPT Assistant"
    ],
    "kpis": [
      "Invoices sent by 17:15 Friday (100%)",
      "Manager approval by 09:15 Monday (100%)",
      "Zero rejections after second submission",
      "Payout released by Tuesday 17:00"
    ],
    "tools": [
      "Google Docs Invoice-Template",
      "Google Sheets WeekMetrics & Exceptions",
      "Insightful dashboard",
      "Trello",
      "Telegram"
    ],
    "risks": [
      "Incorrect totals or rate",
      "Missing Insightful proof",
      "Late manager approval delays cash-flow"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Personal-OS/SOP-04_Invoice_Generation_v0.1.gdoc"
  },

  "procedure_core": {
    "procedure_id": "RI-SOP-3",
    "name": "Invoice Generation & Manager Approval",
    "purpose": "Weekly routine that converts approved minutes into an invoice PDF and secures manager approval for payout.",
    "trigger": "Every Friday at 17:05 local.",
    "inputs": [
      "Invoice_Template_v1.0.gdoc",
      "WeekMetrics and Exceptions tabs (Google Sheet)",
      "Insightful weekly productivity chart",
      "Telegram /manager thread"
    ],
    "responsible_role": "Freelancer Operator",
    "steps": [
      "Duplicate Invoice-Template, rename with week number",
      "Fill totals, insert Insightful chart, link Exceptions, set period",
      "Export PDF and store in Reports_Archive",
      "Create Trello Invoice card, attach PDF, label Tracked, move to Waiting for Approval",
      "Send PDF and message in /manager Telegram thread",
      "Respond to manager ❌ with corrections until ✅",
      "Manager executes bulk payout after two approved invoices, adds payment reference, archives card"
    ],
    "outputs": [
      "Invoice PDF stored in Drive",
      "Trello Invoice card with approval status",
      "Payment reference logged"
    ],
    "sla": "PDF ready by 17:15 Friday; manager approval by 09:15 Monday; payout by Tuesday 17:00.",
    "controls": [
      "Template version-controlled in 02-Templates/Finance",
      "PDF & TxID retained 7 years",
      "Operator chase-loop (Telegram reminders)"
    ],
    "tools": [
      "Google Docs",
      "Google Sheets",
      "Insightful",
      "Trello",
      "Telegram"
    ],
    "kpis": [
      "On-time invoice send",
      "On-time approval",
      "Zero rejections after second submission"
    ],
    "risks": [
      "Mis-totaled hours",
      "Missing evidence",
      "Delayed approval"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Personal-OS/SOP-04_Invoice_Generation_v0.1.gdoc"
  },

  "insights": [
    {
      "note": "Processor-agnostic payout step (PayPal/Wise/Crypto) added; approval SLA clarified.",
      "date": "2025-05-14"
    }
  ],

  "children": []
}

— End of RI-SOP-3 v0.1

—— 04 Subsystem: Rituals & Invoicing/RI-SOP-4 - Bi-Weekly Payout & TxID Trail.md ——§

DraftSOP · Procedure · RI-SOP-4 – Bi-Weekly Payout & TxID Trail · 2025-05-14-r0§

Big-Picture Overview§

Block	Content
Purpose & Scope	Release every approved freelancer invoice once every two weeks and leave a bullet-proof audit trail (TxID / receipt / PDF / card / ledger) regardless of which payment processor is used (PayPal, Wise, crypto, etc.).
Map / Flow	Mon 09 : 15 detect two ✅ invoices in Waiting for Approval → verify totals in Payout Calculator tab → run bulk payment (processor of choice) → capture TxID / receipt PDF → update Invoice cards & PDFs → notify operator in Telegram → operator confirms funds → move cards to Archive → log line in Finance Ledger.
Roles	Freelancer Operator · Ops Manager · Finance Admin · Systems-Ops Lead · GPT Assistant
RACI Snapshot	R Ops Manager · A Ops Manager · C Finance Admin & Systems-Ops Lead · I Operator & GPT
KPIs	Payout released by Tue 17 : 00 100 % · TxID pasted in card and PDF 100 % · Zero unpaid approved invoices
Tools	Trello Invoice board · Google Sheet Ledger_2025 & Payout Calculator tab · Payment processors (PayPal / Wise / Crypto wallet) · Telegram `/manager` thread
Risks (ISO 31000)	Wrong amount / currency · Missing TxID · Processor failure · FX slippage · Audit docs misplaced
Open Questions	1) Split runs by lowest fee vs. freelancer preference? 2) Add FX-rate column to Ledger? 3) Dual-sign for payouts > \$2 000?
Next Action	Draft SOP (this doc) → 1-cycle pilot next Monday → review with Finance Admin.

Detailed SOP — Bi-Weekly Payout (≤ 7 bullets)§

#	Step & Owner	Key Points / Controls
1 · Pre-Payout Check (Mon 09 : 15) Ops Manager	• Open Waiting for Approval list. • Confirm exactly two Invoice cards for the last fortnight, each marked ✅. • If cards missing or ❌, ping operator; stop here.
2 · Verify Totals Ops Manager → Finance Admin	• Open Payout Calculator tab (Ledger_2025). • Check SUMIFS totals vs. Invoice PDFs. • Flag discrepancies (yellow) and resolve before paying.
3 · Execute Bulk Payment Ops Manager	• Choose processor (PayPal mass-pay / Wise batch / Crypto wallet). • Send full amounts in freelancers’ preferred currency. • Capture TxID / reference ID and download receipt PDF (if available).
4 · Update Artefacts Ops Manager	• Edit each Invoice PDF footer → paste TxID & date. • Attach receipt screenshot to Trello card. • Comment: “Paid – TxID XYZ”.
5 · Notify Operator Ops Manager	• Post in `/manager` thread: “Payment sent – TxID XYZ – confirm receipt”.
6 · Operator Confirmation Operator	• Reply “Funds received ✅”. • If funds not visible by Tue 16 : 00 → escalate.
7 · Archive & Ledger Entry Finance Admin	• Move Invoice cards → Archive list. • Append row to Finance Ledger (date, freelancer, amount, currency, TxID, processor, FX rate).

SLA — All payouts completed and ledger updated by Tue 17 : 00 (local HQ time).

WGLL (“What Great Looks Like” snapshot)§

Criterion	❌ Miss	✅ Meets	⭐ Exceeds
Timeliness	Paid after Tue 17:00	Paid Mon-AM	Paid Mon before 12:00 & operators confirm within 1 h
Traceability	TxID missing	TxID in card or PDF	TxID + receipt PDF + FX rate noted
Accuracy	Amount off by ≥\$1	Exact to cent	Exact & FX fee < 1 %

(Full exemplars live in 01-SYSTEMS/WGLL_Gallery.)

ArchitectureSnapshot JSON§

{
  "version_id": "2025-05-14-r0",
  "system_level": "Procedure",
  "lifecycle_state": "DraftSOP",
  "target_name": "RI-SOP-4 – Bi-Weekly Payout & TxID Trail",
  "parent_name": "Rituals & Invoicing",
  "last_updated": "2025-05-14T21:55:00Z",
  "overview": {
    "purpose": "Release every approved freelancer invoice twice a month and record an immutable payment trail.",
    "flow": [
      "Mon 09:15 verify two ✅ invoices in Waiting for Approval",
      "Cross-check totals in Payout Calculator tab",
      "Execute bulk payment via PayPal / Wise / Crypto",
      "Capture TxID or reference and download receipt PDF",
      "Update Invoice cards and PDFs with TxID",
      "Notify operator in Telegram; operator confirms receipt",
      "Archive cards and append entry in Finance Ledger"
    ],
    "roles": [
      "Freelancer Operator",
      "Ops Manager",
      "Finance Admin",
      "Systems-Ops Lead",
      "GPT Assistant"
    ],
    "raci": {
      "Responsible": ["Ops Manager"],
      "Accountable": ["Ops Manager"],
      "Consulted": ["Finance Admin", "Systems-Ops Lead"],
      "Informed": ["Freelancer Operator", "GPT Assistant"]
    },
    "kpis": [
      "Payout released by Tue 17:00 (100%)",
      "TxID pasted in card and PDF (100%)",
      "0 unpaid approved invoices per cycle"
    ],
    "tools": [
      "Trello Invoice board",
      "Google Sheets Finance Ledger & Payout Calculator",
      "Payment processors (PayPal, Wise, Crypto)",
      "Telegram /manager thread"
    ],
    "risks": [
      "Wrong amount or currency sent",
      "Missing TxID / audit proof",
      "Processor outage or FX slippage",
      "Payment delayed beyond SLA"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Personal-OS/SOP-04_Bi-Weekly_Payout_TxID_v0.1.gdoc"
  },
  "procedure_core": {
    "procedure_id": "RI-SOP-4",
    "name": "Bi-Weekly Payout & TxID Trail",
    "purpose": "End-to-end workflow to pay freelancers and record proof.",
    "trigger": "Two consecutive weekly invoices approved (Mon 09:15).",
    "inputs": [
      "Trello Invoice cards (✅)",
      "Payout Calculator tab totals",
      "Invoice PDFs",
      "Payment processor account"
    ],
    "responsible_role": "Ops Manager",
    "steps": [
      "Verify two ✅ invoices are ready",
      "Cross-check totals in Payout Calculator",
      "Execute bulk payment and capture TxID/receipts",
      "Update Invoice PDFs and Trello cards with TxID",
      "Notify operator in Telegram to confirm receipt",
      "Archive Invoice cards and log entry in Finance Ledger"
    ],
    "outputs": [
      "Paid Invoice PDFs with TxID",
      "Receipt PDF/screenshots",
      "Trello card comments with TxID",
      "Finance Ledger row"
    ],
    "sla": "All payouts & ledger update by Tue 17:00.",
    "controls": [
      "Payout Calculator second-eye check",
      "TxID required in both card and PDF",
      "Finance Ledger immutable column lock"
    ],
    "tools": [
      "Trello",
      "Google Sheets",
      "Payment processors",
      "Telegram"
    ],
    "kpis": [
      "Timely payout",
      "Full traceability",
      "Zero unpaid approved invoices"
    ],
    "risks": [
      "Incorrect amount",
      "Missing TxID",
      "Processor failure"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Personal-OS/SOP-04_Bi-Weekly_Payout_TxID_v0.1.gdoc"
  },
  "insights": [
    {
      "note": "Removed PayPal-specific wording; processor now generic. Added optional dual-authorisation open question.",
      "date": "2025-05-14"
    }
  ],
  "children": []
}

— End of RI-SOP-4 r0

—— 05 Subsystem: Meeting Sync & Action Capture/00 Subsystem: Meeting Sync and action Capture.md ——§

DraftSOP · Procedure · MS-SOP-1 – Meeting Sync & Action Capture · 2025-05-15-r0§

Parent Sub-system — Meeting Sync & Action Capture (converts every scheduled or ad-hoc call into clear Trello actions in ≤ 15 min)

Big-Picture Overview§

Block	Content
Purpose & Scope	① Keep “live” conversations (daily 7-min blockers huddle, ad-hoc troubleshooting, client calls) tied to the Solo-Team OS. ② Auto-surface blockers & tasks as Trello cards so nothing dies in chat logs.
Map / Flow	Before call: host opens Meeting Template → During call: note live blockers, decisions → End: click Record (Meet) & drop Transcript into Drive `Transcripts-Inbox` → GPT `/digest` produces TL;DR + action list → paste TL;DR in #manager thread → run /actionize to push Trello cards → label 🔴 blockers if any.
Roles / RACI	Host R, Ops Manager A, Systems-Ops C, GPT I
KPIs	100 % meetings have TL;DR + Trello actions within 15 min · 100 % blocker cards labelled 🔴 and escalated
Tools	Google Meet (record, transcript) · Drive `Transcripts-Inbox` · GPT commands `/digest` `/actionize` · Trello Meeting Actions list · Telegram #manager
Risks	Transcript missing → lost actions · GPT hallucination · Duplicate cards
Controls	Drive on-create trigger reminds if transcript not saved · `/actionize` de-dupes by card title · Checklist at step 6

Detailed SOP — 7-Step Loop§

#	Step & Owner	Key-points / Controls
1. Prep (−1 min)	Host	Open Meeting Template.md (agenda, blockers table).
2. Record On	Host	Start Meet recording for automatic transcript; announce.
3. Round-table (≤ 7 min)	Everyone	Each participant: What I did / Blocked on / Next step. Host notes blockers.
4. Stop & Save	Host	End recording → transcript auto-drops to Drive `Transcripts-Inbox`.
5. Digest (≤ 3 min)	Host	In GPT chat: `/digest <drive-link>` → copy TL;DR + blockers + tasks.
6. Publish	Host	Paste TL;DR in #manager Telegram thread. Run `/actionize` → bot creates Trello cards under Meeting Actions list, links back to transcript.
7. Escalate blockers	Operator of card	If blocker: add 🔴, move card → Blocked / Escalate, trigger SOP-5.

Done-When: TL;DR posted, action cards created & assigned, blockers labelled — all < 15 min after call end.

WGLL (What Great Looks Like)§

❌ Miss	✅ Meets	⭐ Exceeds
TL;DR >15 min late	TL;DR + cards in ≤15 min	Plus personal reflection note posted; duplicate tasks auto-merged

ArchitectureSnapshot JSON§

{
  "version_id": "2025-05-15-r0",
  "system_level": "Procedure",
  "lifecycle_state": "DraftSOP",
  "target_name": "MS-SOP-1 – Meeting Sync & Action Capture",
  "parent_name": "Meeting Sync & Action Capture",
  "last_updated": "2025-05-15T01:10:00Z",

  "overview": {
    "purpose": "Convert every meeting into actionable Trello cards with TL;DR in ≤15 min.",
    "flow": [
      "Start Meet recording and agenda template",
      "Hold 7-min blockers round-table",
      "Save transcript to Drive",
      "GPT /digest generates TL;DR + task list",
      "Paste TL;DR in manager Telegram thread",
      "Run /actionize to create Trello action cards",
      "Label 🔴 blockers and escalate"
    ],
    "roles": ["Freelancer Operator","Ops Manager","Systems-Ops Lead","GPT Assistant"],
    "kpis": [
      "100% meetings with TL;DR & cards ≤15min",
      "100% blockers labelled"
    ],
    "tools": [
      "Google Meet recording",
      "Drive Transcripts-Inbox",
      "GPT commands /digest /actionize",
      "Trello Meeting Actions list",
      "Telegram #manager thread"
    ],
    "risks": [
      "Missing transcript",
      "GPT hallucination",
      "Duplicate or lost tasks"
    ],
    "controls": [
      "Drive on-create reminder for transcripts",
      "Actionize de-duplication by title",
      "Step-7 blocker escalation SOP-5"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Personal-OS/SOP-06_Meeting_Sync_v0.1.md"
  },

  "procedure_core": {
    "procedure_id": "MS-SOP-1",
    "name": "Meeting Sync & Action Capture",
    "purpose": "Fast, reliable conversion of meeting talk into trackable work.",
    "trigger": "Scheduled daily huddle or any ad-hoc call.",
    "inputs": ["Meeting agenda template","Google Meet session"],
    "responsible_role": "Meeting host (operator or manager)",
    "steps": [
      "Open agenda template; start recording",
      "Run 7-min blockers round-table",
      "Save transcript to Drive",
      "Run GPT /digest on transcript",
      "Paste TL;DR to Telegram #manager",
      "Run /actionize to create Trello cards",
      "Label and escalate any 🔴 blockers"
    ],
    "outputs": [
      "TL;DR message",
      "Trello action cards",
      "Escalated blocker cards"
    ],
    "sla": "TL;DR and cards posted within 15 min of call end."
  },

  "children": []
}

— End of MS-SOP-1 v0.1

—— 06 Subsystem: Knowledge Query & Self-Learning/01 Procedure: Instant Query via GPT.md ——§

DraftSOP · Procedure · KQ-SOP-1 — Instant Query & Generative Coach via GPT · 2025-05-15-r6§

Dual-mode bot for lightning-fast look-ups and creative assistance. Supersedes r5 – adds open-ended usage guidance, PII guard-rails, extended command set & full JSON.

Big-Picture Overview§

Block	Content
Purpose & Scope	Provide an always-on knowledge & creativity companion: 1️⃣ Structured commands (12) for deterministic look-ups, navigation, action prompts and check-lists. 2️⃣ Generative coaching — operators may ask any open-ended question (brain-storm, rewrite, translate, sanity-check, draft follow-up) so long as no PII or 00-ADMIN data is pasted. Think of the bot as a senior peer who knows every SOP and never sleeps.
Map / Flow	Open chat Solo-Team Coach → choose /command or plain-language prompt → read answer → if unclear run KQ-SOP-3 Self-Help Checklist → if still blocked tag `🔴Knowledge-Gap` in #systems-kitchen.
Roles / RACI	Freelancer Operator R · Systems-Ops Lead A · Ops Manager C · GPT Assistant I
KPIs	≥ 70 % questions self-resolved · Bot latency ≤ 2 s · “no-match” < 5 %
Tools	GPT-o3 chat · GitHub solo-team-sops (Markdown) · Google Drive mirror · Command-Index.md · (opt.) read-only Trello token
Risks (ISO 31000)	Stale repo ⇒ wrong answers · Accidental disclosure of confidential data · Command spam / rate-limit abuse
Controls	GitHub webhook re-trains GPT after every PR merge (< 10 min) · `/next` & `/whereami` throttled 60 s / user · Bot red-flags messages containing e-mails or legal keywords (“passport”, “SSN”, “bank”).

Two Ways to Use the Coach§

Mode	Best for	How to phrase	Guard-rails
Structured	Exact, repeatable look-ups	`/command argument`	Use `/help` for full list
Generative	Ideas, drafting, critique, translation, second-brain advice	Start with 👉 (optional cue) `👉 Draft a polite follow-up for an overdue invoice`	– No PII / contracts / client secrets – Break long inputs into ≤ 3-paragraph chunks

Pro-tip: Chain commands & creative prompts 👉 Draft an Instagram caption for this product (≤ 125 chars) then /checklist instagram-caption

Command Index v0.3 (bot replies with this on `/help`)§

Bucket	Command	Returns	Source / Logic
Look-up	`/explain <section>`	150-word summary	Exact heading match
	`/example <deliverable>`	Filled exemplar	`## WGLL` or `## Examples` block
	`/find <keyword>`	Top 5 SOP titles w/ links	Title + tag fuzzy search
Navigate	`/map`	ASCII System → Subsystem diagram	`docs/_architecture_map.md`
	`/drivepath <asset>`	Canonical Drive path	`drive_paths.yml`
Act	`/whereami <SOP>`	Current & next step, done-when	Regex on pasted headers (fallback: manual)
	`/next`	Next Q1 / Ready⏳ card	Trello API snapshot (read-only token)
	`/tip <domain>`	3 golden rules	Domain WGLL bullets
Audit	`/drill <section>`	Quiz until 100 %	Auto-generated Q\&A
	`/checklist <deliverable>`	WGLL table (❌/✅/⭐)	SOP WGLL block
Admin	`/reset`	Restart on-boarding flow	Static text + link

Commands that need external APIs degrade gracefully: if no token, bot tells user to paste context manually.

Detailed Loop (≤ 7 bullets)§

Open chat “Solo-Team Coach”.
Choose mode → /command or creative prompt.
Read & act. • Solved → continue work. • Not solved → run Self-Help Checklist (KQ-SOP-3).
Still blocked → post 🔴Knowledge-Gap in #systems-kitchen.
Systems-Ops Lead patches SOP → PR merge → webhook re-trains GPT (< 10 min).
Friday 5-min Doc↔Miro Sync (KQ-SOP-2) keeps diagrams aligned.

WGLL (What Great Looks Like)§

❌ Miss	✅ Meets (baseline)	⭐ Exceeds – knowledge multiplier
Fires ≤1 bot query then pings manager	Resolves need with ≤2 bot interactions	Saves useful Q\&A to Trello Knowledge Wins list for peers

ArchitectureSnapshot JSON (fully expanded)§

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "version_id": "2025-05-15-r6",
  "system_level": "Procedure",
  "lifecycle_state": "DraftSOP",
  "target_name": "KQ-SOP-1 – Instant Query & Generative Coach via GPT",
  "parent_name": "Knowledge Query & Self-Learning",
  "last_updated": "2025-05-15T00:30:00Z",

  "overview": {
    "purpose": "Serve deterministic look-ups AND free-form creative help directly from the Markdown SOP SSOT via GPT.",
    "flow": [
      "Operator issues /command OR generative prompt",
      "Bot searches Markdown / lookup tables OR performs creative generation",
      "Bot returns answer, draft, tip or checklist",
      "If unclear: operator runs Self-Help Checklist",
      "If still blocked: tag 🔴Knowledge-Gap in Systems Kitchen Telegram",
      "KQ-SOP-6 opens GitHub Issue & PR; when merged webhook retrains GPT (<10 min)"
    ],
    "roles": [
      "Freelancer Operator",
      "Systems-Ops Lead",
      "Ops Manager",
      "GPT Assistant"
    ],
    "raci": {
      "Responsible": ["Freelancer Operator"],
      "Accountable": ["Systems-Ops Lead"],
      "Consulted": ["Ops Manager"],
      "Informed": ["GPT Assistant"]
    },
    "kpis": [
      "≥70% questions self-resolved without manager",
      "GPT refresh <10 min after PR merge",
      "Command error rate <2%",
      "Average response latency ≤2 s"
    ],
    "tools": [
      "GPT-o3 chat",
      "GitHub repo solo-team-sops",
      "Google Drive Markdown mirror",
      "Command-Index.md",
      "Optional read-only Trello token",
      "Miro maps"
    ],
    "risks": [
      "Stale documents → wrong answer",
      "Sensitive data leak via generative mode",
      "Command spam or abuse",
      "Merge conflicts delay GPT refresh"
    ],
    "controls": [
      "GitHub webhook retrains GPT on every merge",
      "Rate-limit /next and /whereami to 60 s per user",
      "Bot highlights potential PII & refuses storage",
      "Friday Doc↔Miro sync ritual"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Knowledge/KQ-SOP-1_Instant_Query_v0.6.md"
  },

  "procedure_core": {
    "procedure_id": "KQ-SOP-1",
    "name": "Instant Query & Generative Coach via GPT",
    "purpose": "End-to-end loop to obtain answers, drafts or check-lists via chatbot commands or creative prompts.",
    "trigger": "Whenever the operator needs information or creative assistance.",
    "inputs": [
      "Operator question or work artefact",
      "Markdown SOP repository (GitHub main)",
      "Command-Index lookup tables",
      "Optional Trello board snapshot"
    ],
    "responsible_role": "Freelancer Operator",
    "steps": [
      "Open Solo-Team Coach chat",
      "Issue a structured /command OR a plain-language creative prompt (prefix 👉 optional)",
      "Evaluate the response and act on guidance",
      "If unclear, run KQ-SOP-3 Self-Help Checklist and retry",
      "If still unresolved, post 🔴Knowledge-Gap in Systems Kitchen Telegram",
      "Systems-Ops Lead patches SOP; PR merged; webhook retrains GPT",
      "Operator re-runs original query to confirm answer is now served"
    ],
    "outputs": [
      "Answer snippet, checklist, map, tip or creative draft",
      "If gap: GitHub Issue & PR link for audit trail"
    ],
    "sla": "Knowledge-Gap → PR merged & GPT updated within 24 h.",
    "controls": [
      "Command throttling for heavy API calls",
      "Webhook GPT retrain on merge",
      "PII keyword detector with user warning",
      "Friday Doc↔Miro sync sweep"
    ],
    "tools": [
      "GPT-o3 chat",
      "GitHub",
      "Google Drive",
      "Trello",
      "Miro"
    ],
    "kpis": [
      "Self-resolution rate ≥70%",
      "Bot latency ≤2 s",
      "PR merge → GPT refresh <10 min"
    ],
    "risks": [
      "Out-of-date knowledge base",
      "Operator bypass of checklist causing manager load",
      "Oversharing sensitive info in chat"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Knowledge/KQ-SOP-1_Instant_Query_v0.6.md"
  },

  "insights": [
    {
      "note": "Generative usage guidance added; operators encouraged to ask any open question within PII guard-rails.",
      "date": "2025-05-15"
    },
    {
      "note": "Extended command set now includes /map, /whereami, /next, /find, /drivepath, /tip, /checklist.",
      "date": "2025-05-14"
    }
  ],

  "children": []
}

— End of KQ-SOP-1 r6 (full spec)

—— 06 Subsystem: Knowledge Query & Self-Learning/02 Procedure: Doc ↔ Miro Sync Sweep.md ——§

DraftSOP · Procedure · KQ-SOP-2 — Doc ↔ Miro Sync Sweep · 2025-05-15-r1§

5-minute Friday ritual that keeps every visual map in Miro in lock-step with the Markdown “single-source-of-truth” (SSOT) stored in Drive + GitHub.

Big-Picture Overview§

Block	Content
Purpose & Scope	Prevent “diagram drift”. Every week the operator checks what changed in the Markdown SOP repo, reflects those edits on the public Miro maps, bumps the visible version tag, and flags any visual node that now needs a doc patch.
Map / Flow	Friday 16 : 40 • Pull latest `main` → scan change-log → open Miro Solo-Team OS board → update nodes & version tag → mark drafts → add “🔄 Needs Doc update” stickies if edits were made in Miro first → snapshot board PNG → attach to Weekly Metrics card.
Roles / RACI	Freelancer Operator R · Systems-Ops Lead A · Ops Manager C · GPT Assistant I
KPIs	100 % Doc ↔ Miro sync sweep done each Friday · ≤ 5 stale nodes detected in monthly audit
Tools	GitHub `solo-team-sops` · Google Drive mirror · Miro board Solo-Team OS · Trello Weekly Metrics ritual card
Risks (ISO 31000)	Visuals mislead newcomers · Version tags fall behind · Draft ideas leak into LIVE map
Controls	“LIVE banner” on each finalized SOP node • Orange dashed border = draft • Solid blue = live • Version tag (e.g. v3.2 · 2025-05-15) in board corner

Detailed SOP — Doc ↔ Miro Sync Sweep (6 steps)§

#	Step & Owner	Key points / Checks
1	Prepare – Git pull Operator	`git pull origin main` in `solo-team-sops` repo (or open Drive).
2	Scan Change-Log	In `CHANGELOG.md` filter last 7 days for `## [Changed]` entries; open each file diff.
3	Open Miro board	Frame Solo-Team OS – Master Blueprint; zoom 100 %.
4	Update visual nodes	• Rename, reorder or delete nodes to match Markdown headings. • Change border orange-dashed → blue-solid when a Draft SOP ships LIVE. • Insert new nodes for new SOPs; mark as orange-dashed.
5	Bump version tag	Edit top-right label: `vX.Y · YYYY-MM-DD` → today’s date.
6	Evidence & hand-off	Export board frame as PNG → attach to Weekly Metrics Trello card; add comment “Miro sync ✔”.

If the operator doodled new ideas in Miro earlier in the week: • Add sticky “🔄 Needs Doc update” and move node to orange-dashed until KQ-SOP-6 PR is merged.

WGLL (What Great Looks Like)§

❌ Miss (Red)	✅ Meets (Green)	⭐ Exceeds (Gold)
Tag still shows previous week’s date; > 2 nodes stale	Board tag updated; all new/changed SOPs represented; PNG attached to Weekly Metrics card	Adds mini-loom (≤ 60 s) walkthrough linking visual changes to Git diffs, shared in #system-updates

ArchitectureSnapshot JSON (schema-compliant)§

{
  "version_id": "2025-05-15-r1",
  "system_level": "Procedure",
  "lifecycle_state": "DraftSOP",
  "target_name": "KQ-SOP-2 – Doc ↔ Miro Sync Sweep",
  "parent_name": "Knowledge Query & Self-Learning",
  "last_updated": "2025-05-15T01:20:00Z",

  "overview": {
    "purpose": "Weekly 5-minute ritual that aligns Miro visual maps with the canonical Markdown SOP repository.",
    "flow": [
      "Friday pull latest GitHub main & review CHANGELOG",
      "Open Solo-Team OS Miro board",
      "Update node names, colours, connections to match Markdown",
      "Mark drafts with orange dashed border, lives with solid blue",
      "Update board version tag to today’s date",
      "Export PNG and attach to Weekly Metrics Trello card"
    ],
    "roles": [
      "Freelancer Operator",
      "Systems-Ops Lead",
      "Ops Manager",
      "GPT Assistant"
    ],
    "kpis": [
      "100% Doc ↔ Miro sync completed each Friday",
      "≤5 stale nodes detected per monthly audit"
    ],
    "tools": [
      "GitHub repo solo-team-sops",
      "Google Drive mirror",
      "Miro board",
      "Trello Weekly Metrics card"
    ],
    "risks": [
      "Diagram drifts out of date",
      "Draft nodes presented as live",
      "Version tag not updated"
    ],
    "controls": [
      "Orange dashed = draft; blue solid = live",
      "Live nodes must reference Markdown filename",
      "Version tag bump mandatory"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Knowledge/KQ-SOP-2_Doc-Miro_Sync_v0.1.md"
  },

  "procedure_core": {
    "procedure_id": "KQ-SOP-2",
    "name": "Doc ↔ Miro Sync Sweep",
    "purpose": "Guarantee visual maps and textual SOPs stay in sync.",
    "trigger": "Every Friday at 16:40 local (before Weekly Metrics export).",
    "inputs": [
      "solo-team-sops Git repository",
      "Miro Solo-Team OS board",
      "CHANGELOG.md"
    ],
    "responsible_role": "Freelancer Operator",
    "steps": [
      "Pull latest main & scan change log",
      "Open Miro board & locate master frame",
      "Apply edits: rename/add/remove nodes, update colours",
      "Update version tag",
      "Export frame as PNG and attach to Weekly Metrics card",
      "If edits were made in Miro first, add sticky '🔄 Needs Doc update'"
    ],
    "outputs": [
      "Miro board frame PNG (archived in Trello card)",
      "Up-to-date visual map",
      "Sticky notes for pending doc patches"
    ],
    "sla": "Completed before Friday 17:00; evidence attached.",
    "controls": [
      "LIVE banner on shipped SOP nodes",
      "Orange draft border until PR merged",
      "Weekly Metrics card comment logged"
    ],
    "tools": [
      "Git / GitHub",
      "Miro",
      "Trello"
    ],
    "kpis": [
      "Sync performed 100% of Fridays",
      "Zero high-severity drift incidents"
    ],
    "risks": [
      "Visual-doc mismatch misguides team",
      "Operator skips step under time pressure"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Knowledge/KQ-SOP-2_Doc-Miro_Sync_v0.1.md"
  },

  "children": []
}

— End of KQ-SOP-2 r1

—— 06 Subsystem: Knowledge Query & Self-Learning/03 Procedure: Self-Help Query Flow Checklist.md ——§

DraftSOP · Procedure · KQ-SOP-3 — Self-Help Query Flow Checklist · 2025-05-15-r1§

Big-Picture Overview§

Block	Content
Purpose & Scope	Give every operator a 5-minute, five-source playbook that must be executed before asking a human. The checklist turns “Where do I find…?” into either (a) a self-solved answer or (b) a clearly documented knowledge-gap to be patched.
Map / Flow	Need info → run Self-Help Checklist (Markdown repo 🡒 GPT commands 🡒 Miro map 🡒 Telegram search 🡒 Trello card) → answer found OR post 🔴Knowledge-Gap with evidence → KQ-SOP-6 Gap-Patch kicks in.
Roles / RACI	Freelancer Operator R · Systems-Ops Lead A · Ops Manager C · GPT Assistant I
KPIs	≥ 70 % questions self-resolved · Gap → PR merge < 24 h
Tools	GitHub/Drive Markdown repo · GPT `/find` `/explain` `/map` etc. · Miro Solo-Team OS board · Telegram search · Trello comments/WGLL
Risks	Operator skips steps · Search terms too narrow · Docs stale
Controls	Managers may reply “Finish checklist first” if evidence missing; GitHub webhook retrains GPT on merge

Detailed SOP — Five-Source Checklist (≤ 7 bullets)§

#	Step & Owner	Key points / Controls
1	Markdown repo search (Operator, 60 s)	In Drive or GitHub press `Ctrl + Shift + F` → search top 3 keywords → open matches.
2	GPT quick commands (60 s)	Try `/find <keyword>` then `/explain <section>` or `/tip <domain>`.
3	Miro map scan (45 s)	Zoom to “Solo-Team OS – Master Blueprint” → look for subsystem or SOP box.
4	Telegram history (45 s)	In #systems-kitchen & #reports search the keyword; skim last 30 days.
5	Trello artefact check (45 s)	If question relates to a card, open comments & cover/WGLL; else look in Knowledge Wins list.
6	Solved?	✅ Yes → continue work. ❌ No → proceed to Step 7.
7	Post 🔴Knowledge-Gap	In #systems-kitchen send: `🔴Knowledge-Gap` • “One-line question” • Links/screens proving steps 1-5 attempted. Tag `@Systems-Ops Lead`.

Time-box: entire checklist ≤ 5 min.

WGLL (What Great Looks Like)§

❌ Miss	✅ Meets (Good)	⭐ Exceeds (Great)
Asks manager without evidence	Posts 🔴 with 5 bullet-proof links/screens proving each checklist step	Solves alone, saves Q\&A as card in Knowledge Wins list + suggests PR patch for wording clarity in relevant Markdown SOP

ArchitectureSnapshot JSON§

{
  "version_id": "2025-05-15-r1",
  "system_level": "Procedure",
  "lifecycle_state": "DraftSOP",
  "target_name": "KQ-SOP-3 – Self-Help Query Flow Checklist",
  "parent_name": "Knowledge Query & Self-Learning",
  "last_updated": "2025-05-15T01:05:00Z",

  "overview": {
    "purpose": "Ensure operators exhaust self-service resources before escalating a knowledge question.",
    "flow": [
      "Search Markdown repo (Drive/GitHub)",
      "Use GPT commands /find /explain /tip",
      "Scan Miro Solo-Team OS map",
      "Search Telegram history",
      "Check Trello comments & Knowledge Wins list",
      "If still blocked: post 🔴Knowledge-Gap with evidence",
      "Gap triggers KQ-SOP-6 PR patch & GPT retrain"
    ],
    "roles": ["Freelancer Operator","Systems-Ops Lead","Ops Manager","GPT Assistant"],
    "kpis": [
      "≥70% questions self-resolved",
      "SOP gap to PR merge <24h"
    ],
    "tools": [
      "Google Drive & GitHub Markdown repo",
      "GPT command set",
      "Miro board",
      "Telegram",
      "Trello"
    ],
    "risks": [
      "Checklist skipped",
      "Search terms too narrow",
      "Stale documentation"
    ],
    "controls": [
      "Manager can request checklist proof",
      "Webhook retrains GPT on PR merge"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Knowledge/KQ-SOP-3_Self-Help_Checklist_v0.1.md"
  },

  "procedure_core": {
    "procedure_id": "KQ-SOP-3",
    "name": "Self-Help Query Flow Checklist",
    "purpose": "Five-step self-service routine before escalating any question.",
    "trigger": "Operator encounters information gap.",
    "inputs": [
      "Question needing answer",
      "Access to Drive/GitHub, GPT chat, Miro, Telegram, Trello"
    ],
    "responsible_role": "Freelancer Operator",
    "steps": [
      "Search Markdown repo for keywords",
      "Use GPT commands to query SOPs",
      "Scan Miro map for relevant subsystem/SOP",
      "Search Telegram history for prior answers",
      "Check Trello artefacts (comments, Knowledge Wins)",
      "If solved: continue work",
      "If not: post 🔴Knowledge-Gap with checklist evidence"
    ],
    "outputs": [
      "Answer found OR Knowledge-Gap escalation post"
    ],
    "sla": "Checklist completed within 5 min; PR patch merged <24 h after gap post.",
    "controls": [
      "Evidence links/screens required in escalation post"
    ],
    "tools": [
      "Drive/GitHub",
      "GPT",
      "Miro",
      "Telegram",
      "Trello"
    ],
    "kpis": [
      "Self-resolution rate",
      "Gap patch turnaround"
    ],
    "risks": [
      "Operator skips steps",
      "Docs outdated"
    ],
    "doc_link": "Drive:/01-SYSTEMS/Knowledge/KQ-SOP-3_Self-Help_Checklist_v0.1.md"
  },

  "children": []
}

— End of KQ-SOP-3 r1

—— 04 Subsystem: Rituals & Invoicing/RI-SOP-2 - Mini-Retro & Kaizen Promotion (well-being).md ——§

DraftSOP · Procedure · RI-SOP-2 — Weekly Mini-Retro & Kaizen Promotion + Personal Pulse · 2025-05-14-r3§

Big-Picture Overview§

Detailed SOP — Weekly Mini-Retro & Kaizen + Personal Pulse§

WGLL (“What Great Looks Like”)§

ArchitectureSnapshot JSON§

—— 04 Subsystem: Rituals & Invoicing/RI-SOP-3 - Invoice Generation & Manager Approval.md ——§

DraftSOP · Procedure · RI-SOP-3 — Invoice Generation & Manager Approval · 2025-05-14-r1§

Big-Picture Overview§

Detailed SOP — Weekly Invoice Loop (≤ 7 bullets, imperative verbs)§

WGLL (“What Great Looks Like”) Snapshot§

ArchitectureSnapshot JSON§

—— 04 Subsystem: Rituals & Invoicing/RI-SOP-4 - Bi-Weekly Payout & TxID Trail.md ——§

DraftSOP · Procedure · RI-SOP-4 – Bi-Weekly Payout & TxID Trail · 2025-05-14-r0§

Big-Picture Overview§

Detailed SOP — Bi-Weekly Payout (≤ 7 bullets)§

WGLL (“What Great Looks Like” snapshot)§

ArchitectureSnapshot JSON§

—— 05 Subsystem: Meeting Sync & Action Capture/00 Subsystem: Meeting Sync and action Capture.md ——§

DraftSOP · Procedure · MS-SOP-1 – Meeting Sync & Action Capture · 2025-05-15-r0§

Big-Picture Overview§

Detailed SOP — 7-Step Loop§

WGLL (What Great Looks Like)§

ArchitectureSnapshot JSON§

—— 06 Subsystem: Knowledge Query & Self-Learning/01 Procedure: Instant Query via GPT.md ——§

DraftSOP · Procedure · KQ-SOP-1 — Instant Query & Generative Coach via GPT · 2025-05-15-r6§

Big-Picture Overview§

Two Ways to Use the Coach§

Command Index v0.3 (bot replies with this on /help)§

Detailed Loop (≤ 7 bullets)§

WGLL (What Great Looks Like)§

ArchitectureSnapshot JSON (fully expanded)§

—— 06 Subsystem: Knowledge Query & Self-Learning/02 Procedure: Doc ↔ Miro Sync Sweep.md ——§

DraftSOP · Procedure · KQ-SOP-2 — Doc ↔ Miro Sync Sweep · 2025-05-15-r1§

Big-Picture Overview§

Detailed SOP — Doc ↔ Miro Sync Sweep (6 steps)§

WGLL (What Great Looks Like)§

ArchitectureSnapshot JSON (schema-compliant)§

—— 06 Subsystem: Knowledge Query & Self-Learning/03 Procedure: Self-Help Query Flow Checklist.md ——§

DraftSOP · Procedure · KQ-SOP-3 — Self-Help Query Flow Checklist · 2025-05-15-r1§

Big-Picture Overview§

Detailed SOP — Five-Source Checklist (≤ 7 bullets)§

WGLL (What Great Looks Like)§

ArchitectureSnapshot JSON§

Command Index v0.3 (bot replies with this on `/help`)§