A content engine that is not allowed to make things up

A weekly job builds four drafts for the days the team posts, each from a different source: a partner spotlight or news item, a team update, a topic from the energy-management brand and a consented project. A registry stops any source being used twice, and every draft lands in an approval queue rather than going out.

When there is no sourced news, no unused team update or no consented project, the slot becomes an explicit 'add a sourced record' placeholder rather than a plausible filler post. Partner claims must be verifiable against the official product page or the model returns nothing.

Feeds are parsed in parallel, filtered to the last week, capped, de-duplicated by URL and every URL is checked to resolve. The model only classifies and summarises; the link and the title come from the feed, so it has no way to invent a source. Every run, successful or not, is logged.

The generation prompt allows funding and statistics only from verified funding records; anything else is dropped or flagged. The approvals screen blocks approval while unverified claims remain, across emails, social posts, blog posts and press articles in one queue.

Project-led posts use only installs flagged as consented for publicity. If none are, the system falls back to generic process copy instead of reaching for a client's site. The data backs the caution up: none of the installs on record had yet been flagged, so none had been used.

A shared mailbox is polled for company updates from two allow-listed domains only, de-duplicated by message ID, with text extracted from Word, Excel, PDF and text attachments and stored beside a grounded rewrite. A SharePoint sync parses project codes, shoot dates and tags from folder and file names and indexes the photos and videos so the team can find them by project.

Every five minutes the publisher takes whatever is due, posts to a person or organisation page as configured, stores the post identifier and writes a run record. A failed post becomes an urgent action item and is retried by the scheduler, so a silent failure is not a state the system can be in.