Cyberplanetary simulator

This repository owns simulator wrappers, local controllers and the independently authored Python participant distribution. Organizer authority and inspector presentation belong to the world organizer repository. The protocol repository owns shared runtime, schemas and standards source. Read the published standards for normative requirements.

Start with the installation and release guide, then the operating guide. Product source packages and Python source/wheel belong on this repository's Forge releases. Use the release's exact source commit and manifests; package version alone does not select bytes.

The simulator wrapper requires event-driven controller execution for place-inspection/2, geometric-place-inspection/2, and spatial-place-inspection/1. It rejects a scheduled selection before credential refresh or participant startup. The synthetic environment retains its selected scheduled execution path.

Current simulator 0.13.0 selects the exact protocol runtime in dependency.lock.json and independent Python 0.13.0. Its bounded content readers expose independently validated semantic, spatial, and geometric interpretations, including accepted public reference context. Exact installed selections are recorded in operations/direct-manifest.json and dependency.lock.json.

The maintained operating path follows CP 0005, with protocol cyberplanetary.responsibility/0.7.0, rules independent-assignment/3. An assignment identifies a provider; it does not inherit a simulation.

The organizer records authenticated participation and assignment decisions. Independent providers own and supply their local state. A valid replacement can start with different content at a previously used scope while the former provider and all of its state are unavailable. No checkpoint, import, source cessation, readiness, global run or cross-provider request inheritance is required.

Use the operating guide, immutable dependency lock, and current installation examples. Builders and renderers perform no publication, credential creation or host activation. Authentication, authorized assignment, bounded parsing and relevant scoped evidence remain required.

python3 bin/dependency.py hydrate
python3 bin/dependency.py verify
python3 bin/direct-install.py /private/install.json --out /private/new-render
node bin/direct.mjs --help

Operators can stop services without completing withdrawal or preserving state. Clients distinguish assignment, availability, source context and historical content. Old provider-targeted mutations cannot be transparently retried at a replacement. Historical releases, world identities, structural descriptions, credentials and unrelated services are preserved. Historical fixed/continuing implementation and instructions remain recoverable at immutable release source; they do not define this edition's operating path.

CP 0007 temporal references and CP 0008 structural descriptions are independent selections. The demonstration agreement selects both and declares coarse summaries and detailed private supports. Authorized structural additions preserve existing meanings and allocations; added parts receive ordinary grants and requester permission separately. Shared references create no common state, inherited requests or shared computation schedule.

The operations manifest selects the independent Python source and wheel. Use the verified installation commands and the maintained Python install example with cp5sim.local-settings/4.

The place-world guide covers distinct semantic-only and geometric world selections, provider-authored contents and live rigid poses, and the reusable inspector/viewer with separate per-world entries and caches.