Sensitive Data Checkpoint¶
Seal a local-only SQLite Journal hot snapshot beside an already authorized, content-aware Sources export and verify both by digest. The checkpoint is never eligible for the unencrypted remote backup.
Skill name: data_sensitive_checkpoint
Category: backups
Mutates state (retry policy: manual)
Parameters¶
| Name | Type | Required | Description |
|---|---|---|---|
destination |
str |
No | Checkpoint directory under the configured backup root. Defaults to the Sources export's parent directory. |
idempotency_key |
str |
No | Stable replay key. Defaults to the Sources export ID. |
issued_copy_count |
int |
Yes | Issued-copy count returned by the authorized Sources export. |
source_export_id |
str |
Yes | Export identity returned by the authorized Sources export. |
source_export_path |
str |
Yes | Exact path returned by source_maintenance_operator action=export. It must already be directly inside the checkpoint directory. |
source_export_sha256 |
str |
Yes | SHA-256 digest returned by the authorized Sources export. |
source_item_count |
int |
Yes | Item count returned by the authorized Sources export. |
Details¶
This skill is the second step of a sensitive backup. First create a
content-carrying Sources archive through source_maintenance_operator; that
operator records every issued offline copy behind its own high-consent gate.
Then pass its exact receipt here. This operation does not copy or rename the
Sources archive. It adds a SQLite-consistent Journal member and a digest
manifest in the same directory.
The resulting directory is local-only (remoteEligible: false). It is not
added to the ordinary tarball or uploaded to the unencrypted GitHub Releases
backup path.