Project directory · v1

Three workstreams, one product.

A working library: the demo of what Legacy might become, the concept studies that inform its data model, and the user research that pressure-tests both. All three run in parallel and feed each other.

Workstreams: 3 Demo pages: 13 Concept studies: 2 User studies: 3
01 · DEMO
Product mockup
What Legacy looks like when built — the principal's office, the typed graph, the professional roles, the rules engine. Conceptual but coherent.
13 PAGES
02 · CONCEPT STUDIES
Data-structure inquiries
External patterns — LinkedIn, Wikipedia, typed graphs — examined for what they teach about how Legacy should model people, relationships, and assets.
2 PAGES · MORE COMING
03 · USER STUDIES
Synthetic-persona research
Twelve souls on disk. Ten cold-discovery interviews. A six-phase protocol. The pain matrix that came out of Phase 01.
3 ARTEFACTS · PHASE 02+ TBD
01 · DEMO

Product mockup

Thirteen conceptual pages of what Legacy could look like end-state. Some are explanatory, some illustrative, some structural. None are shipping software.

01.01 · HERO
Product overview
"The principal's office, in software." Vision pitch with hero, capability grid, and the how-it-works flow. The page someone reads first.
overview.html→
01.02
Briefing
Project context and framing — who this is for, what it is not, why now.
briefing.html→
01.03
Recommendation
How decisions surface in the product — the recommendation layer between the principal and the professionals.
recommendation.html→
01.04
Structure
Information architecture — how the product organises what the principal sees and what gets buried.
structure.html→
01.05
Data model
Internal data model — the typed graph of people, accounts, assets, decisions, and the relationships among them.
data-structure.html→
01.06
Architecture
System architecture — how the hub connects principal, professionals, and external systems without becoming the bottleneck.
architecture.html→
01.07
Scopes
Scopes of access — what each professional sees, what stays principal-only, and where the seams are.
scopes.html→
01.08
Professionals
The roles that surround the principal — lawyer, CPA, wealth manager, trustee — and how the product addresses each.
professionals.html→
01.09
Rules
Constraints engine — how the product enforces consistency across documents, beneficiaries, and time.
rules.html→
01.10
Scenarios
What-if simulations — how the principal's plan plays out under death, divorce, sale, and other forks.
simulation.html→
01.11
Validation
How the product checks its own work — and which classes of error it cannot catch without a human.
validation.html→
01.12
Upgrade path
Tiers and progression — how a customer moves from a will to a trust to an integrated multi-jurisdictional plan.
upgrades.html→
01.13
Critique
Honest critique of the approach — what could fail, what's overclaimed, where the hand-waving lives.
critique.html→
02 · CONCEPT STUDIES

Data-structure inquiries

Studies of external systems — LinkedIn, Wikipedia, typed graphs — examined for the patterns Legacy should borrow, adapt, or refuse. Each study is a teaching artefact, not a product claim.

02.01
LinkedIn as a graph
What LinkedIn's professional graph teaches about modelling people and relationships — and what it gets wrong that estate planning cannot.
linkedin.html→
02.02
Typed graphs
A design exploration of typed-graph data structures — edges that mean things, not just connections, and why that matters for estate primitives.
typed-graph.html→
02.03 · COMING
Wikipedia as a fact graph
A planned study — how Wikipedia's structured-data layer (Wikidata) handles entities, claims, and provenance, and what to borrow.
tbd
03 · USER STUDIES

Synthetic-persona research

A virtual-interviewee instrument: twelve souls on disk, each with their own profile and journal, talked to in a six-phase research protocol. Sharpens hypotheses, surfaces objections, and rehearses interviews before they happen with real humans.

03.01 · CAST
The twelve souls
Ten virtual interviewees + two virtual cofounders. Each with a profile (their soul) and a journal (their memory). Diverse on age, wealth, geography, family complexity, and worldview.
interviewees.html→
03.02 · METHOD
The six-phase protocol
How I'd interview the cast to gauge demand: cold discovery → pitch pressure-test → wireframe walkthrough → focus groups → objection harvest → cofounder council.
interview-protocol.html→
03.03 · PHASE 01 REPORT
Cold discovery pain matrix
Phase 01 complete. Ten cold-discovery interviews, ten unhad conversations, ten unshown artefacts. The pattern is the pattern is the pattern. Click any row to read its transcript and founder notes.
sessions/…/pain-matrix.html→
03.04 · COMING
Phase 02 — pitch pressure-test
A planned report — same ten households, standardised 30-second pitch, watching where each persona leans in and where each checks out. Segment-fault-line mapping.
tbd
03.05 · COMING
Phase 03 — wireframe walkthrough
A planned report — mock the onboarding flow, walk each persona through it, capture mental-model collisions.
tbd
03.06 · COMING
Phase 04 — focus groups
A planned report — three focus groups by segment fault-line. Cold round + hot round. Where they argue is where the segmentation lives.
tbd