Newsroom
selects the story
before production.
A news RAG and editorial control plane. It collects, retrieves, scores, verifies, and slates the news, then ships evidence-backed contracts. Audience-facing content generation stays with Warehouse.
The job.
Newsroom decides what the day's news story is. Its editorial loop canvasses roughly 37 RSS and web clusters alongside Ground News, retrieves from a chronological news RAG, scores the candidates, and slates four stories.
The boundary is explicit. Newsroom ships slate and evidence. Warehouse consumes that contract and owns the audience-facing prose and media.
The handoff.
Contract A records a shipped story lifecycle with the slate and its evidence. Each story can carry a platform target and platform angle. Resource work enters the store as a candidate with a resource-preparation request, giving Warehouse a declared request instead of an informal message.
The operating stages cover canvass, the editorial loop, the repository boundary, the slate-to-store handoff, LinkedIn community and resource queues, an external-video gate, self-heal, and deadline watch.
The decisions behind the engine.
Separate evidence and selection from audience-facing production.
Newsroom is the control plane. It collects, retrieves, scores, verifies, and slates. Warehouse authors the finished audience-facing material from the shipped contract.
Make chronology part of the input boundary.
The editorial loop reads the arc-timeline chronological news RAG alongside the source clusters. The ordered evidence record is a declared input to story selection.
Attach the platform decision to the story.
Platform target and platform angle ship per story. That decision travels with the editorial contract instead of being reconstructed later in production.
Represent resource work as store state.
A Warehouse resource request is recorded as a candidate story with resource preparation requested. The queue is visible in the same lifecycle as the rest of the editorial work.
Treat health and deadline checks as operating stages.
Self-heal and deadline watch sit beside canvass and the editorial loop. They are declared parts of the engine's job.
The operating stack.
Licensing this engine
Newsroom is for an operator that needs a repeatable evidence-to-slate editorial loop. It is operated software set up for the licensee, with sources, evidence, story selection, and the production handoff kept as declared stages.
Who it suits - Anyone who has to decide what to say from evidence rather than instinct: newsletter operators, trade and niche publishers and agencies running client programmes, and equally internal comms, competitive-intelligence and security teams. Proven here on PickBits Daily and the CyberHawk CVE alerts.
What it replaces - Manual sourcing and scoring, and a calendar of what-to-cover maintained by hand.
Run it for - A subscription or ad-supported publication in a defined niche.
- Your source set, scoring rules and evidence backbone stood up
- The slate-to-handoff loop wired to wherever the work goes next
- Sources — how many feeds, and how often they change under you
- Cadence — how many slates a week have to land
- Verification — how much evidence a story carries before it ships
Licensing terms are on application — the list above is what drives them, not a rate card. What you pay tracks that scope.
These engines change as they run; if something here has gone stale, tell me and I will fix it.