5/12 18:46Z — Adam's executive-approval gate (verbatim)
Adam Fleckles, replying to Joseph's brain-dump send:
> "Before I share full login credentials for the systems I use, we need to connect with the Executive team to get approval here. With that said, let's keep this simple and move forward with what we have for now. It will likely take some time to provide you with full authorization for all these internal systems."
What this means in plain terms:
- Adam cannot hand over credentials this week — needs Executive approval first
- The Wednesday 5/13 stand-up still happens, but it is NOT "instance stood up with data plugged in" as originally targeted on the 5/11 call
- Phase 1A pivots to parallel build, no sign-in — the platform shell is staged for Adam, and the credentials flow in later (Phase 1B) once Executive approval lands
Phase 1A scope — locked 2026-05-13
| Workstream | Phase 1A status |
|---|---|
| Adam's PWA shell | ✅ Stays in lock-step with GC system (mirror-deploy hook in deploy_pwa.sh step 10/10) |
| Adam's tenant runtime | ✅ Provisioned + dormant (per project_adam_tenant_dormant.md) |
| Adam Google Workspace OAuth | ⏸ Was scheduled Thursday 5/14 15-min screenshare — now blocked on exec approval |
| Adam HubSpot owner_id | ⏸ Was PENDING_FROM_ADAM in tenant.json — still pending, no urgency this week |
| Adam Reamze / Notion / Data Studio / MARQ / Fathom credentials | ⏸ ALL blocked on exec approval |
| Wednesday 5/13 stand-up | ✅ Still happening — agenda becomes "what we've built in parallel + what's ready when access arrives" |
Joseph's operator directive (2026-05-13)
Verbatim instruction received this session:
> "Push forward on the GC system; keep Adam's PWA in lock-step with the GC model; don't ask Adam questions; build for when access does come."
Operational rules this drives:
1. No questions to Adam about credentials, owner_id, OAuth, or anything that blocks on Exec approval. We wait.
2. GC system continues as primary — all skill / cron / PWA / outreach work on Joseph's GC instance proceeds as normal.
3. Adam PWA shell mirrors GC PWA — every time deploy_pwa.sh runs, Adam's PWA gets the same shell update automatically (Deliverable 2 of this turn wires the mirror step).
4. No Adam data files are deployed (no leads.json, deals.json, outbound.json, approvals.json, source_health.json from Joseph leaking to adam-bd-brief.pages.dev). Mirror copies HTML/CSS/JS shell only.
5. Adam-specific files stay Adam-specific — Adam's own index.html (redirect-to-/preview shell), _worker.js (adam_bd_approvals KV binding), manifest stay intact.
Wednesday 5/13 stand-up — revised agenda
Since "instance stood up" is off the table, the call posture shifts to:
- Show what's built in parallel. Walk Adam through the Adam-PWA preview-* pages (now shell-mirroring Joseph's) so he sees the destination state visually.
- Confirm the Exec-approval path. Don't pressure — just acknowledge it and ask Adam to flag when he's clear to share credentials (Adam initiates, not Joseph).
- Talk the 12-tool inventory. Adam's 5/12 list (
reference_adam_tool_inventory_2026-05-13.md) — walk it together, mark Phase 1A vs Phase 2 priority. No promises about timeline. - Stay in the existing weekly cadence. Adam's track record on the 5/11 call was honest + collaborative — keep that posture.
What's already done that doesn't need Adam's creds
These keep running on Joseph's instance and continue to harden the system Adam's tenant will eventually receive:
- ✅ Mirror-deploy step in
deploy_pwa.sh(this turn, Deliverable 2) - ✅ 12-tool inventory captured (this turn, Deliverable 1b →
reference_adam_tool_inventory_2026-05-13.md) - ✅ New-tools integration spec (this turn, Deliverable 3 →
/Users/josephbowens/Desktop/adam-bd-bootstrap/NEW_TOOLS_INTEGRATION_PLAN.md) - ✅
tenant.jsonskeleton already captures every Adam-specific field withPENDING_FROM_ADAMmarkers — no editing needed until creds land - ✅
first_signin_watcher.pyalready running — will auto-bootstrap Adam's market keywords / competitors / signature stale-fragments when he eventually signs in
What blocks (and unblocks how)
| Blocked workstream | Unblocks when |
|---|---|
| Reamze SMS ingestion | Adam delivers Reamze API key or grants chrome_bridge profile session |
| Fathom transcript ingestion | Adam grants Gmail OAuth scope (from:noreply@fathom.video filter already wired into transcript-scan) OR Fathom API token |
| HubSpot owner_id filter | Adam pastes the /users/<owner_id> URL from his HS profile (he can do this without exec approval — it's his own URL, not a credential) |
| SkyRun Data Studio new-lead intake | Adam delivers Looker Studio export-share OR the underlying Google Sheet ID + read OAuth |
| Notion notes import | Adam shares the workspace via integration token |
| MARQ asset inventory | Adam shares the workspace or exports a manifest |
| QRCode Tracker (SPMS) | Adam shares vendor portal access OR an export schedule |
| Dimaco Mailing Tracker | Adam shares vendor portal access OR a CSV export |
| OwnerPoint (legacy) | Adam confirms credentials still valid + grants access |
| Vintory (legacy) | Adam confirms credentials still valid + grants access |
Cross-references
- Predecessor file:
project_adam_dev_call_2026-05-11.md— original 5/11 dev-call synthesis. Adam's Wednesday "instance stood up" target was set there; this file supersedes that timing. - Tool inventory:
reference_adam_tool_inventory_2026-05-13.md— 12-tool catalog with Phase 1A relevance + integration path + GC-architecture plug-point. - Behavioral rule:
feedback_adam_phase_1a_no_credentials_yet.md— operator-issued rule "don't push Adam for credentials; the exec-approval gate is what unblocks." - New-tools spec:
/Users/josephbowens/Desktop/adam-bd-bootstrap/NEW_TOOLS_INTEGRATION_PLAN.md— 6 NEW tools from Adam's inventory (Reamze, Fathom, MARQ, Data Studio, QRCode Tracker, Dimaco). - Mirror-deploy hook:
/Users/josephbowens/Library/Application Support/SkyRun/deploy_pwa.shstep 10/10 — keeps Adam PWA shell in lock-step every deploy. - Adam tenant state:
project_adam_tenant_dormant.md+~/Library/Application Support/AdamBD/tenant.json.
How to use this memory
When the next Adam contact happens (Wednesday 5/13 stand-up, or any inbound from Adam):
1. Re-read this file first — operator posture is "don't push, parallel-build, mirror-deploy"
2. Cross-check reference_adam_tool_inventory_2026-05-13.md for the per-tool plan
3. Do NOT cite specifics from this synthesis in outbound to anyone outside SkyRun without source-verifying against the Gmail thread (Adam's 5/12 18:46Z reply)
4. Update this file (not predecessor) with delta from the next Adam touchpoint