choudoufu: AWS and Kubernetes with more on the way, not experimental

src/content/docs/compare/choudoufu-and-terraform-state.md

@@ -22,7 +22,7 @@ Twenty of them, each a scenario that runs in a few minutes. Every one also runs
 
 ## Where it stops
 
-AWS only, and experimental. About half the provider's types carry no tags, so they are identifiable but not governable by a tag condition. The identity of a resource has to be knowable before it is created, and a read-only check reports what refuses before you commit to anything.
+choudoufu runs on AWS and Kubernetes, with more platforms on the way. A missing resource type is rarely what stops a configuration. A `backend "s3"` block, a non-default workspace or a `count.index` in a resource name usually stops it first. `choudoufu live-check` reads your configuration and reports anything it would refuse before you commit to anything.
 
 <!-- scale claims held until the 10,000+ run lands (choudoufu#1051)
 745 resources measured against real AWS. 3,705 on the emulator only.

src/content/docs/compare/control-planes.md

@@ -25,6 +25,6 @@ Workflow files are generated from the declarations that describe the deploy, and
 
 ## Where it fits
 
-choudoufu suits an AWS estate whose owners are willing to run something experimental. On Azure or GCP, or for one hosted thing your whole company logs into, buy the product.
+choudoufu suits an estate on AWS or Kubernetes. On a platform it does not cover yet, or for one hosted thing your whole company logs into, buy the product.
 
 If the guardrail stopping at the edge of the tool is your problem, [get in touch](/contact/).

src/content/docs/tools.mdx

@@ -31,7 +31,7 @@ Declares an agent's sandbox, its secrets and its schedule as ordinary infrastruc
 
 ## choudoufu
 
-A build of OpenTofu where every AWS resource records who owns it, written into the cloud as two tags. The state file becomes a copy you are allowed to lose. Twenty claims about it, each one you can run yourself. Experimental, and AWS only.
+A build of OpenTofu where every resource records who owns it on the resource itself, as two tags on AWS or a label on Kubernetes. The state file becomes a copy you are allowed to lose. Twenty claims about it, each one you can run yourself. It runs on AWS and Kubernetes, with more on the way.
 
 [Docs](https://intentius.io/choudoufu/) · [Source](https://github.com/INTENTIUS/choudoufu) · [Claims](https://intentius.io/choudoufu/docs/claims/) · [Compare](/compare/choudoufu-and-terraform-state/)
 

src/content/docs/work.md

@@ -7,7 +7,7 @@ Everything I build runs in your CI, under your accounts, and stays yours.
 
 ## Estate migration and carving
 
-A large estate gets [choudoufu](https://intentius.io/choudoufu/) as its binary. Each resource gets its own lock and an owner tag, so splitting a team off becomes a tag rewrite and a permissions policy. AWS only.
+A large estate gets [choudoufu](https://intentius.io/choudoufu/) as its binary. Each resource gets its own lock and an owner tag, so splitting a team off becomes a tag rewrite and a permissions policy. It runs on AWS and Kubernetes, with more on the way.
 
 ## Moving from another runner
 

src/data/rooms.mjs

@@ -28,7 +28,7 @@ export const ROOMS = [
 		does: [
 			'Same HCL, same providers, same plan. choudoufu is a build of OpenTofu.',
 			'Ownership moves out of the state file and onto each resource, where your IAM policies can read it.',
-			'AWS only, and experimental. A read-only check reports what refuses before you commit to anything.',
+			'Runs on AWS and Kubernetes, with more on the way. A read-only check reports anything it would refuse before you commit.',
 		],
 		check: [
 			{ label: 'The twenty claims, each one you can run', href: 'https://intentius.io/choudoufu/docs/claims/' },