About

A workbook today. A permissioned executor agent tomorrow.

Updated

Executor Workbook begins as a source-linked New Hampshire guide for first-week organization. The longer-term goal is more ambitious: software that helps an executor carry the administrative work, asks before taking action, and knows when to stop.

Today

What exists now

The public workbook helps a first-time New Hampshire executor know what to gather, what to read, what to ask banks, and what to tell family before guessing.

It is intentionally narrow: official source links, calm language, preparation templates, and visible legal boundaries. It is not trying to be probate automation.

Future thesis

The app should help carry the work

A traditional app waits for you to operate it. An executor agent should notice what needs attention, prepare the next move, and ask before it acts.

That changes the center of the product. The useful interface is not only a dashboard of tasks. It is a permissioned control surface for what the agent has prepared, what it needs you to approve, and where it has paused.

Possible actions

Five ways the future agent could help

Each action starts with a simple contrast: old software asks the executor to manage the work; Executor Workbook should help carry it.

Action 01

Build the next-step plan

Traditional app

A traditional app gives you a checklist and asks you to decide what applies.

Executor Workbook agent

The Executor Workbook agent would ask a few context questions, propose the next three to five actions, explain what can wait, and flag what needs professional input.

Before claiming this: This needs source-backed New Hampshire estate sequencing, common first-week executor tasks, and careful language that does not decide whether probate is required.

Action 02

Prepare institution calls

Traditional app

A traditional app stores contacts, notes, or generic task fields.

Executor Workbook agent

The agent would draft a call script, list documents to have nearby, and flag what a bank, insurer, court, or advisor may not discuss before appointment.

Before claiming this: This needs research into common institution requests, authority limits before appointment, institution variability, and private-data boundaries.

Action 03

Coordinate family updates

Traditional app

A traditional app gives you templates or a status board you have to keep current.

Executor Workbook agent

The agent would draft updates from current progress, avoid promises about timing or distributions, and ask before sending or sharing anything.

Before claiming this: This needs safe family-update language, privacy boundaries, conflict scenarios, and rules for asking relatives for documents without overpromising.

Action 04

Track open loops

Traditional app

A traditional app lets you create tasks, due dates, and reminders one by one.

Executor Workbook agent

The agent would notice unresolved loops such as missing death certificates, promised callbacks, unanswered attorney questions, or documents still waiting on a relative.

Before claiming this: This needs source-backed deadline research, user-entered reminder handling, audit trail design, and a clear disclaimer against overclaiming responsibility for missed dates.

Action 05

Pause risky actions

Traditional app

A traditional app lets you keep moving unless you recognize the risk yourself.

Executor Workbook agent

The agent would stop when facts are disputed, ownership is unclear, creditor pressure appears, distributions are requested, or legal judgment is needed.

Before claiming this: This needs unauthorized-practice boundary review, attorney escalation triggers, bank and court edge cases, and safe phrasing for refusals.

Trust model

Permission is part of the product

The agent prepares the work, explains its reasoning, asks for approval, takes bounded action, and leaves an audit trail.

  • Prepare first

    The agent should draft, organize, summarize, and assemble work before asking the executor to approve anything external.

  • Ask before side effects

    Sending, sharing, scheduling, requesting, filing, or contacting anyone should require clear permission.

  • Show the work

    The executor should be able to see what source, document, task, or user-provided fact shaped each recommendation.

  • Leave a trail

    A future workspace should record what the agent prepared, what the executor approved, and what was paused.

  • Escalate cleanly

    When an issue needs a court, bank, attorney, or other qualified professional, the agent should turn uncertainty into a better question.

Boundary

Not AI probate

The future is not an AI lawyer, a court-filing service, an account closure service, or a replacement for the executor's judgment.

The work worth automating is operational: organization, drafts, reminders, packets, questions, and communication. When facts are disputed, ownership is unclear, creditors are pressing, distributions are requested, or a legal judgment is needed, the agent should stop and help the executor ask a better question.

Review the source posture Read the workbook