Cyberplanetary browser experiments

Sixteen distinct, bounded synthetic worlds demonstrate institutional and operational mechanisms in a local browser session. They share a capability-checked state engine and candidate v0.2 description syntax. Each has specialized controls, public state, events, costs, failure scenarios, replay and reset.

This is the first browser milestone, not complete multiuser worlds. No real authentication/privacy boundary, durable hosting of resident state, autonomous residents, distributed consensus, live migration, model inference, economic findings or human preference evidence is claimed. Only synthetic data belongs in this source or these sessions. Closing the tab loses state.

Start with ui/index.html or a world under worlds/. A temporary local HTTP preview is required for ES modules. The shared shell provides typed actions, synthetic actor selection, explicit capability-denial injection, public state and replay. Specialized world pages expose institution-specific scenarios. Daybreak's specialized page probes actual browser capabilities; shared-shell capability fields are explicitly synthetic.

Run npm test, python3 -m unittest discover -s tests -p 'test_*.py', and node worlds/<slug>/test.mjs for each module. No dependencies, paid service or model calls are required. Full JSON Schema validation is a separate optional check; the offline reader's semantic checks are not full schema or network-security validation.

Read docs/INTERFACE.md, docs/MILESTONE.md and each world's README for implemented mechanisms, missing features and next functional increment. Adapter code is reviewed application code, not an untrusted-code sandbox. Demo actor capabilities are client-controlled test inputs, not service authentication. Synthetic canary filtering does not establish general data-loss prevention. Raw state/logs are private debugging surfaces and may include synthetic-private input; public views use observe().

tools/stage_browser.py packages only allowlisted public browser assets into a new dist/ child. Packaging neither deploys a service nor proves URL reachability. Deployment and credential state stay outside source. Public descriptions must use actual HTTPS publication locations; listing does not imply richer compatibility. Shared geometry does not define institutions.