# Per-Account Vault Estate Bridge

`@v2/per-account-vault-estate-bridge` closes the §137 per-account vault estate
planning wiring. It composes `@lakshmi/estate`, `@oshun/identity`, and
`@themis/transparency` into the `v2.per-account-vault-estate-transfer-manifest`
consumed by `V2Vault`, `V2Profile`, `V2OnlineServices`, and `V2CompanionApp`.

## Source Packages

- `@lakshmi/estate` owns the estate asset inventory, encrypted document vault,
  beneficiary tracker, digital legacy catalog, emergency access protocol, and
  executor/trustee runbook.
- `@oshun/identity` owns canonical account state, platform binding validation,
  account inheritance gates, and delegation-sensitive action gates.
- `@themis/transparency` owns the immutable delegation and asset-transfer audit
  trail through `ImmutableGovernanceAuditTrail`.

## Transfer Contract

The reciprocal Lakshmi schema is `v2.per-account-vault-asset-transfer`. Required
fields are `vaultPlanId`, `householdId`, `ownerOshunAccountId`, `assetId`,
`beneficiaryId`, `delegationId`, `evidenceDocumentId`, `transferInstructions`,
and `themisAuditRecordId`.

Each publishable transfer row must satisfy:

- Lakshmi asset transfer status is ready.
- A beneficiary designation is present and not in conflict with will provisions.
- The delegation is active, accepted, and backed by an evidence document in the
  encrypted estate document vault.
- Oshun identity validates the canonical account and passes verified-2FA /
  recovery-ready gates for inheritance and asset transfer.
- Themis records the delegation and every executable transfer in a valid hash
  chain with a forced checkpoint.

The gRPC surface is `libs/proto/v2/vault/per-account-vault-estate.proto`; event
topics are `v2.per-account-vault.delegation.recorded`,
`v2.per-account-vault.transfer.queued`, and
`v2.per-account-vault.transfer.revoked`.

## Runtime Boundary

The bridge is off rollback, server-authoritative, and account/companion-only. It
rejects live gameplay frame RPCs and never feeds deterministic match simulation,
competitive frame outcomes, AI, damage, inventory effects, or rollback inputs.
Vault transfers are estate administration events only.

CI ownership is enforced by
`V2/ue/Tools/check-v2-per-account-vault-estate-bridge.py`.