What went live in Atlas this week, what is shipping next week, and what we want early-access feedback on. Founder-level note from the Arthea team.


A short note from the team about what shipped, what is shipping next, and where we want feedback. This goes out every week.
What went live
A dead-link guardrail in the publishing pipeline. Every URL in a draft is now checked against a registry of verified-live destinations before it can ship. Posts linking to pages that do not exist, return 404, or have no published content get refused at the publish boundary. The operator sees a hard banner above the preview explaining why.
A pillar-aware destination router. Posts that do not yet have a real source URL now route to the right default for that pillar: product page for product-led posts, booked-call link for conversion-led posts, no link for behind-the-build posts. No more drafts shipping with tacked-on broken CTAs.
Together these two changes catch the failure mode where a draft is voice-perfect, on-pillar, and useless because it points somewhere that does not exist.
What is shipping next week
The first ten Architecture Notes essays are landing on the blog with hero images, a clean reading layout, and the same voice contract every social post ships under. From the moment they are live, the social pipeline starts pointing at real article URLs instead of placeholder routes.
Also coming: a presence overlay on the Validate queue so operators reviewing drafts can see each other working in real time. Useful when more than one person is reviewing the same week of posts.
Where we want feedback
If you are running a content or marketing operation across four or more publishing surfaces and you want a deeper look before the public launch on May 15, reach out. We are taking five teams into an early-access cohort. The price is feedback. We want to see this run against a real pipeline that is not ours, and we want the operators using it to tell us what is missing.




Architecture Notes
Occasional insights on infrastructure, conversion systems, retention architecture, and AI deployment, shared when they’re worth reading.






