MIS Folder — Finalization

1Code shipped to v1 today (4 clasp pushes)

v1 script (1yBMztL4…) is the only active production target. Old production script 1r9vWL… bound to 1cosuFr… sheet is dormant (triggers should be killed if any still fire). Sam confirmed in earlier session he killed them.

2Chronological inventory — every file, newest first

Compact ranking. Subdirectory contents covered in §3.

3Subdirectory breakdown

MIS-v1-script/ Keep — this is THE clasp project

• emailDailySnapshot.js — 6,900+ lines · email engine · just got SMS + Secrets functions added · ACTIVE
• Code.js — 1,400 lines · tab builders + earnings refresh · ACTIVE
• fse_foundation.js — FSE Session 1+3 code · ACTIVE
• mobile_command_center.js · runSACSUpgrade.js · appsscript.json · .clasp.json

This folder is gitignored (per MIS/.gitignore); managed via clasp. All today's pushes landed here. Sole source of truth for v1 script behavior.

src/ Archive — dead production code

Old production clasp project bound to dormant script 1r9vWL…. Files match the v11.0f version from May 7. Not pushed since. Triggers on the old script killed weeks ago. Suggest renaming to src-legacy-v11.0f/ with a header note, OR move to archive/src-v11.0f-2026-05-07/.

scripts/ Review

• mobile_command_center.js — duplicate of the one in MIS-v1-script/. Delete this copy.
• runSACSUpgrade.js — same. Delete this copy.
• auto_triggers.js · trigger_power_system.js · MIS_ARCHITECT_COMPLETE_FIXED.js — paste-ready Apps Script tooling. Keep but flag for review later.
• v11_excerpts_for_v1.gs + v11_microservices/ — old V11 extraction. Archive
• build_owed_tabs.py · build_holdings_reconciled.py — one-time Python tools. Archive

audits/ Keep — all are good historical reference

• MIS_Master_v11_0f_Forensic_Teardown.md · MIS_V11_Forensic_Teardown.md · MIS_1F31z_Forensic_Teardown.md · MIS_Genesis_Context.docx · SACS_ZScore_Analysis.docx — keep
• v2_extracts/ — 11 CSVs from broken v2 mining. Archive as one bundle.

data/ Mostly Archive

Three large .xlsx exports (MIS_live_export, MIS_v7.1_gsheet, MIS_v8_Mindblown) + four point-in-time CSVs. Archive everything older than 7 days.

docs/ Keep — mixed but useful

Mostly stable reference docs. GITHUB_ISSUES_TRIAGE_2026-05-12.md is the most recent active doc.

archive/ + files/ + python/ Already archived / dormant

screenshots/ Keep

14 PNGs from Apr 28 / Apr 30 / May 1 / May 6. Reference artifacts.

4The keep / archive / delete plan

Top-level files to archive

Subdirectory cleanup

After moves: top-level MIS/ has ~10 files (README, .clasp files, today's 3 screenshots, this briefing reference, FOLDER_INVENTORY-link-to-this), plus 6 active subdirectories (MIS-v1-script · audits · docs · archive · screenshots · scripts-trimmed).

5Schwab + Finnhub keys → PropertiesService (the migration)

You asked: "if you want me to move the secret key for Schwab or anything, tell me how to do that, whatever I need to create. If it's the same way through script properties, I can hide my APIs and my keys."

Yes. Same pattern as the SMS webhook setup. Two-click migration shipped today.

What's in CONTROL tab today (plaintext)

The runbook (3 minutes total)

If anything breaks

Migration is reversible: re-paste the secret values back into CONTROL column B. Both code paths work — Properties first, CONTROL fallback.

Other APIs you mentioned ("see what else they can do for me")

Same Script Properties pattern works for any API. Worth considering for:

• IBKR — you mentioned having IBKR. If you add an IBKR connector later, drop the credentials in Properties from day one — never CONTROL.
• Twilio direct — if you ever bypass the command-inbox webhook and call Twilio direct from MIS, the SID + auth token go in Properties.
• Polygon.io / Alpha Vantage / IEX — if you swap out or add a market data source, same pattern.
• OpenAI / Claude API — if you ever wire LLM directly into MIS for ticker analysis, the API key belongs in Properties.

The rule: anything that looks like a secret → ScriptProperties. The CONTROL tab is for tuneable parameters (VIX bands, version stamp, last-run timestamps) — never credentials.

XWhat you do next

In order of fastest-to-meaningful:

1. Re-paste v3 holdings block if not yet done — outputs/2026-05-20_14-05_action_holdings-paste-may20-v3-formula-safe.md. Then MIS Tools → Refresh Holdings Clean Only. ~5 min
2. MIS Tools → 🧪 Verify Secrets Status — see baseline. ~30 sec
3. MIS Tools → 🔑 Migrate Schwab/Finnhub Keys to Script Properties — moves all 5 secrets. ~30 sec
4. MIS Tools → 🧪 Verify Secrets Status again — confirm both columns populated. ~30 sec
5. MIS Tools → 🔐 Set SMS Webhook — if not yet done. URL + secret from command-inbox/.claude-notify.json. ~1 min
6. MIS Tools → 📲 Send Command Center SMS Now — sanity test the SMS path. You'll get a text with the SOSMS string. ~10 sec
7. MIS Tools → Refresh Earnings Master — re-run with the rate-limit fix. Will take ~3.4 min this time but Finnhub will return data for ~all stock tickers (MSFT/INTC/LLY/etc. should populate). ~3.5 min
8. MIS Tools → Run Full Refresh Now — full pipeline, picks up new earnings data. ~2 min
9. MIS Tools → Send Morning Brief Now — verify everything's flowing. Should show 21 holdings, ORCL Margin -38% as EXIT, AMZN +24% as REDUCE/lock-gains. ~1 min
10. (Optional, when convenient) Clear CONTROL tab secret cells after confirming ScriptProperties side works.
11. (Optional) Reply with the folder-move plan from §4 — I'll execute the mv commands to archive in a single commit.

Total active time: ~15 min. SMS me when each major step completes (or just at the end with "all done").