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.
Workflow diagram
Swipe horizontally to inspect the full diagram.
Workflow chain
Twice-weekly Chronicle publisher→Report artifact intake→Chronicle Visualizer private archive and publication loop
Part of project
HyphenomenonParent project
Twice-weekly Chronicle publisherThis workflow
Workflow diagramRendered with the workflowWorkflow
Twice-weekly Chronicle publisher
- Start Monday and Thursday at 9:00 AM America/New_York and enumerate every completed day not yet represented publiclystate
- Confirm exact-day coverage and recover only eligible aggregate source summaries without exposing private archive detailssubprocess
- Generate and validate one public Chronicle v2 artifact per eligible day for schema, citations, coverage, and privacydecision
- Require exact-source release proof and an absent-target, additive-only production dry-run for every artifactdecision
- Retain unavailable dates and send failed, incomplete, or mismatched cases to human operator review instead of skipping or overwritingdecision
- Publish each eligible report once and verify database, route, discovery, indexing, sitemap, drift, retry ledger, and proofsubprocess