InheritKit is a proposed rich embedded SDK that sits above Apache 2.0 INHERIT schemas and above Sourcemeta’s Blaze validator. It encodes jurisdictional business logic — rule engines, cross-jurisdiction inference, succession/tax/faith resolution, will-template rendering, Henry AI integration hooks, generation tooling, partner-success signalling, tax computation (IHT/BPR/APR/TNRB).
Licence: AGPL 3.0 + commercial dual licence. Enterprises embedding it (Clio, Wealth.com, Addepar, LegalZoom-scale) buy the commercial licence. Free under AGPL for individuals, academics, non-profits.
Why: This is the only category where the iText/MySQL dual-licence model actually works for INHERIT — embedded executable code, not schema definitions. It gives TT a revenue extraction layer without requiring any change to the open standard itself.
Why the Sourcemeta agreement doesn’t block it: §2 of the agreement scopes Sourcemeta as “Validation Technology Partner”. Blaze = validation. InheritKit = business logic layer beyond validation. Different product category, not covered by the agreement’s joint-use clause.
How to apply: When future sessions revisit licence strategy, monetisation, or product architecture, InheritKit is the answer to “how do we extract revenue from embedded use without breaking the open standard or the Sourcemeta partnership.” Don’t revisit AGPL on schemas (blocked contractually and strategically). Don’t revisit proprietary-everywhere (kills adoption). Tier 2 SDK is the clean path.
Status as of 2026-04-16 evening: Concept emerged in brainstorm between Rich and Claude. Rich validated as “brilliant idea”. Design spec drafted at docs/superpowers/specs/2026-04-16-inheritkit-design.md (v1.0 draft, 13-page PDF in Downloads). Awaiting Rich’s review. Spec not yet committed to git. Rich still wants thinking time before updating the parent roadmap spec (2026-04-16-inherit-tt-roadmap-ideas-design.md).