artifacts/standard-named

Rendered from markdown source. Open raw source on GitHub.

Candidate Loop Dissolution Checklist

Status: research artifact Content canon status: unset

This checklist does not replace bankruptcy, labor, environmental, records, privacy, insolvency, contract, or sector-specific law.

1. Decision and authority

• State why the loop is ending.
• Identify who has authority to order dissolution.
• Record dissent and affected standing.
• Distinguish completion, failure, revocation, merger, fork, and forced closure.

2. Freeze recruitment

Stop creating new:

• memberships;
• promises;
• data intake;
• automated decisions;
• financial exposure;
• dependencies;
• long-duration obligations.

3. Inventory residual state

Inventory:

• assets;
• liabilities;
• credentials;
• delegations;
• data;
• models;
• embeddings;
• automations;
• contracts;
• appeals;
• claims;
• environmental effects;
• public representations;
• third-party reliance.

4. Map affected centers

Include:

• participants;
• workers;
• users;
• beneficiaries;
• customers;
• suppliers;
• creditors;
• communities;
• data subjects;
• future claimants;
• successor institutions.

5. Transfer, discharge, restrict, or repair

For every residual item, select and witness:

TRANSFER
COMPLETE
COMPENSATE
DELETE
RESTRICT
ARCHIVE
NOTIFY
REPAIR
RELEASE
CONTESTED

6. Revoke authority

Revoke:

• credentials;
• API and model endpoints;
• delegated roles;
• financial authority;
• data access;
• signing authority;
• scheduled jobs;
• public claims of representation.

7. Preserve bounded witness

Preserve only what is needed for:

• audit;
• claims;
• repair;
• history;
• successor understanding;
• legal obligation.

Apply privacy, retention, and access boundaries.

8. Verify afterlife

Test for continued operation through:

• cached processes;
• copied data;
• derived models;
• informal workflows;
• inherited labels;
• automated decisions;
• successor claims;
• public assumptions.

9. Establish aftercare

Create a narrow successor loop only where needed for:

• archives;
• appeals;
• claims;
• remediation;
• monitoring;
• pension or benefit obligations;
• data-subject requests.

10. Closure review

Closure is complete only when:

• active authority has stopped;
• residual state is assigned;
• affected centers have notice;
• repair routes exist;
• aftercare is bounded;
• unresolved remainder is recorded.