Workflow

    Twice-weekly Chronicle publisher

    How the active Monday-and-Thursday automation finds missing completed Chronicle days, proves source coverage, generates privacy-safe reports, publishes eligible artifacts, and retains unresolved dates for review.

    chronicletwice weeklyautomationpublic publicationprivacyno gapHyphenomenon

    Workflow diagram

    Swipe horizontally to inspect the full diagram.

    Workflow chain

    Part of project

    HyphenomenonParent project
    Twice-weekly Chronicle publisherThis workflow
    Workflow diagramRendered with the workflow
    Workflow

    Twice-weekly Chronicle publisher

    6 steps
    1. Start Monday and Thursday at 9:00 AM America/New_York and enumerate every completed day not yet represented publicly
      state
    2. Confirm exact-day coverage and recover only eligible aggregate source summaries without exposing private archive details
      subprocess
    3. Generate and validate one public Chronicle v2 artifact per eligible day for schema, citations, coverage, and privacy
      decision
    4. Require exact-source release proof and an absent-target, additive-only production dry-run for every artifact
      decision
    5. Retain unavailable dates and send failed, incomplete, or mismatched cases to human operator review instead of skipping or overwriting
      decision
    6. Publish each eligible report once and verify database, route, discovery, indexing, sitemap, drift, retry ledger, and proof
      subprocess

    Related notes