Workflow
    private archiveencryptionredactionreview boardhuman reviewpublication gateChronicle VisualizerCodex Skills Library

    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.

    Part of projects

    Project

    Chronicle Visualizer

    Chronicle Visualizer is a privacy-first visual work-history project. It started with a real local Chronicle browser that indexed recent screen frames and persisted Chronicle summaries, then split into a public-facing Next.js scaffold and a private archive/redaction operating lane. The project is not just a screenshot gallery. Its product shape is a governed visual evidence system: raw frames stay private, written context is archived with images, public derivatives require redaction and review, and project/work-state labels remain inferred until corroborated by durable sources.

    Project

    Codex Skills Library

    Codex Skills Library is the durable source repository for Maggie Lerman's custom Codex skills, custom local plugin backups, generated skill catalogs, and the public docs site that explains the workflows. The repo turns local agent behavior into portable, inspectable artifacts: each skill folder carries trigger metadata, instructions, references, scripts, examples, assets, and validation expectations, while the catalog tooling keeps the public docs aligned with the suite allowlist.

    Workflow

    Chronicle Visualizer private archive and publication loop

    8 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
      subprocess
    3. Archive tooling bundles deltas, encrypts them with GPG AES256, uploads to the private S3 bucket, and writes minimal receipts
      subprocess
    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

    Related chats

    Related nodes