Phase 1 · Days 1-30
Day 21 · 10 days left in phase →

Blockers

Waiting on Kevin

NextKevin is back. Clear his decisions so the built backlog can deploy: entity, payment method, the move-off-Predis confirm (social), web-vs-native, and the website-hosting confirm. Decision brief in Ben's inbox 2026-06-15.

Waiting onKevin, entity decision, payment method, move-off-Predis confirm (social), app web-vs-native, website-hosting confirm. CARE is build-to-spec per his own brief, no sign-off pending (item 3).

Updated 2026-06-15

Open blockers (highest leverage first)

Ranked by how many downstream items each one frees.

  1. Entity decision — Kevin. Acuity Lab LLC or a new Kindred rOS entity. Sets EIN, bank, and legal structure. Blocks Stripe, and Stripe blocks the beta push, paid users, and conversion. One decision, the whole monetization chain.

  2. Payment method — Kevin. A card Kevin is comfortable putting behind the business (a business card, virtual card, whatever he prefers). Apple Developer license is purchased (Kevin, set up later) — off this list. Still needed for the Fly org transfer and Anthropic reimbursement; Google Play ($25) only applies if the app goes native (see item 4).

  3. CARE methodology — defined, no longer a Kevin sign-off. Kevin gave his definitive model in his own CARE Clarity brief (01 - Inboxes [JC, BK, KE]/Ben/CARE Clarity.md): capacity as one annualized number, attributes and relationship as yes-counts, engagement as a level, and the sorted list (not the score) sets the strategy. That supersedes the older JC-drafted 1/3/5 anchor note (2026-06-03 2022 CARE A-R-E 1-3-5 anchors for sign-off), which should not be put to Kevin for approval. CARE is now a build-to-spec item: the engine gets rebuilt to match his brief (APP-5). Not a blocker on Kevin, and not an open question. His doc fully specifies the model (two capacity fields, the capacity-first lexicographic sort, strategy by thirds, careScore supplementary). Do not put CARE questions back to him; build to the doc.

  4. App: web vs native — web instance confirmed 2026-06-15 (Ben); only the "also native" half may remain for Kevin. The web instance of Kindred rOS ships at app.kindredros.com (Fly app kindred-ros-app), DNS and APP_URL tracked as APP-22. The open question, if any, is whether to ALSO submit to the Apple and Google stores; web-only retires the app-store submission (APP-8) and both developer licenses and removes that part of the payment-method dependency. Push is achievable on web either way.

  5. Website hosting confirm — Kevin (Friday), low-stakes. The plan reversed to a Fly-hosted, Claude-built marketing site (off Squarespace). Build can proceed regardless; the one thing to confirm is that Kevin accepts giving up click-to-edit for the Claude-driven build. Sunk-cost rationale in Ben note 2026-06-02 1927 Website Hosting Reversal.

  6. Kyle's start date + tool access list — Ben / Kevin. Needed for a clean day-one onboarding. The onboarding packet is drafted and ready.

Recently cleared

  • Squarespace / email chain — resolved. JC is in, DNS records are set, the Resend domain is verified, and noreply@ sending is enabled. Fully unblocked.
  • Repo access — not an instance thing and never a blocker. Kevin and Ben both reach the repos (and the vault) through the shared jean-claude@kindredros.com GitHub account. There is no separate "Kevin-facing" Claude code instance; that framing was a hallucination and is removed wherever it appears.
  • "Kevin's GitHub handle" — not needed. Same shared jean-claude@ account, so there is no personal handle to grant. Not a blocker.
  • Connectors (Stripe, Zoho CRM, Gmail) — set up, per Ben (could not re-verify from this instance; the registry check returned empty). The Google Drive live-read is the separate, parked SRC-5 track, not a blocker.
  • Welcome-email reply-to address — resolved 2026-06-02. Set to jean-claude@kindredros.com (Ben's pick — real, human-monitored, catchall). APP-10 closed.
  • Email Fly secrets (RESEND_API_KEY, APP_URL) — resolved 2026-06-02. Confirmed/set on kindred-ros-api; APP_URL corrected to kindred-ros-app.fly.dev (APP-9, APP-11).

Updates

  • 2026-06-02: Corrected hallucinations Ben flagged. Removed the "connectors to enable" section (Stripe/Zoho/Gmail are set up per Ben) and dropped the Zoho-connector open blocker (Kyle's onboarding becomes item 6). Killed the "Kevin-facing JC code instance" fiction: Kevin and Ben both use the shared jean-claude@kindredros.com GitHub account, so neither a separate instance's repo access nor Kevin's personal GitHub handle is a blocker. NOTE for reconcile: same "Kevin-facing instance" phrasing still lives in app-product.md and the 30-60-90 execution map; and if Zoho's connector is truly live, sales-crm-tasks.md CRM-2 should be marked done.
  • 2026-06-03: Corrected the stale-render explanation above. The dashboard is NOT reliant on a redeploy — the active Obsidian Git sync plus runtime GitHub reads (OPS-13/14, deployed) mean vault edits show within minutes. The email-verification chain is fully resolved: the auth code arrived and works, DNS records are in, the domain is verified, noreply@ sends. The archived note in Ben/done was reworded so its body no longer reads as open.
  • 2026-06-02: Apple Developer license purchased (Kevin) — removed from the payment-method blocker; setup deferred. Note: the old "Privacy.com / dedicated card blocks all four" and "Squarespace auth code, one inbox four items" wording is NOT in any live status file (only in the May 1 / May 26 meeting notes as history). If that text is showing up, it is not coming from a live status file. The Ops Dashboard reads status from GitHub at runtime (OPS-13 live reads, active Obsidian Git sync), so a corrected push lands on the dashboard within the push interval plus the ISR TTL (a few minutes). There is no redeploy dependency.
  • 2026-06-02: Cleared the welcome-email reply-to and email Fly secrets (APP-9/10/11). Added two Friday Kevin decisions: app web-vs-native (item 4) and website-hosting confirm (item 5, the Squarespace→Fly reversal). Noted that web-only would retire the Apple/Google licenses and shrink the payment-method dependency. Renumbered; entity + payment stay the top long poles.
  • 2026-06-01: Seeded from the 30-60-90 execution map and the May 27 action items.
  • 2026-06-01: Squarespace login resolved; email-verification chain advancing.
  • 2026-06-01: Reworked. Fixed the numbering (it was missing item 1 and ran 2 through 6), removed the bogus GitHub-handle item, moved Squarespace/email and repo access to Recently cleared, corrected the fabricated "auth code never arrived" claim (the codes have arrived), and added the CARE A/R/E rubric as a genuine Kevin blocker. Attribution set to Ben for ops/dev, Kevin for entity, payment, and rubric.
  • 2026-06-03: Reworded the CARE A/R/E rubric blocker (item 3) to be informed — it now points to the existing canon (Core Product Spine axis definitions; the CARES Weight note, already in the math) and frames the ask as Kevin signing off JC-drafted 1/3/5 anchors, not a blank request to explain the scale.
  • 2026-06-04: CARE A/R/E rubric (item 3) moved from to-draft to awaiting sign-off. JC drafted the 1/3/5 anchors for all three axes and delivered them to Kevin's inbox (2026-06-03 note); the open piece is now purely Kevin's approval or redline, not JC drafting. Entity and payment method remain the top two long poles, unchanged.
  • 2026-06-05: Reconcile sweep (Friday). Live status files are clean of the retired "Kevin-facing instance" fiction; the phrasing now survives only in historical archives and Ben/done/ notes, which are left as a record by design. The 06-02 reconcile NOTE about app-product.md and the 30-60-90 execution map is resolved: both are confirmed clean. app-product.md and app-product-tasks.md APP-5 updated so they no longer say "JC to draft" the CARE anchors (they are drafted and in Kevin's inbox). CRM-2 (Zoho) left open: still pending the connector-live confirm, so not marked done. No blocker states changed; entity and payment remain the top two long poles.
  • 2026-06-09: Kevin is out all week (per Ben's June 9 working agenda), so every waiting-on-kevin long pole is frozen until he returns: the entity decision (1), the payment method (2), the CARE A/R/E anchors (3, drafted and sitting in his inbox), and the two Friday calls, app web-vs-native (4) and website-hosting confirm (5). No states change and the leverage ranking holds. This records that the clock is paused on Kevin's items this week. Ben's June 9 block is build and cleanup that does not need Kevin: app dedupe and DATABASE_URL labeling, the donor list view, store resilience, and website images.
  • 2026-06-15: Kevin is back. The clock is unfrozen on every waiting-on-kevin long pole. A decision brief is in Ben's inbox (2026-06-15 1118 Kevin is back) framing the live yeses: entity (item 1, still the top pole, gates Stripe and the whole monetization chain), payment method (item 2), the move-off-Predis confirm (social), app web-vs-native (item 4), and the website-hosting confirm (item 5). No decision is recorded yet, so all items stay waiting-on-kevin; they are now active asks rather than parked. CARE remains build-to-spec (item 3), not a sign-off. Leverage ranking holds.
  • 2026-06-15 (evening): kindredros.com is repointed to Fly and live (WEB-8 executed at Ben's direction — dedicated IPv4, both certs Issued, HTTPS verified serving the Fly build, email records untouched). This makes the hosting reversal real on the apex, so item 5 (website-hosting confirm) is now just Kevin's after-the-fact nod, not a precondition — the site is already serving. The demo-form backend (WEB-10) is built, pushed, and now deployed (kindred-ros-web v38, live + verified on kindredros.com). APP-18 store resilience is built + pushed but not yet deployed (apps not deployed as of 2026-06-15). No Kevin-blocking states change.