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 diagram
Swipe horizontally to inspect the full diagram.
Part of projects
Chronicle VisualizerParent projectCodex Skills LibraryParent project
Chronicle Visualizer private archive and publication loopThis workflow
Workflow diagramRendered with the workflowWorkflow
Chronicle Visualizer private archive and publication loop
- Chronicle writes rolling screen frames, OCR sidecars, latest frames, and persisted memory summaries into local private pathsaction
- LaunchAgent runs the incremental archive every 10 minutes, preserving new screen files and written context before local rolloversubprocess
- Archive tooling bundles deltas, encrypts them with GPG AES256, uploads to the private S3 bucket, and writes minimal receiptssubprocess
- Remote verify and restore dry-run confirm referenced keys, written-context contents, and exclusion of private git internalsaction
- Operator selects candidate frames or timeline spans for possible public derivatives, keeping raw paths and OCR privatedecision
- Sensitive-surface checks, pixel-burned redaction, review-board packet generation, and human review determine publication statedecision
- Only approved public derivatives and public-safe manifests can appear in the public timeline or Hyphenomenon image evidenceaction
- Unapproved or high-risk material remains raw-private or quarantined; local pruning happens only after upload receipts and retention windowsdecision