The back office is the separate application at admin.securemylegacy.cloud where operators deliver Family Cleanup. A request from the client app opens a case; the knowledge base says what each provider allows after a death and supplies the steps; the engine runs those steps, holding anything automated for a person when the rules say so; and the audit log records every action in a hash chain.

​
The pieces

Cases

One per Family Cleanup request. Accounts, outcomes, steps, documents and a timeline the family can see part of.

Approvals

Automated emails, webhooks and API calls waiting for a person to read exactly what will go out.

Mail

Replies and documents families send back, filed on the case by reply address; and everything the service has sent, with its delivery state.

Knowledge base

A provider per online service, a published playbook per outcome, AI research that drafts but never publishes, and a review queue.

Automation

Rules that decide which automated steps run on their own, which wait for approval and which never run; and the operators themselves.

Audit log and settings

The append-only, hash-chained record, and the organisation, mail, LLM, automation and knowledge-base settings.

​
Invariants worth knowing before the first case

  • Nothing an LLM produced reaches a case until a person has reviewed it. Research drafts; operators apply, verify and publish.
  • A case copies its playbooks when it starts. Editing a playbook later never changes a live case.
  • The family sees account-level progress, the documents we asked for and the notes marked visible. Never operator notes, task internals or what was sent.
  • The audit log is append-only. Nothing edits or deletes a row, and Verify chain proves it.
  • No passwords, anywhere. The client app never stored them, and the back office has no field for them.

​
Start here

Sign in and roles

Invitation-only access and the four roles: viewer, reviewer, operator, admin.

How a case flows

Request → case → accounts and outcomes → start → steps → documents → approvals → done.

Work a case

Import the inventory, choose outcomes, complete steps, ask for documents.

Set up a fresh deployment

Organisation details, Resend, an LLM endpoint, dry run, and the starter knowledge base.