project_mlp_call_2026_05_11

Mon 11 May 2026 — Rich had a call with Jane + Stephen from MLP. Both very interested in www.MyFamilyInherits.com. Rich told them the next phase is him sending detailed mockups of www.MyFamilyInherits.com + IAS.

Why: MLP is the lead pilot-partner firm in the partner-pipeline (per project_mlp_pilot_v1_7_doc_pack_delivered_2026_05_05). The 11 May joint call was the natural next checkpoint after the v1.7 doc-pack delivery (Tue 5 May). The mockup deliverable was Rich’s commitment to advance the relationship — MLP is now waiting on TT. Their enthusiasm specifically about MFI (not just IAS) is a useful signal that the consumer-facing surface resonates with practitioner eyes too — supports the inherit-v2 product direction (memory #651 framing MFI as the competitive counter to myfamilyinherits.com).

How to apply:

• The mockup deliverable is now a hot Rich-deliverable — see richard-task #237 (richard-tasks-tt.md)
• Two surfaces to mock: (1) MFI consumer-facing comparison/discovery, (2) IAS partner-firm authoring surface
• Tue 19 May 2026 board meeting is in ~2 days (as of 17 May) — confirm whether MLP wants mockups in their hands BEFORE board (urgent / lighter fidelity) or AFTER (more polished)
• Any frontend-design / mockup / sketch session for MFI or IAS in the next weeks is in service of this commitment — don’t accidentally treat as unscoped exploration
• MLP partner-pipeline state has advanced from “doc-pack-delivered” to “next-phase-mockups-owed” — update docs-admin/partner-pipeline/partner-firm-pilot-pipeline.md when next touched
• When scoping the mockup work, brainstorm first; use brand-architecture.md v1.16 + per-brand local design-system CSS (global CLAUDE.md §14)
• Jane = ?, Stephen = ? at MLP — confirm full names + roles when next touched if not already on file in mlp-meeting-prep.md

Timeline locked (confirmed by Rich 2026-05-17): ~2 weeks from the call → deliverable by ~Sun 31 May 2026. NOT board-coupled (Tue 19 May TT board is independent of MLP mockup commitment).

Remaining open scoping questions (highest knock-on first):

1. Fidelity — wireframe / mid-fi HTML / high-fi pixel-perfect / hybrid?
2. Screen coverage — full flows or hero screens? Approx count?
3. Tooling — HTML mockups via frontend-design skill / Figma / static images / Canva?
4. Who builds — Rich + Claude alone, Dave McNally involved, anyone else?
5. Starting basis — build from existing MFI design-spec v2.3 + IAS arch-state, or fresh?

Update 2026-05-20: post-call recall details + substrate intake

Decision-maker identified: Stephen Attree is the main decision-maker at MLP. Jane Hunter is the day-to-day partner-contact + collaborator but Stephen is the lock-decision authority. When TT advances the partner-firm-DD pilot to formal agreement, Stephen is the addressee.

Main TT-contact at MLP: TBD pending Stephen’s pick. Stephen said they will select a solicitor on the MLP side to be TT’s main day-to-day contact. Name + role unknown as of 2026-05-20 — watch for pick announcement.

Acceptance criterion surfaced — Clio Draft import (load-bearing): MLP is “very interested in being able to import into Clio Draft” — Stephen used “very ‘safe’” framing meaning practitioner-familiarity / risk-reduction (not security-specific). This is a partner-firm-DD acceptance criterion that materially affects the InheritKit + IAS Phase-1.5+ scope. Registered as:

• empirical-substrate-registry finding #51 (Clio Draft import = MLP-pilot partner-firm-DD requirement)
• Phase-1.5+ ledger task-85 (Clio Draft import / export support — InheritKit Phase-1.5+ partner-firm-DD requirement)

Complex-wills substrate intake: Jane Hunter sent 3 redacted complex-will PDFs post-call. Filed at ~/testatetech/docs-admin/partner-pipeline/mlp/wills-substrate/ (PDFs gitignored per docs-admin/CLAUDE.md §2 confidentiality + binary-bloat avoidance; README.md committed). 3 files:

• dpt-will-redacted.pdf (~112 KB; DPT case)
• redacted-will.pdf (~1.5 MB; single complex-will case)
• complex-will-redacted.pdf (~2.5 MB; largest complex-will case)

These substrate-PDFs feed downstream into:

• Q-026 + Q-027 + Q-028 Wills module cascade-Q substrate validation
• Future complex-will Q-locks (cross-link Q-026.2 + Q-027.2 PARTIAL AMEND lock evidence)
• Phase-1.5+ task-85 (Clio Draft import test-fixture authoring)
• Acquirer-DD §3.x partner-firm-DD evidence pack

Status advance: partner-pipeline state goes “doc-pack-delivered” (5 May) → “next-phase-mockups-owed” (11 May call) → “happy-to-proceed + substrate-shared + Clio-Draft-requirement-locked” (2026-05-20 recall). Update docs-admin/partner-pipeline/partner-firm-pilot-pipeline.md when next touched.