Chronicle Visualizer private archive and publication loop
The operating loop that preserves Chronicle frames and written context privately, verifies encrypted storage, reviews candidate derivatives, and only publishes redacted public timeline assets after human approval.
Workflow steps
- 1
Chronicle writes rolling screen frames, OCR sidecars, latest frames, and persisted memory summaries into local private paths
Action
- 2
LaunchAgent runs the incremental archive every 10 minutes, preserving new screen files and written context before local rollover
Process
- 3
Archive tooling bundles deltas, encrypts them with GPG AES256, uploads to the private S3 bucket, and writes minimal receipts
Process
- 4
Remote verify and restore dry-run confirm referenced keys, written-context contents, and exclusion of private git internals
Action
- 5
Operator selects candidate frames or timeline spans for possible public derivatives, keeping raw paths and OCR private
Decision
- 6
Sensitive-surface checks, pixel-burned redaction, review-board packet generation, and human review determine publication state
Decision
- 7
Only approved public derivatives and public-safe manifests can appear in the public timeline or Hyphenomenon image evidence
Action
- 8
Unapproved or high-risk material remains raw-private or quarantined; local pruning happens only after upload receipts and retention windows
Decision