Example post: how a Full Time Post story is put together

This is an example post. It is here so the layout, the feeds, the search index and the generated social image can be checked before any real writing exists. Delete src/content/posts/example-post.md when the first real story goes up.

Every story on this site is built the same way. The tooling reads open RSS feeds, public Reddit threads and Hacker News, clusters the duplicates, and ranks what is left by signal. That produces a shortlist. Nothing on the shortlist is published automatically.

From there a human writes the piece. That is the whole standard, and it is the reason the site exists: there is plenty of software that will generate a thousand words about last night’s result, and none of it is worth reading.

What a story has to carry

Every load-bearing claim links to its source. If a number appears in a sentence, the reader can click it and land on the thing that produced the number. Where a claim cannot be sourced, it does not go in.

A second pass reads the finished draft back against its sources and flags anything that has drifted from what the source actually said. That happens before publish, not after.

What a story does not do

No clickbait headlines, no manufactured outrage, no tribalism, and no filler written to hit a word count. A short piece that says one true thing is better than a long one that says nothing.

Front matter reference

The frontmatter at the top of this file shows every field the posts collection accepts. The full contract, including which fields are required and what each one does, is written up in docs/content-contract.md. That document is the interface any tool writing posts into this repository should build against.