# Protocol Execution Invariants

The following properties **must always hold** and cannot be bypassed.

#### Asset Custody and Movement

* Assets may be moved **from external Asset Holder addresses into the personal CryptoLegacy contract** only via **protocol-defined execution paths** and only if:
  * all required on-chain state conditions for that execution path are satisfied, and
  * the relevant assets were **pre-approved** for protocol-defined transfer.
* During the **Normal Period**, assets are **not** moved into the personal contract via inactivity-based or guardian-based execution paths. Asset movement during the Normal Period is possible **only** via **recovery-specific execution paths**, subject to recovery thresholds and recovery-specific on-chain conditions.
* Assets may be moved **from the personal CryptoLegacy contract to external addresses** only via **protocol-defined execution paths** and in accordance with the rules of that path. In particular, recovery execution paths may withdraw contract-held assets to **arbitrary new recipient addresses** according to recovery execution rules.
* **Recovery execution is a distinct protocol-defined execution path** and **cannot reverse, modify, or invalidate** finalized beneficiary claims.
* Any assets sent directly to the personal contract **outside protocol-defined execution paths** are **out of scope** and do not affect protocol guarantees.

***

#### Deterministic Execution and Finality

* All execution is deterministic and based exclusively on on-chain state and timestamps.
* Execution finality is asset-level, not contract-level.
* Finalized execution cannot be rolled back.

***

#### Authority Boundaries

* Beneficiaries, Guardians, and Recovery addresses are execution roles, not custodians.
* No role may bypass execution conditions, shorten protocol-defined challenge periods, or override protocol-defined state transitions.

***

#### Ownership and Control

* Once Distribution begins, owner-only operational actions are disabled by protocol checks.
* Ownership transfer does not re-enable disabled authority or grant discretionary control.

***

#### Plugins and Extensibility

* Plugins may extend execution actions **only within existing execution paths**.
* Plugins cannot modify:
  * protocol timing parameters,
  * role classes,
  * execution finality guarantees.

***

#### Governance and Operators

* Governance, build managers, registries, and operators:
  * cannot move assets,
  * cannot trigger execution paths,
  * cannot alter finalized outcomes.

***

#### Time Assumptions

* All time-based logic relies on blockchain timestamps.
* Network delays may delay execution but cannot change rules or authority.

***

### Protocol vs Interface Semantics

The protocol operates purely on-chain.

Encryption, backups, asset lists, wallet management, and decrypt/import flows are **off-chain coordination tools** and do not affect protocol execution or authority.

Visibility of encrypted metadata does not grant authority.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cryptolegacy.app/protocol-mechanics/protocol-execution-invariants.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.