Last updated Jun 14, 2026

RA termination (SEV2)

Triggered by: the RA termination step in the dissolution cascade fails admissibility, OR a standalone RA-termination attempt fails the precondition matrix.

On-call: Primary (compliance bounded context).

Diagnose

Run the precondition check:

matter ops ra-termination-status --entity-id <id>

Returns the ordered missing-precondition list per apps/api/lib/ra-termination.ts decideRaTermination:

1. dissolution_filing_accepted — state SOS hasn't acknowledged the dissolution filing.
2. claims_window_closed — creditor claims window still open.
3. final_federal_return_filed — IRS Form 966 not yet filed.
4. final_state_return_filed — state final return outstanding.
5. tax_clearance_on_file — state-required clearance certificate missing.
6. distributions_paid — liquidation waterfall not complete.
7. bank_account_closed — bank account still open (ordering guard).

Recover

The single missing precondition is what blocks the termination. The "next step" is always the first in the ordered list.

For each missing precondition, follow its dedicated runbook OR resolve customer-side. Don't attempt to skip a precondition.

After resolving the missing item:

matter ops ra-terminate --entity-id <id>

If multiple missing, resolve them in the canonical order — earlier preconditions block later ones.

Validate

matter ops verify-ra-termination --entity-id <id>

Expected: RA marked terminated in registered_agent table, RA provider notified, audit chain contains ra.terminated event, entity post-dissolution flow continues.

Communicate

• Customer email same-day with the blocking precondition.
• If precondition is customer-side (final return), give a 7-day SLA for customer action before escalating.