Cold read of https://bounded.tools, 2026-09-03.
/blog/ lists six posts and is one of seven items in the primary nav. There is no way to follow it. Measured:
| Path |
Status |
/feed.xml |
404 |
/atom.xml |
404 |
/blog/feed.xml |
404 |
No <link rel="alternate" type="application/atom+xml"> on any page either.
The site's own conformance report already names the gap, under semantic:
Atom feed (RFC 4287) — not assessed — no feed report supplied (optional)
Marked optional, which is a fair call for a criterion. It is a less fair call for the product. The posts are the part of this site a stranger is most likely to want more of, and the only offered follow is "check back."
Worth noting what already exists, because it makes the gap cheap to close: every page is served as Markdown at <route>.md, llms.txt enumerates all six posts, and sitemap.xml lists them with the same slugs. The post list is already a derived artifact. A feed is another projection of it, not new content to maintain.
Suggested shape
- Generate
dist/blog/feed.xml from the same source gen-blog.mjs already walks. Atom, since the conformance criterion names RFC 4287.
- Add the
<link rel="alternate"> to the blog index and post pages.
- Flip
semantic.atom-feed from not-assessed to assessed once it validates. One of the twenty-one grey rows on /conformance turns green for real work rather than for a report being supplied.
Related to #209's scope line about not-assessed criteria that could move with evidence already in hand, but this one needs the artifact built first, so filing separately.
Filed from a cold read, unclaimed and unassigned.
Cold read of https://bounded.tools, 2026-09-03.
/blog/lists six posts and is one of seven items in the primary nav. There is no way to follow it. Measured:/feed.xml/atom.xml/blog/feed.xmlNo
<link rel="alternate" type="application/atom+xml">on any page either.The site's own conformance report already names the gap, under
semantic:Marked optional, which is a fair call for a criterion. It is a less fair call for the product. The posts are the part of this site a stranger is most likely to want more of, and the only offered follow is "check back."
Worth noting what already exists, because it makes the gap cheap to close: every page is served as Markdown at
<route>.md,llms.txtenumerates all six posts, andsitemap.xmllists them with the same slugs. The post list is already a derived artifact. A feed is another projection of it, not new content to maintain.Suggested shape
dist/blog/feed.xmlfrom the same sourcegen-blog.mjsalready walks. Atom, since the conformance criterion names RFC 4287.<link rel="alternate">to the blog index and post pages.semantic.atom-feedfrom not-assessed to assessed once it validates. One of the twenty-one grey rows on/conformanceturns green for real work rather than for a report being supplied.Related to #209's scope line about not-assessed criteria that could move with evidence already in hand, but this one needs the artifact built first, so filing separately.
Filed from a cold read, unclaimed and unassigned.