Launching the Cloister blog on cloister.ca

Cloister launched its public site as a focused landing page: enough to explain the thesis, invite early conversations, and establish a sovereign web presence in Canada. What it did not include was a place to publish deeper thinking.

That gap matters. We want to share practical writing about governed agent workflows, backend evaluation, and how teams can introduce AI systems without losing policy control or auditability.

This blog is the home for product updates, design notes, field reports from protected deployments, and thought-leadership pieces that deserve more room than a landing page can provide.

It also creates the publishing surface for the backend evaluation framework we intend to release as an open resource: a way for engineering and governance teams to evaluate systems against more than raw benchmark performance.

The implementation stays true to Cloister's current website model. Posts are authored in-repo, statically generated with the existing Next.js deployment, and exposed through the same bilingual English/French route structure as the rest of the site.

That keeps publishing lightweight, reviewable in pull requests, and ready to grow without committing the team to a heavier CMS before the cadence justifies it.