Spike 21 — Q-016 Will Update Architecture pre-validation CLOSED 2026-05-03 (research-only)

  • Spike ID: Q-and-A-S21 (D3)
  • Group: Group 6 — Deferred-Q pre-validation (Spikes 19-22; 20-22 loose-ordering)
  • Closed: 2026-05-03T12:35 BST
  • Outcome: VALIDATED (research-only; no kill condition by design per plan §7 Task 21)
  • Session: SPIKE-RUNNER session 4 — Batch K (Option B smart-batching: Spike 22 + Spike 21 INLINE same session; second of two)
  • Effort: ~⅗d wall-clock (T-file pre-flight ~25min + Tier 2 retrieval ~10min + T-file authoring ~70min + closure cascade ~25min)

What this spike delivered

Single artefact: T-file at ~/off-github/library/projects/inherit/T-spike-q016-will-update-architecture-pre-validation-2026-05-03.md v1.0 (639 lines / 58 KB / 8 body sections / 11 honesty caveats). Pre-validates Q-016 Will Update Architecture ahead of Phase 6 InheritWills lock-decision.

5-option taxonomy μ.α-μ.ε

  • μ.α full-replacement — new Will is freshly executed (Wills-Act-1837-compliant); supersedes via PROV-O prov:wasInvalidatedBy
  • μ.β codicil-pattern — statutorily-recognised Wills Act 1837 amendment instrument; PROV-O prov:wasDerivedFrom + fold operation at probate
  • μ.γ event-stream — Will-state captured as immutable event-stream of PROV-O prov:Activity events; current Will = fold over event-stream
  • μ.δ versioned-graph — each Will-version is immutable graph node anchored via SHA + did:web partner-firm DID; per-version SD-JWT VC issued; revocation via Bitstring Status List v1.0
  • μ.ε hybrid — μ.β codicil + μ.γ event-stream + μ.δ versioned-graph operating alongside legally-valid execution

5-criterion 1-5 rubric scoring

OptionLegalDefOpsVelAcqNarrPhase1FeasStdsTrackTOTAL
μ.α full-replacement5233316/25
μ.β codicil-pattern5344319/25
μ.γ event-stream2554521/25
μ.δ versioned-graph3453520/25
μ.ε hybrid (★ recommended)5453522/25

Dominant constraint (per T56)

Legal-form-of-execution: Wills Act 1837 s.9 + Scottish Requirements of Writing 1995 + Swiss ZGB Arts 498-504 ALL require physical-witness-presence + handwritten-subscription as of 2026-05-03 BST. COVID-era video-witnessing relaxation EXPIRED 31 Jan 2024. Law Commission Modernising Wills Law 2025 enabling-power statutory instrument NOT YET COMMENCED.

Implication: μ.γ event-stream + μ.δ versioned-graph + μ.ε hybrid options ALL operate ALONGSIDE legally-valid execution rather than replacing it. Year-2+ enabling-power-commencement is the canonical reconsideration trigger.

Recommendation

Phase-1 baseline: μ.ε hybrid (~£12-18K incremental build / ~24-36 engineer-days; Sphereon SSI-SDK TypeScript + Spruce ssi WASM + Bitstring Status List + nexus-prov SHACL + ProvToolbox 2.2.x + Catala WillUpdateReview scope + IK Probate UI + IAS solicitor authoring panel)

Phase-1 degraded fallback: μ.β codicil-pattern alone (~£4-6K) if μ.γ + μ.δ slip to Phase-1.5

NOT recommended:

  • μ.α full-replacement (16/25) — operational-velocity 2/5; partner-firm friction
  • μ.γ pure event-stream alone (legal-defensibility 2/5 — must run alongside μ.α/μ.β)
  • μ.δ versioned-graph alone (legal-defensibility 3/5 — cryptographic anchoring on top of NOT-legally-valid version-content is category error)
  • Spike 22 trigger-event detection (T-spike-q017 same Batch K session): PROV-O annotation pattern shared; 14-trigger taxonomy informs Will-update-event-class decision matrix at T-file §2.5 (triggers 1+2 → μ.α/μ.β; triggers 3-4+6 → μ.β; triggers 7-10+13 → μ.γ; triggers 11+14 → μ.γ; trigger 12 → μ.ε)
  • Spike 5 ζ-Q15 NEW Wills follow-through: upstream cascade-Q file pending authorship per plan §3 Task 5; substrate evidence + 1-5-rubric scoring transfers regardless of label-shift at Spike 5 framing

Witness-event-as-PROV-bundle pattern

Per T56 §1 finding 5 — store the witness-event as a DistributionContext PROV bundle with two W3C VCs (one per witness) + same wall-clock instant + geolocation + biometric. Jurisdiction-agnostic; survives statutory change; faith-tradition witness-pattern-mapping per v6.6 SEED 5 pillars (Islamic two-male / Hindu pandit-presence / Jewish two-kosher-witness / Sikh / Catholic).

VC infrastructure

Per T2 + T63: SD-JWT VC primary (EUDI Wallet ARF v1.4 alignment; IETF tooling); DI + BBS+ where unlinkability matters; Bitstring Status List v1.0 W3C Rec for revocation; did:web Phase-1 (partner-firm DNS-anchored); did:keri Phase-2+ (cross-jurisdiction Court-order delegation).

Year-2+ reconsideration trigger

Law Commission Modernising Wills Law 2025 enabling-power statutory instrument commencement → electronic Will execution becomes legally valid in E&W → μ.γ event-stream gains legal-defensibility 5/5 → architecture options gain NEW layer (electronic-Will-update via QES + W3C VC + PROV-O annotation as primary). Trigger date estimate: 2027-2030 per Law Commission roadmap chatter.

Phase-1.5 jurisdictional-crate addition

Texas + Florida e-Wills + RON per T56 §A-99 + A-100 reframe — Phase-1.5 addition to symmetric-jurisdiction discipline. e-Wills via QES + RON notary witnessing → μ.γ event-stream + μ.δ versioned-graph become legal-defensibility 5/5 in Texas + Florida ahead of E&W enabling-power.

Cost-rows architectural estimates

  • Phase-1 build (μ.ε hybrid): ~£12-18K (~24-36 engineer-days)
  • Year-2+ enabling-power-commencement extension: ~£8-15K incremental
  • 5y cumulative additional run-cost: ~£5-8K/yr

Cascade artefacts

  • T-file T-spike-q016-will-update-architecture-pre-validation-2026-05-03.md v1.0 → off-github commit (Batch K batch 1; pending push)
  • arch-state v3.34 → v3.35 with §14 placeholder row S21 REPLACED + Changelog row → docs-strategy commit (Batch K batch 2; pending)
  • Plan v1.16 → v1.17 §0 Spike 21 checkbox ticked + lastmod + CHANGELOG row → docs-strategy commit (same as above; pending)
  • Memory file (this file) saved
  • MEMORY.md index entry pending
  • Active-work-log entry pending CLOSED conversion
  • NO docs-personal commit (no richard-task disposition)

Honesty caveats salient

  1. Research-only — NO Will-update prototype built
  2. 5-option taxonomy formulated fresh by this spike (not retrieved from prior evidence)
  3. 1-5 rubric scoring is reasoned argument from substrate evidence (not empirical measurement)
  4. Wills Act 1837 enabling-power-not-yet-commenced holds throughout Phase-1
  5. Texas + Florida e-Wills + RON not separately enumerated in §3 scoring (Phase-1.5 jurisdictional-crate addition)
  6. Multi-jurisdiction-customer Will-update fan-out OUT-OF-SCOPE for Phase-1
  7. PROV-O annotation illustrative (not validated against owlready2/SHACL/shex)
  8. VC issuance benchmark not done
  9. Capacity-assessment referenced but not empirically tested
  10. 5-option taxonomy MAY collapse to fewer at Q-016 lock-decision time
  11. Companion to Spike 5 may shift labels

NO modifications

  • A-1..A-142; A-22 SSSOM-canonical pin; A-41/A-42/A-43 Credentials module (already accommodates Will-update VCs)
  • MQ-000 ζ.2 scope; brand-architecture v1.16; master plan v1.10; per-repo BUILD-PLAN v1.4-1.6; refined-prompt v3.7
  • NO new richard-tasks; NO new SKOS classifier scheme; NO new A-21 CI gate (still 22 per A-130); cross-module primitive count UNCHANGED at 27; module count UNCHANGED at 9; risk register UNCHANGED

Methodological observations

  • 7th spike of 22-spike suite to close (after Spikes 1 + 12 + 18 + 22 + 2 + 8)
  • THIRD research-only spike (after Spike 18 + Spike 22)
  • SECOND of two inline-paired research-only spikes via Batch K Option B smart-batching SAME session (Spike 22 closed 11:50 + Spike 21 closes 12:35)
  • T-file pre-flight per feedback_check_t_files_first_for_any_inherit_v2_work saved ~30-40% of authoring effort (T6 + T56 + T2 + T63 + companion T-spike-q017 covered ~50% of Will Update Architecture options landscape)