project_mlp_pilot_v1_7_doc_pack_delivered_2026_05_05

MLP pilot v1.7 doc-pack delivery

Date: Tuesday 5 May 2026. Trigger: Rich invoked /review-plan on outreach/mlp-board-combined-proposal.md v1.6 + asked for tightening pass + DPIA/DPA placeholders + reverse-direction-conversion strategic question + 4 follow-on actions on partner-format-of-choice principle.

Calendar context

• Tuesday 28 April 2026 — Rich’s first-pitch meeting with Jane Hunter (delivered Jane invitation v1.8 + tech supp v1.1)
• Tuesday 5 May 2026 — this session (review-plan tightening pass + DPIA/DPA + meeting-prep + integration-scope stub + IK state + richard-task #231)
• Monday 11 May 2026 — joint call with Jane Hunter + Stephen Attree + Rich Davies (P-γ stage of partner-pipeline)
• Friday 16 May 2026 — Rich-owned deliverable deadline: completed integration-scope estimate + pilot-agreement draft + SRA Lawtech compliance summary + DPIA/DPA shareability confirmation, ALL to MLP before the 19 May board
• Tuesday 19 May 2026 — MLP board meeting considers the pilot proposition

Files delivered

File	Path	Version	Status
Combined proposal	~/testatetech/docs-strategy/outreach/mlp-board-combined-proposal.md	v1.7	committed by parallel session as 39f7f9b outreach: MLP board pilot proposition refresh — v1.6 → v1.7
Jane invitation	~/testatetech/docs-strategy/outreach/mlp-jane-hunter-pilot-invitation.md	v1.9	same commit
Tech supplement	~/testatetech/docs-strategy/outreach/mlp-jane-hunter-technical-supplement.md	v1.2	same commit
IK arch-state	~/testatetech/docs-strategy/docs/superpowers/specs/inheritkit-architecture-state.md	v1.1 → v1.7 (skipping reverted v1.2-1.6)	this session
Partner-pipeline	~/testatetech/docs-admin/partner-pipeline/partner-firm-pilot-pipeline.md	v1.0 → v1.1	this session
Meeting-prep	~/testatetech/docs-admin/partner-pipeline/per-firm/mlp-law/meeting-prep-2026-05-11.md	v1.0 (new)	this session
Integration-scope-estimate stub	~/testatetech/docs-admin/partner-pipeline/per-firm/mlp-law/integration-scope-estimate.md	v0.1 stub (new)	this session
DPIA placeholder	~/testatetech/docs-admin/partner-pipeline/per-firm/mlp-law/dpia-placeholder.md	v0.1 (new)	this session
DPA placeholder	~/testatetech/docs-admin/partner-pipeline/per-firm/mlp-law/dpa-placeholder.md	v0.1 (new)	this session
Richard-tasks	~/davieshq/docs-personal/richard-tasks.md	task #231 added	this session

PDFs in /mnt/c/Users/Richard/Downloads/

7 PDFs covering the full pack — combined v1.7 (17pp) / Jane v1.9 (17pp) / tech supp v1.2 (8pp) / meeting-prep (9pp landscape) / integration-scope-estimate stub (8pp landscape) / DPIA (16pp landscape) / DPA (17pp landscape).

Key disciplines applied

1. Review-driven tightening pass against locked state files. Verified 30+ specific claims in v1.6 against inherit-v2-architecture-state.md v3.56 / ias-architecture-state.md v1.2 / inherit-v2-standards-engagement-state.md v1.0 / tt-products/orgs/partner-model.md v2.5. Found §8 IDP claim (“Microsoft Entra ID, Google Workspace, Okta, and standard SAML providers”) and §8 encryption claim (“AES-256 with per-firm key management”) drift from IAS state v1.2 — softened proposal text rather than pinning new architectural commitments. Found §1 standards-engagement framing (“ISO/W3C/OASIS pathways all under active consideration”) slightly under-stated where OASIS lock actually sits — reframed as OASIS-Phase-1.5-locked / W3C-active / ISO-roadmap.

2. Sibling consistency. Two siblings (Jane invitation v1.8, tech supp v1.1) had the v1.4-pre overpromise pattern + wills-only scope from before v1.5/v1.6 reframing landed in the combined. Brought both up to v1.9 / v1.2 with: founding-partner terminology / routing→visibility framing / LPA inclusion / commission disclosure (Jane only; tech supp doesn’t carry commercial terms) / 11-May-19-May next-steps timeline (replacing “the meeting today” + “scoping call within 2 weeks” — both now historical).

3. Jurisdictional framing held NARROW per Rich directive 2026-05-05. Despite ζ-Q15 λ.η lock 2026-05-05 expanding Phase-1 to UK&W + Scotland + Switzerland + Texas/Florida, NONE of the multi-jurisdictional disclosure leaked to MLP. All seven docs hold “England & Wales is the launch jurisdiction” with no further pre-disclosure. Verified via grep for Switzerland / Texas / Florida / Scotland / UK&W = 0 hits across all docs.

4. Partner-format-of-choice principle (NEW framing). Rich asked: should we provide tools to convert “our” wills into MLP’s preferred software formats so MLP solicitors can confirm in their familiar environment? Verdict: strong yes — strengthens partner proposition, fully consistent with open-standard / data-portability framing. Architecturally sound: audit-trail integrity preserved across the round-trip (cryptographic hash anchored to executed document, not to where editing happened, per combined §5). Bounded by R-032 (case-management integration scope-creep at first partner-pilot, MATERIAL) — Phase-1 commits to Clio Draft only; additional formats (Lexis Protégé / Actionstep / Leap / Iris / Insight Legal) are Phase-1.5+ partner-demand-driven. Lossy-conversion handling: explicit annotation default + embedded INHERIT JSON-LD blob where target supports custom fields. NOT in v1.7 body — Rich raises it verbatim at the 11 May call (verbatim wording captured in meeting-prep-2026-05-11.md §2). Then: integration-scope estimate captures it as Phase-1 commitment 2 (post-11-May fill-in).

5. DPIA + DPA placeholders authored from scratch. UK GDPR Art 35 (DPIA) + Art 28 (DPA) standard processor-controller forms. Structurally complete; [TO BE COMPLETED IN PRE-PILOT DILIGENCE] items clearly marked for MLP-side input or post-contract legal review. Anchored to A-113 DO-per-firm tenancy + Apache 2.0 foundation + ACDC audit trail. DPIA scores 12 risks DPIA-R1..R12 with residual scores all Low post-mitigation; Article 36 prior-consultation-with-ICO assessed not required.

Cross-doc reference graph (closed)

Every doc in the pack references its peers via companion_files: blocks pinned with pin_kind: snapshot:

• combined v1.7 → references arch-state + IAS state + standards-engagement + partner-model + partner-pipeline
• Jane v1.9 → references combined v1.7
• tech supp v1.2 → references combined v1.7 + IAS state + standards-engagement
• DPIA v0.1 → references combined + IAS state + arch-state + partner-pipeline + DPA
• DPA v0.1 → references combined + IAS state + DPIA + partner-pipeline
• meeting-prep v1.0 → references combined + DPIA + DPA + partner-pipeline + 28 April meeting-prep + contact-log
• integration-scope-estimate v0.1 → references combined + meeting-prep + partner-pipeline + DPIA + DPA
• partner-pipeline v1.1 → references combined v1.7 in changelog
• IK arch-state v1.7 → references combined v1.7 §3 in §11 tension-queue entry

Outstanding actions (for Rich)

Per richard-task #231 (Friday 16 May 2026 deadline):

1. Conduct the Mon 11 May joint call using meeting-prep-2026-05-11.md v1.0 §2 verbatim wording for the partner-format-of-choice principle. Items wanted from MLP: sample anonymised Clio Draft export + MLP’s primary IDP confirmed + MLP DPO contact + board-temperature read.
2. Fill in the integration-scope estimate post-call (integration-scope-estimate.md v0.1 → v1.0). Two Phase-1 commitments to capture: Clio Draft bidirectional + partner-format-of-choice principle.
3. Draft pilot agreement (short — confidentiality, data protection, term, liability cap). Run through external legal counsel.
4. Draft SRA Lawtech compliance summary (1-2 pages). Pre-pilot documentation pack inclusion.
5. Confirm DPIA/DPA placeholders shareable with Stephen + Jane (already in PDF form in Downloads).

Architectural disciplines preserved (no architectural commitments smuggled in)

• IK arch-state §10 amendment registry stayed at 22 Tier-2 entries unchanged — [FULL PHASE-2-3 REVERSION 2026-05-01T20:45] integrity preserved. The v1.7 bump only added a forward-looking tension-queue entry to §11, NOT a new A-N amendment.
• Version-bump from IK state v1.1 to v1.7 (skipping reverted v1.2-1.6) documented in changelog with rationale.
• Pre-commit pin-drift hook (docs-strategy/scripts/check-frontmatter-pins.py) — all new companion_files: use pin_kind: snapshot (not floor); will not trip the blocking hook.

Why this matters

This is the largest single-session partner-outreach delivery to date for the v2 build. The pack stands behind Phase-1 closure gate B (≥1 Tier-1 IAS partner-firm onboarded with full will + LPA workflow). MLP becoming the founding-partner firm during Phase-1 is the single most important commercial proof-point for Phase-1 closure per the partner-firm-pilot-pipeline workstream.

If MLP signs the pilot agreement post-19-May, the partner-pipeline P-ε stage fires GREEN and Phase-1 closure-gate B has a concrete path. If MLP defers, the v1.7 §13 fallback path (extended diligence / June board / bilateral with Jane) is in place + the pack remains usable with the next partner-firm conversation (the meeting-prep v1.0 §2 verbatim wording generalises to any partner firm reaching for their familiar drafting environment at final confirmation).