Summary
A long, substantive evening/overnight session producing the core INHERIT/TT strategic document stack. Key strategic decisions made:
-
InheritKit as Tier 2 commercial SDK (AGPL+dual commercial licence). Absorbs the dropped Henry product’s workflow orchestration logic. Rich builds this directly after Phase 0 schema hygiene.
-
Three-partner advisory model (succession + tax + faith, each with capability flags at individual level). Replaces the earlier two-tier tech + faith model.
-
Three-track partner badging — INHERIT Contributor (open-standard recognition), InheritKit Certified [Specialty] (commercial validation), TT Partner (contractual). Same professionals hold multiple badges per context.
-
InheritKit-first principle — when in doubt between Tier 0 (Apache schema) and Tier 2 (AGPL InheritKit), default to InheritKit. Apache is irrevocable for published versions; AGPL → Apache is trivial.
-
Henry and Command Centre both dropped as products. Henry’s logic absorbed into InheritKit + UX into MFI/InheritWills. Command Centre preserved as internal operational concept only.
-
MFI differentiator is “takes into account” — integrated estate plan across succession + tax + faith, not three separate plans. Faith modules in Phase 1.
-
E&W succession partner switched — MLP Law (via Jane Hunter Robinson) instead of IDR Law.
-
InheritKit name locked,
inheritkit.compurchased. Dedicatedgithub.com/inheritkit/org planned. -
Full scoping exercise before InheritKit spec confirmation — Rich overruled the partial-first suggestion. ~11 months of scoping across 50+ jurisdictions before build starts. MFI launch target: late 2028.
Commits delivered
24+ commits on main. Final commit ecb13a2 — InheritKit v1.10 + scoping framework v1.0.
Spec state at handoff
| Spec | Version | Path |
|---|---|---|
| Roadmap | v3.7 | docs/superpowers/specs/2026-04-16-inherit-tt-roadmap-ideas-design.md |
| InheritKit Design | v1.10 | docs/superpowers/specs/2026-04-16-inheritkit-design.md |
| InheritKit Scoping Framework | v1.0 | docs/superpowers/specs/2026-04-17-inheritkit-scoping-framework.md |
| E&W Schema Audit | v1.2 | docs/superpowers/specs/2026-04-16-ew-schema-audit.md |
| Governance Charter | v2.2 | standard/inherit-governance-charter.md |
| Partner Model | v2.3 | tt-products/orgs/partner-model.md |
| Partnership Targets | v1.1 | tt-products/orgs/partnership-targets.md |
| TT Brand Architecture | v2.4 | tt-brand-architecture.md |
| Viotti Commercial Proposal | v1.1 | standard/orgs/sourcemeta/viotti-commercial-proposal.md |
Self-correction moments worth remembering
-
Apache 2.0 lock-in overstatement — wrote “binding going forward” / “cannot be made unilaterally” in charter v2.1; Rich flagged; corrected in v2.2 with accurate “time-bounded contractual” framing. Triggered audit pass across other specs.
-
Lane 5 scope expansion omission — commit message claimed a Lane 5 update that didn’t actually happen; caught on self-review; fixed in follow-on commit.
-
Partner model partial commit — second commit on MLP Law change covered only 4 of 9 files because Edit calls failed on files not previously Read; caught and completed in follow-on.
Hand-off to fresh session
Rich wants to pilot the first scoping record under the scoping framework, applied to E&W succession. The pilot is the natural next step after landing the framework tonight. Fresh context recommended to avoid noise from this long session.
See docs/superpowers/scoping/pilot-handoff-prompt.md for the paste-in prompt.
Rich’s emphasis at session end
- Interoperability is his passion — badges 3 (FAIR), 4 (conformance suite), 6 (public register) are his priority from the quick-wins list
- He wants InheritKit prioritised above badges
- He wants full jurisdictional scoping before confirming InheritKit spec
- He explicitly reinforced the InheritKit-first bias: “we must ensure we continue to put things into inheritkit over the standard, when in doubt — it is far easier to move them into the inherit standard at a later date, than move out of inherit standard”