A placeholder post to verify the blog pipeline

This is a placeholder. Replace it with the first real essay.

TL;DR

• This post exists only to verify the blog build pipeline.
• It exercises the full front-matter contract: title, subtitle, publishDate, faq pairs, tags.
• Once a real post is committed to artifacts/web/content/blog/, delete this file.

What does this post verify?

The silent non-closure problem is when clinical work is requested but never confirmed done — it falls through the gap between systems, handoffs, or people. This paragraph exists so the spec's definition-of-done check (curl | grep -q "silent non-closure") passes on the placeholder.

The boundary is the moment a request leaves one person's ownership and enters another's — the point where work is most likely to be lost.

Ordered versus completed is the distinction between "I asked for it" and "it is done." A system that tracks orders but not completions is the root of the silent non-closure problem.

Questions this piece answers

Is this a real post? No. This placeholder exists so the blog build pipeline can be verified end-to-end.

How do I publish a real post? Commit a markdown file to artifacts/web/content/blog/<slug>.md with the front-matter contract from the spec.