Moye Law OSTrusts & Estates
Trusts & Estates · public product specimen

An estate plan should feel like one clear path.

A family may have to make difficult decisions, gather records, answer detailed questions, review drafts, sign documents, and remember what still needs attention. The software should make that path easier to follow without pretending the software is the lawyer.

The client experience

Give the facts and records once. Keep the next step visible.

The client should not have to understand Docassemble, a document kernel, a database schema, or a workflow engine to complete an estate plan. Those are implementation details.

The visible experience should be simpler: know what counsel needs, answer guided questions, provide the records, see what remains, review the work with the lawyer, complete signing, and understand the follow-up.

The Recipe organizes the path. Counsel owns the legal decisions.

01 · Tell us once

Guided facts stay with the matter.

Draft answers, uploaded records, and later corrections belong to one matter path instead of becoming disconnected intake fragments.

02 · Know what remains

Missing work stays visible.

The system can show incomplete questions, missing records, draft status, and the next workflow step without converting those signals into legal conclusions.

03 · Review with counsel

Human approval is a real gate.

Draft facts and documents stay draft until counsel reviews them. Client release is a deliberate act after attorney approval, not a side effect of generation.

The Recipe pathway

Nine stages. One authority pattern.

The stages can be implemented with different tools. What travels with the Recipe is the order of responsibility: draft facts stay draft, attorney decisions stay attorney decisions, and release stays gated.

  1. 00

    Matter entry

    Attorney or intake operator

    Start from an authorized matter and a client-safe workspace so the work has a home before information begins to move.

  2. 01

    Conflict, capacity and scope preflight

    Counsel

    Counsel reviews conflicts, representation structure, possible capacity concerns, undue-influence concerns, and the scope of the engagement before substantive planning moves forward.

  3. 02

    Engagement and portal setup

    Firm and counsel

    Establish the engagement, portal access, initial records request, and the planning scope. Drafting does not become a shortcut around engagement authority.

  4. 03

    Guided planning interviews

    Client, with later attorney review

    Guided interviews collect draft facts and preferences, preserve partial progress, and return the work to the matter. The interview does not attest facts or choose legal conclusions.

  5. 04

    Records and supporting documents

    Client and operator

    Prior plans, deeds, beneficiary forms, account or business summaries, and other relevant records are gathered once and kept visible as part of the matter record.

  6. 05

    Fact normalization and attorney attestation

    System and operator assist; attorney controls authority

    Names, relationships, roles, addresses, and document references can be normalized and checked for gaps. Counsel decides which facts may actually be relied on.

  7. 06

    Matter Plan, clause planning and document assembly

    Counsel

    Counsel determines the appropriate instruments and planning approach. Software may prepare candidate language or assemble attorney-selected templates, but generated material remains internal.

  8. 07

    Attorney review and correction

    Counsel

    Every draft is reviewed against the source facts, client instructions, selected planning approach, and execution requirements before anything is released.

  9. 08

    Client release, signing and follow-up

    Counsel, operator and system

    Approved client-shareable material moves through the release gate, then into signing, executed-document preservation, and the appropriate follow-up path.

The authority boundary

Automation can carry work forward. It cannot inherit the lawyer's judgment.

Software may
  • Gather draft facts and preserve partial progress.
  • Organize records and surface missing information.
  • Normalize draft matter information for review.
  • Assemble attorney-selected templates and candidate language.
  • Assist with bounded research and drafting.
  • Track workflow, review, release, signing, and follow-up state.
Counsel decides
  • Whether conflicts and representation structure are cleared.
  • Capacity, testamentary intent, and legal suitability.
  • Which facts are attested and may be relied on.
  • Which instruments, clauses, and planning techniques are appropriate.
  • The final legal advice and substantive legal conclusions.
  • Whether work product is approved for client release.

Moye Law, P.C. remains the practicing-law authority. The operating system may gather, organize, retrieve, draft, and track. It may not clear conflicts, determine capacity, attest client facts, select final legal conclusions, give final legal advice, or release unreviewed work product.

What the specimen proves

Prove the workflow without borrowing credibility from a client.

TEST-2026-0001 lets us exercise the public product story against a stable, synthetic matter shape: a Trusts & Estates engagement, guided questions, supporting records, draft work, review states, and a client-safe path through the matter.

That is enough to explain the experience. The public showcase does not need a client name, a private document, a financial fact, or a claimed legal result to demonstrate how the system is intended to work.

Real matters may validate the same Recipe privately inside Moye Law OS under ordinary firm authority. What comes back to the product is workflow learning: where the Recipe is confusing, repetitive, or incomplete. Client facts stay with the client matter.

From proof to product

One workflow, three distinct authorities.

Moye Law OS

The reference deployment where the legal workflow is operated, observed, and refined.

Sushii Legal

The reusable product lane that formalizes the authority pattern without taking over a firm's matters or professional judgment.

Sushii Kitchen

The inspectable technical starting architecture underneath the Recipe. It describes infrastructure, not the practice of law.

Inspect the technical Recipe
Back to the whole system

Trusts & Estates is the first Recipe, not a separate operating system.

The same Moye Law OS holds the matter, records, review gates, and client relationship. The Recipe gives one practice workflow a reusable shape while preserving that single source of authority.

Return to Moye Law OS