Summary
Focused pilot session producing the first scoping record under the InheritKit Scoping Framework. Validated the methodology and absorbed refinements into Framework v1.2. Four commits on main.
Outputs
| Artefact | Version | Location |
|---|---|---|
| E&W × succession scoping record | v1.1 | docs/superpowers/scoping/2026-04-17-ew-succession.md |
| InheritKit Scoping Framework | v1.2 | docs/superpowers/specs/2026-04-17-inheritkit-scoping-framework.md |
| InheritKit Design Spec | v1.11 | docs/superpowers/specs/2026-04-16-inheritkit-design.md (pointer added in §2.16) |
| E&W Schema Audit | v1.3 | docs/superpowers/specs/2026-04-16-ew-schema-audit.md (pilot SCRs cross-referenced) |
PDFs in Downloads: ew-succession.pdf (v1.1), inheritkit-scoping-framework.pdf (v1.2), inheritkit-design.pdf (v1.11), ew-schema-audit.pdf (v1.3).
Commits
| SHA | Summary |
|---|---|
01b3336 | E&W succession scoping pilot v1.0 |
53a6285 | Scoping framework v1.2 absorbing FW1–FW5 |
| (tidy-up commit) | FW marks resolved in pilot; pointers added to InheritKit + Schema Audit; session memory |
Pilot methodology findings (validated)
- Framework template fit-for-purpose. 9 sections carried real content; no padding or forced structure.
- Aggressive InheritKit-first bias worked. Only 8 SCRs produced vs 15–20 without the bias.
- Test vectors did heavy architectural work. TV4 (contemplation-of-marriage) and TV6 (forfeiture) produced SCRs that would not have surfaced from §2–§4 alone.
- §3.5 “Existing schema coverage map” sub-section was a useful discovery during sanity-check — promoted to required sub-section in Framework v1.2.
- §6 cross-cutting is the longest section — capped at four canonical sub-sections in v1.2 (×dimension, ×faith, ×cross-border, ×interface-readiness).
- Surveyor cadence. 1–2 sessions per core (jurisdiction × dimension) record; ~0.5 session for lighter-touch “other jurisdictions” records. Page counts: 14–20 for core, 6–10 for lighter.
Framework refinements absorbed in v1.2 (FW1–FW5 all resolved)
- FW1 MVE heuristic clarified: “required for a legally valid decision”
- FW2 Test-vector format: prose at scoping depth, literal JSON at conformance-suite depth
- FW3 SCR ADR-style template codified (§8)
- FW4 §6.4 generalised from DADE-specific to “Interface readiness” (DADE, FHIR, OpenLegal, identity registries)
- FW5 Review-status-to-partner-badge mapping formalised as a table (§1)
Plus: §3.5 coverage map promoted; §6 sub-section cap; pilot-validated cadence in Phase B.
Schema Change Requests surfaced (SUCC-SCR-01–08)
| ID | Change | Size | Priority |
|---|---|---|---|
| SUCC-SCR-01 | Will-instance contemplation-of-marriage declaration | Small | Medium |
| SUCC-SCR-02 | PoA entity schema | Medium-Large | High — Phase 1 blocker |
| SUCC-SCR-03 | Executor renunciation status | Trivial | Low |
| SUCC-SCR-04 | Guardian appointment basis enum | Trivial | Low |
| SUCC-SCR-05 | Double-taxation treaty reference data | Medium | Medium (cross-border strategic) |
| SUCC-SCR-06 | Beneficiary entitlement state | Small | Medium |
| SUCC-SCR-07 | 28-day spouse survival rule | Trivial | Low |
| SUCC-SCR-08 | Revocation clause structure on will | Small | Medium |
Schema Audit v1.3 recommends expanding Phase 0 opportunistically to absorb SUCC-SCR-01, 03, 04, 07, 08 (small/trivial bundle); defer SUCC-SCR-02 and SUCC-SCR-05 to dedicated workstreams; treat SUCC-SCR-06 as a close call.
Self-correction moments (none in this session)
No major mid-stream corrections — the pilot executed cleanly with one sanity-check at the top and no further interruption. Contrast the prior session (project_session_2026_04_16_17.md) which had three self-correction moments. This reflects the value of fresh context for well-defined work.
What’s next
Rich’s stated next steps (as of session end):
- Review pilot + framework v1.2 PDFs away from screen
- Decide second scoping record target (Claude’s pick: E&W × tax, because it stress-tests the cross-dimension architecture decisions assumed in pilot)
- Other candidates: Scotland × succession (legal-tradition variant); Islamic × E&W succession (first faith overlay)
- Background workstreams not session-suitable: Phase 0 schema hygiene (Rich’s direct work, 2–3 days); backoffice form JSON Schema design; partner outreach (MLP Law)
Interaction pattern worth preserving
Rich used the pilot handoff prompt (docs/superpowers/scoping/pilot-handoff-prompt.md v2.0) as a fresh-context starter. That prompt explicitly told Claude to proceed without unnecessary questions — one initial sanity-check only. This pattern worked well: the sanity-check surfaced four template interpretations, Rich redirected briefly (aggressive InheritKit-first bias + more test vectors where data assists), then Claude drafted end-to-end without interruption. Worth repeating for future scoping pilots.