Daily local-news ingestion workflow

EP047 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.

Immediate local routeFuture hosted routeSafeguard / approvalData boundary

Immediate route — cost-effective daily local agent

Schedule

Daily run starts

A fixed daily schedule starts one local ingestion run; no client action is required.

daily_news_ingestion
→
Research

Run local-news skill

Hermes or Codex runs the existing local-business-news skill and researches multiple credible sources.

→
Editorial

Write publication-ready stories

Produce original, source-backed copy with verified facts separated from clearly labelled local reading.

→
Deployed intake

Deploy private JSON batch

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.json
→
Automatic importer

Deploy-triggered Render import

Render automatically starts the hosted importer after deployment. It reads only pending ledger-backed batches, validates schema, deduplicates, and applies town/category/scope tags.

→
Automatic outcome

Store draft / review-required

Each valid item becomes a hosted Postgres draft; incomplete, uncertain, or duplicate items become review-required. No import button exists.

news_articles: draft | review_required
→
Publication policy

Publish only by approved policy

Import never publishes. Any future automatic publication must satisfy an explicitly approved policy after source, facts, local reading, tags and public scope checks.

status: published
→
Public site

News site reads DB

The public News page reads published database records through the API; JSON is never public.

Future route — fully autonomous hosted agent

Hosted schedule

Managed daily job fires

Render or another hosted scheduler starts the run independently of any laptop or local session.

→
Autonomous agent

Research and compose

Hosted agent calls approved research tools, compares multiple sources, and creates the same structured story contract.

→
Shared downstream route

Reuse JSON-to-database ingestion

After generation, the hosted agent writes the defined JSON intake; the always-running importer picks it up. There is no separate future importer path.

→
Policy gate

Human or policy approval

Autonomy does not bypass editorial controls: failed evidence, uncertain facts or ineligible scope remain draft.

→
Database output

Publish through Postgres

Only approved published records become visible to the database-backed News site.

Safeguards — apply to both routes

Automatic retry

Ledger-backed bounded retry

Render automatically retries only transiently failed pending batches with bounded backoff; failed intake remains private and never publishes partial output.

→
Idempotency

Exactly-once batch import

Batch IDs and content hashes in a durable importer ledger prevent re-import after deploy retries, restarts, or scheduled reconciliation.

→
Audit

Trace every automatic decision

Record deployment, batch ID, source, extraction time, agent/run ID, validation result, importer outcome, reviewer, scope decision and publication transition.

→
Hard boundary

JSON never becomes public

Private JSON is deleted or retained under access control after import; the site exposes only approved DB records.