BAMF
BAMF.AIDev Dashboard
24 lanesUpdated Sep 4 · 6:00 PM PT

Operating dashboard

One lane. One owner. One verifiable finish.

Assign the machine and harness, steer with notes, surface Houston blockers, copy the exact audited prompt, and close each lane against evidence.

1Complete
10Active
23Remaining

Three-computer plan

Astra directs. Focused tasks finish.

One copyable director prompt per computer contains every assigned lane, exact model, task name, dependencies, and full kickoff prompt.

MacBook Pro9 lanes
Mac Mini7 lanes
MacBook Air7 lanes

S2 · Both repos

Self-serve integrations

Active/partial. Slack and Notion live-proven; Google/GHL software paths exist but positive tenant grants remain unproven

Loading saved state…

Assignment

Where this lane runs

Plan recommendation: GPT-5.6 Terra · medium

Steering

Houston notes and blockers

Canonical kickoff

Full audited lane prompt

Create and own a focused goal: finish Lane 3 self-serve connectors in the canonical BAMF.ai V2 Plugins experience. Work across /Users/houstongolden/Desktop/CODE_2025/bamfaiapp and /Users/houstongolden/Desktop/CODE_2025/bamfsite/bamfsite from current origin/main, preserving unrelated WIP.

Read project-context/HANDOFF-v2-product-closure-2026-09-04.md, project-context/v2-consolidation-lanes.md, project-context/evidence/2026-09-04-lane-3-provider-closure-matrix.md, and project-context/evidence/2026-09-04-v2-oauth-runtime-handoff.md. Do not rebuild existing connector primitives.

Priorities: Slack, Notion, Gmail, Google Calendar, Drive, Sheets, Analytics, Search Console, and GoHighLevel. Finish the bounded customer Verify/Refresh UI and prove connection, callback workspace binding, reconnect, revoke, refresh, disconnected/error states, cancellation, encrypted tenant grant persistence, and cross-tenant denial. Slack and Notion already have positive Houston receipts. Google count-only probes exist but production had zero tenant grants. GoHighLevel requires dedicated Marketplace tenant OAuth and must never borrow the internal agency credential. Skip HubSpot unless a developer account already exists.

Never mark a provider healthy from credential presence alone. Use .env.local access without printing secrets, but do not simulate provider consent. If visible OAuth consent blocks one provider, record the precise blocker and continue other providers.

Acceptance: the provider closure matrix records implemented, configured, connected, live-runtime verified, tenant-isolated, error/reconnect verified, and exact blocker; customer-facing UI is truthful; contract and API docs are current; focused tests/build and authenticated visible-browser QA pass. Commit bisected units and push main.

Definition of done

Closure and evidence

Prioritized connectors have truthful connect/reconnect/refresh/error/isolation evidence