# Anchor Class Independence Checklist

**Draft checklist for high-risk continuity actions.**

The protocol survives not by trusting good people, but by making capture require incompatible conspiracies.

## Step 1 - identify the action class

### Pause

Preserves status and prevents immediate harm.

Examples: disputed payee change, suspected key compromise, contested successor claim.

Pause may be triggered by a weaker signal.

### Change

Updates a live continuity route.

Examples: contact update, key rotation, mirror update, steward update, package hash update.

Change requires fresh proof of will or adequate authority.

### Transfer

Moves rights, ownership, control, archives, succession, payee destination or project authority.

Transfer requires the strongest review.

## Step 2 - list anchor classes

Potential classes:

- subject / declaration / key / mnemonic;
- material anchor;
- family or personal witnesses;
- notary, lawyer or fiduciary;
- state root-fact node;
- platform, publisher, counterparty or foundation;
- independent archive, library, university or repository;
- professional association or community;
- technical public ledger, timestamp or content-addressed archive;
- insurance, mutual defense or legal-defense layer;
- witness-commons node outside the local power chain.

## Step 3 - test independence

Ask:

- Are these actors legally separate?
- Are they economically dependent on the same institution?
- Are they under the same state pressure?
- Are they controlled by the same family conflict?
- Are they all using the same compromised account or email?
- Are they all downstream of the same platform?
- Could one coercive order capture them all?

## Step 4 - apply the quorum rule

For high-risk transfer, prefer confirmations from at least three genuinely different classes.

Three signatures from the same power chain are weaker than three confirmations from incompatible classes.

## Core rule

No class of power may confirm itself.