Cloud World building examples · All people and records are fictional
Optional orientation, with no sign-in. Explore arrival, foundry preparation and handoff readiness. Nothing here saves to a real room, assigns work or records agreement.
Wizard Joe Your practice companion
Cloud 9 · Optional Cloud World building practice
See how a Cloud World project is prepared.
Meet Joe
Joe’s hint
We can inspect a fictional Cloud World building example before opening a real room. Choose “Meet Joe and choose a quest” when you are ready, or skip and explore freely.
“I’m Joe. A fictional team is preparing Cloud World’s first-visit guide. Let’s find who confirmed responsibility, which evidence needs review, and what still needs a human decision.”
This little quest is yours to try, skip or put down. No sign-in, score or real approval.
My practice notebook · 0/3 clues
Cloud World arrival quest: Meet Joe.
Responsibility: place not kept yet
Pending decision: place not kept yet
Evidence revision 1: place not kept yet
Only these practice checkpoints are kept in this browser. They contain no account, private work, names you enter or real agreement.
A fictional workshop
Project sky
Explore a place. Follow its sample work, decisions and evidence.
3 of 3 previews
Opening controls… Page links remain available.
Reading the sky
Mint outline Selected preview · Blocked Explicit blocker · Needs you: personal attention.
Each illustrated place is a project preview. Landmarks take illustrative cues from the recorded purpose; they are not official project categories. A bright path means owner confirmation is recorded. A bright evidence lantern means work is in review with an evidence revision. These symbols do not mean approval. Read the labels and source records. Position is a stable layout, not priority or E8 meaning.
About this preview and its connections
Every person, project and record on this page is fictional. The pictures illustrate places to work; they do not show live people, progress, permission or agreement. Real rooms require sign-in and their own membership.
What happens inside a project
One project, three things to inspect
These read-only samples show a fictional team building Cloud World. Ari, Lee and Morgan are invented teammates. In a real room, its actual Sphere policy and permitted people govern each action.
Showing Cloud 9 arrival. All three examples remain available above.
Cloud 9 arrival
Help a first visitor find their way into Cloud World and understand what each instrument is for.
Sample work · In review
Prepare the Cloud 9 first-visit guide
Owner: Ari, a fictional teammate, has confirmed responsibility.
Next: The required reviewers check evidence revision 1. They can ask for a correction before accepting it.
Assigning someone does not mean they have accepted the work.
Sample decision · Still proposed
Agree on the first-visit route
This example uses two required people: one has agreed and the other has not. The sample decision stays proposed.
Opening this record, reading it or adding a note does not count as agreement. Two is only this example’s rule. The actual Sphere policy determines required signers for real decisions.
Sample evidence · Revision 1
What the reviewers would inspect
An illustrated guide to the World map, intention abacus and Hopf geometry, with a reason to switch, a way back, and an explanation of what resets on reload.
This submission is not accepted yet. A new evidence revision needs its own review. Internal acceptance does not mean a client agreed or the work was published.
Cloud 6 foundry preparation
Prepare one clear Cloud World building question for people to review before taking responsibility or acting.
Sample work · In review
Prepare a Cloud 6 proposal packet
Owner: Lee, a fictional teammate, has confirmed responsibility.
Next: The required reviewers check evidence revision 1. They can ask for a correction before accepting it.
Assigning someone does not mean they have accepted the work.
Sample decision · Still proposed
Agree on the next bounded building step
This example uses two required people: one has agreed and the other has not. The sample decision stays proposed.
Opening this record, reading it or adding a note does not count as agreement. Two is only this example’s rule. The actual Sphere policy determines required signers for real decisions.
Sample evidence · Revision 1
What the reviewers would inspect
A draft packet naming the question, proposed owner, small next step, current evidence revision and unresolved questions. It does not connect a shared foundry or execution service.
This submission is not accepted yet. A new evidence revision needs its own review. Internal acceptance does not mean a client agreed or the work was published.
Joeville handoff readiness
Make a Cloud World handoff understandable to the people who will use and care for the result.
Sample work · In review
Prepare the Joeville handoff note
Owner: Morgan, a fictional teammate, has confirmed responsibility.
Next: The required reviewers check evidence revision 1. They can ask for a correction before accepting it.
Assigning someone does not mean they have accepted the work.
Sample decision · Still proposed
Agree on what is ready for handoff
This example uses two required people: one has agreed and the other has not. The sample decision stays proposed.
Opening this record, reading it or adding a note does not count as agreement. Two is only this example’s rule. The actual Sphere policy determines required signers for real decisions.
Sample evidence · Revision 1
What the reviewers would inspect
A draft handoff note naming the intended reader, confirmed responsibilities, current evidence, open decisions and care contact. Publication and execution still require their own authorization.
This submission is not accepted yet. A new evidence revision needs its own review. Internal acceptance does not mean a client agreed or the work was published.