Rich’s directive Sunday 19 April 2026 late evening. Accidental stealth from v6.6’s basic-Hugo-site appearance has commercially benefited TT (competitors underestimate us); preserve this deliberately.
Operating principle: “Every public release is a launch-coupled event, not a schedule-driven one.”
Release plan:
- Build months 1-4 (private) — v6.6 unchanged publicly; partners + academics have NDA access to next-version modules
- InheritWills.com launch → Core + Wills family become public on openinherit.org
- InheritKit.com commercial launch → Probate + Trusts become public
- MyFamilyInherits.com launch → Assets + Catalogue + Delegation become public
- Post-MFI (~month 15+) → all modules public; v6.6 under maintenance heading
Key disciplines future sessions must preserve:
- Don’t improve openinherit.org preemptively. The basic-Hugo-site appearance IS the camouflage. Investment signals seriousness and forfeits the stealth advantage.
- Minor v6.6 iteration only if someone asks. No unprompted cosmetic uplift. If a partner or collaborator raises a specific gap, fix it narrowly. Otherwise leave v6.6 alone.
- Partner access is NDA-bound during the private-build phase. Sign the access agreement first; developer access follows.
- Each public release is a launch event — not a date on a calendar. If a product launch slips, the public-reveal slips with it. Never reveal ahead of the product that justifies it.
- The “dramatically different from v6.6” narrative is revealed gradually across ~9-12 months of launch-coupled events, not a single dramatic reveal. Competitor surprise is distributed rather than concentrated.
- Apache 2.0 commitment preserved — v6.6 stays public throughout. The next version becomes public progressively rather than by decree.
How to apply when future sessions interact with openinherit:
- If asked to improve openinherit.org content / design / aesthetics → push back: “is someone specifically asking for this, or is it preemptive?”
- If asked to release / publish next-OpenInherit modules → check: “is the matching consumer product launching? if not, the reveal is premature”
- If Rich mentions partner needing access → remind him the access is NDA-bound + the public version is still v6.6
- If competitor research surfaces that someone has noticed the gap between v6.6 and TT’s commercial ambition → flag to Rich so he can decide whether stealth is still viable
Canonical docs for this decision:
~/testatetech/docs-strategy/brand-architecture.mdv1.4 §6.5~/testatetech/docs-strategy/docs/superpowers/specs/2026-04-19-inherit-v2-roadmap.mdv1.5 §2.0c