MemberIntel, page by page.

The V1 advisor-only spec for MemberPress operators: two-tier brain architecture, Free/Pro pricing model, and a data-flywheel moat built from product mechanics rather than pre-existing proprietary data.

V1.5 extends MemberIntel with AI write-actions via the MemberPress MCP and a 5-minute 'Set up FOR ME' greenfield wizard backed by a 14-day Pro trial.

V2 expands MemberIntel to BuddyBoss customers via a sister-company partnership — a low-engineering-risk cross-platform proof point since BB Memberships runs on MemberPress under the hood.

Covers GCP vs Heroku vs DigitalOcean for hosting, then deep-dives per-tenant isolation strategy using shared-schema RLS as the V1 foundation.

Details the three failure modes of the cross-pollination pipeline — re-identification, tenant leakage, and opt-out bypass — and the architectural mitigations for each, including k-anonymity floors, three-role isolation, and GCP project structure.

Defines the three separate promotion pipelines — code, Terraform, and database migrations — with GitHub Actions, Workload Identity Federation, manual prod gates, and the eval suite as a release-blocking check.

Describes the three-destination telemetry model — Cloud Logging for debugging, BigQuery for business analytics, locked-down BigQuery for audit — plus domain-specific metrics, on-call structure, and pre-written runbooks for the five highest-stakes failure modes.

Defines the four-layer cost-control stack — rate limiting, entitlement service, per-call token budgets, and continuous spend monitoring — with Redis-backed quota counters, server-side model routing enforcement, and a global daily circuit breaker.

Covers the three signup paths converging into a unified user model, per-license MP OAuth signing keys, customer-OAuth-only Stripe (no Connect), Argon2id passwords with server-side sessions, account merge prevention, and the V1.5 trial state machine.

Defines the three separate sync pipelines — MP (queue-based with per-customer concurrency controls), Stripe (webhooks for Pro, polling for Free), and site analysis (weekly-cached Claude calls) — with shared convergence layer and a platform-agnostic canonical schema designed for V2 expansion.

Defines five distinct secret categories with separate lifecycles, a layered KMS key hierarchy per environment, Secret Manager naming conventions with path-prefix IAM, 5-minute TTL caching, and the hard rule that no human ever reads a production secret.

Treats the eval suite as versioned release-gate infrastructure rather than ad-hoc tests, with 150 structured scenarios across seven categories, a judge-model scoring layer, CI integration, a differentiation subset that proves advantage over baseline LLMs, and a production thumbs-down feedback loop.

Honestly assesses which SPEC risks the architecture handles well, which remain genuinely fragile (differentiation, content lead bottleneck), and names four risks the SPEC never flags — Anthropic dependency, ops time underbudget, per-customer brain as liability, and compliance as a moving target.

Phase-by-phase sequencing of all architectural commitments against the actual team ramp, surfacing five friction points where the phased plan and architectural reality diverge — content lead timing, Phase 2 scope calibration, differentiation eval ship date, privacy counsel engagement depth, and infra engineer hiring window.

A 6-phase team ramp plan growing from 2 people in May to 7+ at launch, with hard milestone gates controlling when each new team member joins MemberIntel full-time.

Rev 2 of the team ramp plan, updated after May architecture sessions: adds a dedicated brain-content lead recommendation, recalibrates Phase 2 milestone language for honesty, and moves the differentiation eval to a Phase 3 gate item.

Seth Shoultes's Lead Architect role definition: end-to-end technical ownership of the brain, data pipeline, AI/ML architecture, engineering team, and vendor decisions for MemberIntel.

Blair Williams's CEO role definition for MemberIntel: product owner, final decision-maker on strategy, pricing, and architecture material choices, executive sponsor across the company.

Product Lead role definition: execution ownership of MemberIntel's PRDs, compliance, marketing site, beta program, Free-to-Pro conversion, and cross-functional coordination from scoping through GA.

Santiago Perez Asis's Project Manager role definition: cadence, dependency tracking, risk register, and L10 scorecard ownership for MemberIntel inside the broader Caseproof portfolio.

A companion one-pager surfacing seven decisions where the May architectural commitments conflict with the v1 phased plan — each with a recommendation and named decider — designed to drive a 30–45 minute sign-off session before Rev 2 is approved.

A binding contract defining who owns which decisions across engineering, product, compliance, and GTM — keeping Seth and the Product Lead unblocked as peers without escalating every disagreement to Blair.

A 90-minute fixed-agenda template for quarterly architectural health reviews — covering differentiation gap, cost-per-cohort, reliability, cross-pollination health, compliance posture, and a standing 'one thing that worried me' round — starting Q4 2026 post-GA.

A 4-hour late-May working agenda for outside privacy counsel to review MemberIntel's per-tenant isolation, cross-pollination boundary, secrets management, and data lifecycle decisions — grounding counsel's June ToS and Privacy Policy drafting in the actual architecture.

Seth's operational working checklist for May 2026 — organized week-by-week with ADR drafts, GCP scaffolding, schema design, RLS prototype, hiring pipeline, and cross-functional coordination tasks required to unlock Phase 2 on June 1.