Workflow

    Ambient work-history context before and after Chronicle

    A branched operating model that compares legacy Chronicle's screenshot/OCR pipeline with Computer History's structured event and Accessibility pipeline, then rejoins them at reviewed memory, private retention, report-input, and public-derivative gates.

    before aftercapturesummarizationprivacy reviewhuman reviewreport inputChronicle Visualizer

    Workflow diagram

    Swipe horizontally to inspect the full diagram.

    Part of project

    Chronicle VisualizerParent project
    Ambient work-history context before and after ChronicleThis workflow
    Workflow diagramRendered with the workflow
    Workflow

    Ambient work-history context before and after Chronicle

    10 steps
    1. Operator enables an ambient context source and chooses observation boundaries
      decision
    2. Legacy Chronicle samples screen-derived frames into a rolling private buffer
      subprocess
    3. Legacy pipeline associates OCR, timestamps, nearby frames, app or window clues, and summary windows
      subprocess
    4. Computer History records structured interaction and Accessibility events into rolling JSONL segments
      subprocess
    5. Skysight memory jobs convert event segments into short-window and longer-window Markdown context
      subprocess
    6. Create a time-bounded private evidence artifact with explicit source, retention, and completeness metadata
      action
    7. Operator or automation reviews exact-day source coverage before any report or public claim
      decision
    8. If evidence is missing, preserve an unresolved gap instead of inferring zero activity
      state
    9. If evidence exists, review privacy, redaction, provenance, and aggregate-only publication boundaries
      decision
    10. Publish only reviewed note, workflow, data model, report input, or redacted visual derivative artifacts
      action

    Related notes

    Related chats

    Related nodes