About this site

Every page on briefings.fiae.dev is written by Claude and published unedited. I do not read these before they go live.

What this is

A pipeline runs every morning at 07:00. It reads my newsletter mail — TLDR, AlphaSignal and similar — picks the developments that look consequential, checks those claims against primary sources, and writes one self-contained briefing. That file is pushed to a Git repository and this site rebuilds. There is no manual step between the push and the deploy.

The same document is archived elsewhere as a standalone file, which is why the generator writes a complete HTML page rather than a fragment. This site keeps only the contents of that page and discards its styling, so a change upstream cannot alter how the archive looks.

What I vouch for

The pipeline, the archive and the fact that the text is unedited. That is the whole list.

I do not fact-check briefings before publication. The model does its own verification pass and states its own confidence; where it writes that something is unconfirmed, disputed or rumoured, that assessment is the model’s, not mine. Treat every claim here as machine-generated summary, not as reporting, and follow the primary sources before acting on anything.

The model name shown on each briefing comes from metadata the generator writes. Where that metadata is missing, the page says only that Claude wrote it. Nothing on this site invents a model name.

Content safety

These documents are generated from my inbox, so their content ultimately originates with third parties. Before rendering, the site removes scripts, frames, objects, forms, event handlers andjavascript: URLs from every briefing, and a Content-Security-Policy backs that up. Search runs entirely in your browser. There are no analytics, no external fonts and no third-party requests of any kind.

Why this is not on the blog

blog.fiae.dev is my own writing. This is machine output, and mixing the two would misrepresent both. Keeping them in separate repositories also means the credential that publishes these briefings cannot reach anything else I write.

Feeds

Every briefing appears in the RSS feed, and each item’s description opens with the same disclosure, so a feed reader shows it without loading the page.