SOWWWL / validation deck

Validate the frame here before it graduates to cloud.

sowwwl.org becomes the review layer: the place where copy, structure, domain roles, and handoff logic are checked in daylight before sowwwl.cloud takes over as the canonical hub.

Open the canonical hub Open the user ingress Open the user cloud shell
validate sowwwl.org

Test message, naming, domain hierarchy, and outward clarity here first.

promote sowwwl.cloud

When the frame is approved, move the validated structure and copy to the hub.

operate sowwwl.xyz / 0.user

User-facing ingress and cloud shell keep their roles, but inherit the approved frame.

Promotion rule

The point is not duplication. The point is approval first, canon second.

What gets validated here

  1. Message: the wording says what each host is for without collapsing them together.
  2. Structure: the CTA order, information hierarchy, and next-step links feel obvious.
  3. Map: the relationship between .org, .cloud, .xyz, and 0.user stays legible.

Promotion threshold

Once the public frame is coherent and the routing feels right on sowwwl.org, the approved shell moves to sowwwl.cloud. The cloud host should carry the canonical map, not the experimental draft.

Validate slowly. Promote cleanly. Keep the hub authoritative.

Domain roles after rebalance

  • sowwwl.orgValidation and public review layer
  • sowwwl.cloudCanonical hub once approved
  • sowwwl.xyzUser ingress / personal land creation
  • 0.user.o.sowwwl.cloudUser cloud shell / SPA
  • api.sowwwl.cloudAPI, docs, health, status
  • 0wlslw0.comExperimental door

If the structure is not approved on sowwwl.org, it does not get promoted to sowwwl.cloud.