Daily run starts
A fixed daily schedule starts one local ingestion run; no client action is required.
daily_news_ingestionEP047 agreed operating model — a local Hermes or Codex agent creates an intake batch, then deployment automatically triggers a Render-hosted importer. The importer uses a durable ledger to import each batch exactly once, route every item to draft/review-required, and schedule bounded retries. No manual command, button, local database write, or client action is part of this workflow.
A fixed daily schedule starts one local ingestion run; no client action is required.
daily_news_ingestionHermes or Codex runs the existing local-business-news skill and researches multiple credible sources.
Produce original, source-backed copy with verified facts separated from clearly labelled local reading.
The local skill writes one schema-defined private batch; it is deployed to the designated Render intake path with the application release.
private_news_intake.jsonRender automatically starts the hosted importer after deployment. It reads only pending ledger-backed batches, validates schema, deduplicates, and applies town/category/scope tags.
Each valid item becomes a hosted Postgres draft; incomplete, uncertain, or duplicate items become review-required. No import button exists.
news_articles: draft | review_requiredImport never publishes. Any future automatic publication must satisfy an explicitly approved policy after source, facts, local reading, tags and public scope checks.
status: publishedThe public News page reads published database records through the API; JSON is never public.
Render or another hosted scheduler starts the run independently of any laptop or local session.
Hosted agent calls approved research tools, compares multiple sources, and creates the same structured story contract.
After generation, the hosted agent writes the defined JSON intake; the always-running importer picks it up. There is no separate future importer path.
Autonomy does not bypass editorial controls: failed evidence, uncertain facts or ineligible scope remain draft.
Only approved published records become visible to the database-backed News site.
Render automatically retries only transiently failed pending batches with bounded backoff; failed intake remains private and never publishes partial output.
Batch IDs and content hashes in a durable importer ledger prevent re-import after deploy retries, restarts, or scheduled reconciliation.
Record deployment, batch ID, source, extraction time, agent/run ID, validation result, importer outcome, reviewer, scope decision and publication transition.
Private JSON is deleted or retained under access control after import; the site exposes only approved DB records.