📌 Active Projects from MEMORY.md
**Workspace start surface:** `dashboards/command-center.html` is the generated open-first index and, as of Jun 12, now routes into the fresh Friday WFH package instead of the stale Jun 6 weekend board. Current active package: `dashboards/friday-wfh-command-center-jun12.json`, `dashboards/friday-wfh-command-center-jun12.html`, `dashboards/command-center-index-jun12.json`, `dashboards/friday-wfh-launch-brief-jun12.md`, and `dashboards/friday-wfh-proof-log-jun12.md`. That package deliberately grounds the first-click path in current Jun 11/12 work on disk: NYC PR / healthcare Step-5 verification first, previous-PELS draft lane second, Circle submit-proof queue third, and DOAC attribution repair fourth. The Jun 6 weekend→Monday package and earlier Friday/weekend boards are now reference context only. Integrity guardrail stays `dashboards/check-command-center-links.js` → `dashboards/command-center-link-status.json`; the Jun 12 routing refresh verified clean link resolution on disk.
**PanArgent BD:** highest-priority workstream. Canonical repo: `panargent/bd-repo/`. Current May 29/31 restart/research additions are `panargent/bd-repo/notes/may29-fee-motion-owner-date-card.md`, `panargent/bd-repo/notes/may30-mighty-union-fee-motion-hook-card.md`, `panargent/bd-repo/notes/may31-monday-fee-motion-proof-ledger.md`, `panargent/bd-repo/research/deal-briefs/future-today-ib-deal-brief-may29.md`, and the Monday June 1 fee-motion stack package (`panargent/bd-repo/data/monday-fee-motion-jun1{,-pipeline}.json`, `panargent/bd-repo/scripts/build-monday-fee-motion-stack-jun1.js`, `panargent/bd-repo/monday-fee-motion-stack-jun1.html`, `panargent/bd-repo/action-packets/monday-fee-motion-packet-jun1.md`, `panargent/bd-repo/comms-kits/monday-fee-motion-comms-kit-jun1.html`, `panargent/bd-repo/launchpads/monday-fee-motion-launchpad-jun1.html`, `panargent/bd-repo/imports/2026-06-01-panargent-monday-fee-motion-stack-june-1-*`, and `panargent/bd-repo/qa/monday-fee-motion-stack-jun1-qa.md`); the June 2 target-lane truth layer now matters too: `panargent/bd-repo/scripts/build-target-lane-truth-dashboard.js`, `panargent/bd-repo/data/target-lane-truth-dashboard.json`, `panargent/bd-repo/dashboards/target-lane-truth-dashboard.html`, and `panargent/bd-repo/notes/jun2-target-lane-truth-dashboard-note.md` scan saved target-lane notes for claim-vs-proof risk so packaged lanes do not get mistaken for compliant deliverables. The June 2 seller-motion gate now matters too: `panargent/bd-repo/notes/jun2-binary-motion-gate-card.md` defines the exact Outward → Mighty Union → Matter order plus the timestamped external-touch proof standard required before any motion claim counts as real. The June 3 fee-motion proof layer now matters too: `panargent/bd-repo/scripts/build-fee-motion-proof-dashboard.js`, `panargent/bd-repo/data/fee-motion-proof-dashboard.json`, `panargent/bd-repo/dashboards/fee-motion-proof-dashboard.html`, and `panargent/bd-repo/notes/jun3-fee-motion-proof-dashboard-note.md` separate concrete saved lane lines, gate-cleared states, and qualifying external-motion proof so a polished restart stack does not masquerade as seller progress. The same-day Mighty Union live-step gate now also lives at `panargent/bd-repo/notes/jun3-mighty-union-first-touch-proof-card.md`; the approval-ready outreach packet is `panargent/bd-repo/notes/jun3-overnight-mighty-union-touch-pack.md`, and `panargent/bd-repo/research/deal-briefs/molekule-consulting-ib-deal-brief-jun3.md` is the new June 3 research-stage healthcare / biopharma-intelligence brief. These are still prep/research artifacts only, not outreach proof. The May 31 Miami correction layer still matters: `panargent/bd-repo/targets/miami-all-subsectors-may27/miami-all-subsectors-draft-post-exclude-106-summary-may31.md`, `panargent/bd-repo/targets/miami-all-subsectors-may27/miami-all-subsectors-draft-research-queue-99-summary-may31.md`, and `panargent/bd-repo/targets/miami-advertising-may31/research-summary.md` preserve Hunter's count correction while keeping the lane honestly labeled draft/not compliant. The May 27 support layer (`panargent/bd-repo/notes/may27-fee-motion-decision-sheet.md`, `panargent/bd-repo/targets/miami-all-subsectors-may27/miami-all-subsectors-target-list-summary-may27.md`, and `panargent/bd-repo/targets/restoration-service-lines-final-may27/restoration-service-lines-final-pels-may27.md`) still stands behind them. All of these are restart/research support only, not outreach proof or compliant final-deliverable proof. PanArgent pushes are healthy; the old sync trap was assuming one repo-scoped PAT could cover `rudy-memory` too.
New May 20 restoration lane: `panargent/bd-repo/targets/restoration-service-lines-may20/` contains five service-line workbook lenses plus Apollo import CSVs, cross-list QA, quarantine, and `restoration-service-lines-may20-summary.md`; treat the whole lane as `Draft / not compliant`, not a final deliverable.
Use repo files + Obsidian for current active sectors/prospects, not stale prose.
Start from `panargent/bd-repo/dashboards/execution-stack-command-center.html` when multiple dated execution stacks exist; it is now the fastest retrieval path to the latest usable stack and its real downstream assets, and as of May 31 it correctly promotes the Monday June 1 fee-motion stack instead of the stale May 8 Friday package.
Current restart surfaces are `panargent/bd-repo/monday-fee-motion-stack-jun1.html`, `panargent/bd-repo/action-packets/monday-fee-motion-packet-jun1.md`, `panargent/bd-repo/comms-kits/monday-fee-motion-comms-kit-jun1.html`, `panargent/bd-repo/launchpads/monday-fee-motion-launchpad-jun1.html`, `panargent/bd-repo/qa/monday-fee-motion-stack-jun1-qa.md`, `panargent/bd-repo/notes/may30-mighty-union-fee-motion-hook-card.md`, `panargent/bd-repo/notes/may29-fee-motion-owner-date-card.md`, and the earlier May 18/24 fee-motion truth/proof layer; all are prep/proof artifacts only, not evidence that any outreach actually happened. The Jun 1 stack resets the local PanArgent opener around one current sequence: Outward gate first, Mighty Union next ask second, Matter send/hold third.
Current May 18 meeting-prep/export package: `panargent/bd-repo/research/deal-briefs/fp-alpha-deal-brief.{md,html,docx}` plus `panargent/bd-repo/scripts/render-fp-alpha-docx.js`. May 19 also added the preliminary `moburst-deal-brief.md` and `frozen-fulfillment-deal-brief.md` files plus more France-fintech URL/domain workbench support inside `targets/fintech100-france-apr28/`; treat those as working research, not proof of mandate progress or target-list compliance.
May 21 added `panargent/bd-repo/research/deal-briefs/s360-ib-deal-brief-may21.md` plus the cold-chain research lane in `panargent/bd-repo/research/sectors/cold-chain-logistics/`; treat both as working research only, not external motion proof.
`panargent/bd-repo/data/phone-enrichment-kirks-prestolite-may15.{md,json}` preserves the exact Apollo free-plan blocker on the Kirks/Prestolite phone-enrichment attempt so that lane can be resumed from file truth.
Current May 7 mandate-prep artifacts include the Arioneo package in `panargent/bd-repo/research/deal-briefs/arioneo-ib-deal-brief-may7.{md,html,docx}` plus support files and the CreationDose brief at `panargent/bd-repo/research/deal-briefs/creationdose-ib-deal-brief-may7.md`.
Monday restart note: `panargent/bd-repo/notes/monday-may11-panargent-top-3-followups.md` is the quickest grounded reopen path for Outward, Mighty Union, and Matter.
Conference-fintech lane note: `panargent/bd-repo/targets/fintech100-france-apr28/` now includes a May 11 LinkedIn-assisted verification workbench (`pels-compliance-research/`, `linkedin_batches/`, May 11 workbook snapshots, and explicit `INVALID_TRIAGE_ONLY_DO_NOT_USE_*` quarantine files). Treat the whole lane as `Draft / not compliant`, not a final target-list deliverable.
🧱 Infrastructure
**Newsletter API:** `newsletter-api.maxwellgrey014.workers.dev`
**Mission Controls:**
life → `mission-control.maxwellgrey014.workers.dev`
panargent → `mission-control-panargent.maxwellgrey014.workers.dev`
update via `node update-mission-controls.js <life|panargent> '<json>'`
**Office API:** `office-api.maxwellgrey014.workers.dev`
**Funding Intel:** `funding-pipeline.maxwellgrey014.workers.dev` (Bearer `fi-hunter-2026`), D1 `funding-intel-db`
**GWS CLI:** historical path reference `C:\Users\hunta\gws-cli\`; verify live macOS location before relying on it.