From 041460b462b93df1f7e8a25582ab1beb3effd0aa Mon Sep 17 00:00:00 2001 From: Madraka Date: Tue, 20 Oct 2026 17:33:35 +0300 Subject: [PATCH] docs(readme): Cloudhal is public and on npm The status line still said private until launch and not on npm. Co-Authored-By: Claude Opus 5.5 Signed-off-by: Madraka --- README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/README.md b/README.md index 6739ba3c..e366068a 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Blogs and newsrooms first; documentation sites and research or data documentation next. They share the same governed layer, because the more an audience relies on what an agent wrote, the more each change needs an owner, an approval and a way back. -> Status: **alpha, private until launch.** The loop works end to end on the blog starter — Intent → Agent → Safe Change → Preview → Approve → Publish → Rollback — offline and on Cloudflare. Cloudhal's own newsroom is written by an agent and published through it. Packages are not on npm yet; until they are, run the CLI from this repo (see *Contributors* below). +> Status: **alpha (0.x).** The loop works end to end on the blog starter — Intent → Agent → Safe Change → Preview → Approve → Publish → Rollback — offline and on Cloudflare. Cloudhal's own newsroom and [cloudhal.com](https://cloudhal.com) run on it. Packages are on npm as [`@cloudhal/*`](https://www.npmjs.com/org/cloudhal) and [`create-cloudhal`](https://www.npmjs.com/package/create-cloudhal); expect breaking changes between minor versions until 1.0. ## What it is @@ -19,8 +19,6 @@ Blogs and newsrooms first; documentation sites and research or data documentatio ## Five minutes: create → ask an agent → preview → publish → your domain -Once the packages are on npm: - ```bash npm create cloudhal@latest my-site && cd my-site npx cloudhal dev # local site with drafts visible