Aegis HTML Ledger

Maintain a current execution record so another agent can resume the work if the active session fails or becomes unavailable.

Location and ownership

Keep the primary HTML ledger in the project. Local-only operation is complete and supported.
Make an iCloud or other cloud copy only when the operator's authorization covers this project's records, the destination account and folder, and the content being copied. Reuse that authorization while its scope still applies; choosing this skill alone does not authorize a cloud transfer.
If that authorization is absent, keep the ledger local and record cloud sync as not enabled. A missing optional cloud copy must not block ordinary project work or a local handoff.
Keep credentials, tokens, private conversations, personal records, and restricted project content out of cloud copies. Use authorized summaries and artifact references; do not copy referenced files or full transcripts by implication. Project disclosure restrictions take precedence over sync convenience.
Reuse the active project or work-slice ledger. Do not create another ledger for every turn, command, or helper session.
Update the project ledger first, then refresh an authorized cloud copy from that checkpoint. Identify the project ledger as the primary record.
When cloud sync is enabled, keep the destination, authorized content scope, checkpoint, and freshness explicit. If copying fails or lags, preserve the project record and report the gap. A local copy does not prove propagation to other devices.
Keep the ledger dependency-light. Treat it as execution and handoff state, not project canon unless explicitly promoted.