CM validation · MIS validation design · folder relationships · phone triggers · code-from-sheets

1 · CM VALIDATION TOMORROW — exact path (3 steps)

Expected invoice numbers (so you know what "right" looks like)

2 · MIS VALIDATION DESIGN (parallel to CM)

Same skeleton. Sacrificial test mode = use a fake ticker (e.g., TESTAAA) that doesn't pollute production decisions or the trade log.

Proposed 15-test MIS validation framework

Action item: when you're ready, I'll write docs/MIS_VALIDATION_PLAN.md with full per-test detail (similar to CM_VALIDATION_PLAN.md). Tonight = framework only.

3 · FROZEN REPOS — relationships, not deletions

Per your decision: keep all 5. Map their connections + likely future merge-points.

The "where do they all link in" answer

Future BOS umbrella architecture (your stated vision):

HookStreet-Business-OS (umbrella)
  ├── sheets/ (BOS-v1 Apps Script — Monthly Obligations engine)        ✅ ACTIVE
  ├── sheets-v2/ (BOS-v2 Apps Script — Monthly Obligations v2 engine)  ✅ ACTIVE (no GitHub yet)
  ├── command-center/ (Next.js dashboard — visual front-end)           🔴 FROZEN
  ├── (future) lee-os.html (alt dashboard template)                    🔴 FROZEN (in zee78900/Lee)
  └── archive/ (xlsx historical OS attempts)                           ℹ STATIC

Outside the umbrella (keep standalone):
  ├── CM_Invoice_System (Mom's wholesale tool)
  ├── MIS (market intelligence)
  ├── eden-gardens-os (active client)
  ├── HookStreetServices-Site (public marketing site)
  ├── hookstreet-voice-intake (intake pipeline)
  ├── hookstreet-skills (Claude Code skills)
  ├── abnbcalc (STR calculator — utility tool)
  └── north-woodmere-lawn-coop (one-off proposal)

4 · HS_SRVC FOLDER — what it is

5 · CODE-FROM-SHEETS architecture decision

Apps Script has 2 project types. Each has tradeoffs.

Recommendation per system

6 · PHONE TRIGGERS — 5 patterns ranked

Goal: text/shortcut from phone → certain sheet does certain thing.

Recommended Pattern 1 implementation (the "Go" path)

// In any Apps Script project — bound or standalone
function doPost(e) {
  var data = JSON.parse(e.postData.contents);
  var action = data.action;
  var key = data.key;  // shared secret in Settings
  if (key !== getSecret_('PHONE_TRIGGER_KEY')) return ContentService.createTextOutput('FORBIDDEN').setMimeType(ContentService.MimeType.TEXT);

  switch (action) {
    case 'cm_save_invoice':       saveInvoice(); break;
    case 'cm_email_invoice':      emailInvoice(); break;
    case 'mis_send_power_hour':   POWER_HOUR_SEND(); break;
    case 'bos_daily_snapshot':    DAILY_SEND(); break;
    case 'capture_quick_idea':    saveQuickCapture_(data.text); break;
    default: return ContentService.createTextOutput('UNKNOWN_ACTION');
  }
  return ContentService.createTextOutput('OK');
}

iPhone Shortcut spec

• Shortcut name: "Trigger BOS" (or per-action: "CM Save Invoice", "MIS Power Hour")
• Action: Get Contents of URL
• URL: deployed Web App URL (https://script.google.com/macros/s/.../exec)
• Method: POST
• Headers: Content-Type: application/json
• Body: {"action":"cm_save_invoice","key":"<your-secret-key>"}
• Response → Show Notification

7 · OUTPUTS FORMAT — recommend HTML default

Per your phone-shortcut goal:

📋 TOMORROW'S PRIORITY ORDER

1. CM validation (Step 1-3 above) — 30 min
2. Open HS_SRVC_v1.xlsx → decide archive vs extract
3. Connect lawn-coop-proposal local → north-woodmere-lawn-coop GitHub (1 command)
4. Phone trigger Web App — pick which sheet to deploy first (recommend BOS for "send daily snapshot from phone")
5. If time: screenshot Apps Script trigger panels for MIS, BOS-v1, BOS-v2 → enables trigger cleanup phase