Cyberplanetary · registration, discovery, and two worlds

Reference implementation candidate 0.13.3

The separate Milestone A conformance kit 1.0.1 supplies the portable corpus, runner and exact standards closure. It corrects neutral artifact coverage and selection enforcement; its assessed runtime is 0.12.0. Source and installed candidate assessments are delivered separately from this implementation-neutral public kit.

Candidate 0.13.3 retains the durable bounded requester, local request-context rotation and direct-public reference provisioning. It retains original canonical requests and verifies returned records before confirming outcomes. The separately versioned Milestone B live conformance kit 1.0.5 defines selective availability with validation of supplied known references, terminal-only causal audit applicability, executable fresh candidate handoff and bounded startup diagnostics. The four owning patch editions commit that exact corrected core. Implementation qualification and deployment evidence are reported separately from the public test kit.

This release publishes fixed-reference reading and bounded live producer, processor and requester conformance criteria. The public kit provides executable methods for signed exchanges, retained outcomes, retry/status, supported restart and finite service-local retention. Existing wire formats, compact outcomes and provider-owned contents remain selected. The separate assessment packet records which exact source and installed implementations earned each claim.

The conformance editions are CP 0011 v0.2.1, CP 0008 v0.3.0, CP 0005 v0.13.3, CP 0009 v0.7.3, CP 0010 v0.5.3 and CP 0006 v0.11.3. CP 0007 v0.3.0 and the registration/resource/static-asset foundations remain selected. Published predecessors and existing place-agreement primitives retain their exact identities. The public test kit identifies the applicable closure, roles, optional capabilities and finite assessment limits. Exact source and installed artifact commitments are required; a package version alone does not identify assessed bytes.

Active assignment, place and geometry runtime companion bytes retain CP 0005 v0.11.0, CP 0009 v0.5.0 and CP 0010 v0.3.0. The wire identifiers remain unchanged. The existing exact place-agreement artifacts retain their baseline primitive selections, including CP 0011 v0.1.0 and CP 0010 v0.2.0 where stated. Runtime CP 0008 v0.2.0 and CP 0011 v0.1.0 primitive files are preserved as those identified selections; the separately assessed conformance editions add explicit reading and acceptance criteria. No fallback or automatic agreement adoption is implied.

Arcology remains coordinate-free and non-geometric. Cipherlot combines independently authored contributions through explicit fixed reference relationships. JavaScript and native Python interpret these selected contracts independently. The current world definitions and operating deployment are separate from this bounded conformance assessment release.

Bounded movement and support standards target

The completed bounded implementation milestone selected CP 0011 0.6.0, CP 0012/13 0.3.0, CP 0014/15 0.3.1, corrected portrayal CP 0010 0.9.0 and guide CP 0006 0.16.1. Exact immutable files and selections are recorded in the interval and compact-release contract lock, with the delta from numerical packet 1. These editions specify bounded translation, separately authorized control and sensing, contributed kinematic candidates with accountable acceptance, and cross-provider support/release. Optional handoff is separate. Authored checks do not establish runtime interoperability or computational savings.

Port-readiness contract extension

The successor profile CP 0015 v0.4.0 selects bounded evolving translation and attitude, same-time pose/rate transport, mechanical contacts and fields, scoped coupled effects, authorized contributed dynamics, situated image resources and supplied-audio actions. Exact native edition references and companion commitments are in the authoritative register. The earlier bounded translation milestone and its immutable selections remain historical results.

This is a contract extension, not a claim that the required distributed proving world or Expedition port is complete. Minds remain external; semantic-only worlds, nonvisual geometric access and view-only clients remain supported. No concept definitions or CP 0007 time semantics change. Portable generic inputs and offline runners are in the conformance source closure. Executed assessments and operational publication evidence are distributed separately.

The preceding claim-admission clarification is CP 0013 0.4.3, selected by CP 0015 0.4.5 / interactive-federated-world/v10 and explained by CP 0006 0.17.5. The issuer measures maxClaimMs from its atomic claim-admission security instant; the original claim attests admission without adding a timestamp field. Exact replay preserves the original lease. The versioned verification-v0.8 package provides 22 offline groups; actual issuer/independent-peer and full proving-world evidence remain separate. Earlier selections and releases retain their exact identities.

The bounded cooperative timing successor selects CP 0013 0.4.4 (foundation) and 0.4.5 (dynamics), CP 0014 0.4.1, CP 0015 0.4.6 / interactive-federated-world/v11, and guide CP 0006 0.17.6. Its task/claim, fence, prepare and commit maxima are respectively 300, 180, 120 and 180 seconds, subject to every tighter original security and source horizon. Existing operations retain their immutable deadlines. Terminal replay retention begins at durable original response recording; unresolved commitments remain fenced. The verification-v0.9.1 closure provides 30 offline groups. These contract and reproduction results do not establish completion of the distributed proving world.

The mixed traction and restraint successor selects CP 0014 0.4.3, CP 0013 0.4.8 (dynamics) and CP 0015 0.4.9 / interactive-federated-world/v14. It adds explicitly selected fixed-relative-pose and normal-support restraints alongside traction and optional axle hinges, with one aggregate impulse/couple procedure and fail-closed model-to-witness dispatch. Existing authority, acceptance, timing and resource bounds remain selected. The verification-v0.12.1 closure supplies 44 portable groups and 79,943 closure checks. These are source checks; signed runtime interoperability and the full proving-world assignment remain separate.

The exact-parent binding correction selects CP 0015 0.4.10 / interactive-federated-world/v15. It joins cooperative timing to the selected computation v5 root, selects the current sensing-v5 resource checker, and supplies a current capability-claim schema with exact profile-digest validation. All fifteen roots, mechanics, timing bounds and predecessor artifacts remain unchanged. The production target-adoption loader and selected resource checker are included in the qualification procedure; source checks and target installation do not establish the full distributed proving-world claim.

Choose your starting point

• Read the published standards for implementation requirements and each edition's downloads.
• Use this repository for registration/discovery, the catalog, Cipherlot, Journal Vaults, and the CP 0005 runtime.
• Install the World Organizer for operator and inspector interfaces.
• Install the Simulator for the simulator product and its Python implementation.

The product repositories own their wrappers, installers and usage guides. Their pinned protocol dependencies come from this repository. Website publication, project operations and evaluation records are maintained separately with appropriate private Forge access.

Run the registration and static-source demonstration

Use Node 22.16 or newer in the 22.x line, and tar. There are no runtime npm dependencies and no model, paid API, account or externally hosted asset is needed. Use a supported patched Node 22 runtime for public operation.

npm test
npm run demo

This retained registration demo uses the earlier static Cipherlot and locally navigated Journal Vaults examples. The current distributed place programme and client installation are described in the two-world guide. The registration demo prepares and signs two worlds with freshly generated local keys, starts four loopback HTTP services, registers both worlds through the catalog's advertised submission endpoint, and explicitly publishes both through its operator API. It never inserts seeded catalog rows. Repeating the command preserves identities, keys and receipts and does not create duplicate statements.

Local destination	Address
Documentation preview	http://127.0.0.1:8780
World catalog, registration form and generic resource reader	http://127.0.0.1:8781
Cipherlot (garden)	http://127.0.0.1:8782
Journal Vaults (house rooms)	http://127.0.0.1:8783

Press Ctrl+C to stop. .state/ holds the local-only keys, generated public artifacts, database and evidence. It is excluded from source distribution. Deleting it loses the local identities and catalog history; never use deletion as a production reset procedure.

A fresh demo starts with an empty catalog before its two ordinary HTTP registrations.

What is implemented

Core protocol. Strict bounded JSON, one flattened JWS signature with the fully specified Ed25519 algorithm, public-JWK thumbprint identifiers, multiple worlds per key through independent nonce-based world tokens, exact protected bytes, linked sequential revisions, separately attributable catalog records, optional profile claims, and explicit failure outcomes. No cell resolution or world ontology is imposed.

World catalog. Native Node HTTP and SQLite, a discoverable public registration endpoint, durable receipts, idempotent retries, catalog-local revision ordering, operator publication/withdrawal, paginated public records, source download and a browser interface. Incoming URLs are data, not server-side fetch instructions. Pending submissions are not publicly listed. The default queue is a reference deployment policy, not a requirement that every catalog must use moderation or perform assessments.

Profiles. HTTP Registration specifies submission/receipt behavior. Linked Resources allows a generic client to list and check committed material without interpreting its world model. Static GLB Scene selects a small, explicit glTF 2.0 subset. Each has its own source document and exact version identifier.

Current place worlds. Arcology and Cipherlot have distinct world selections, provider-owned contents, shared bounded cabinet and lamp interactions, and one reusable client with two presentations. Arcology has explicitly declared floor order and distinct provider contributions, with no coordinates or geometry. Cipherlot supplies immutable meshes, qualified entity bindings and live rigid cabinet poses. Authoring and operating instructions describe independent installation without promising deployed availability.

Static Cipherlot source. The retained visual source is an original pastoral neighbourhood park, generated as a self-contained GLB with shared trees, slatted benches, residences and storefronts, with orbit/zoom/keyboard controls, a downloadable scene, and a bounded, depth-tested software preview when WebGL is unavailable. No avatars or artificial people are implied. It uses Linked Resources and Static GLB Scene.

Local Journal Vaults source. Seven original linked reading rooms, expressed as a local JSON content model and a navigable text experience. It has no geometry. It uses Linked Resources, not the scene profile. Choices affect the browser's view; there is no shared mutable world state.

These retained source examples use independently generated signing identities and are separately hostable. They can use any catalog accepting the relevant registration profile. The generic resource reader can inspect both without bespoke knowledge of either content model.

Start reading

• Current numbered standards: the authoritative register lists exact current editions, historical predecessors and their immutable selected contracts. Document editions preserve their explicitly selected wire/profile identifiers.

Selected standards downloads permanently include separate automatically generated publication diffs, defaulting to current-to-previous. Two optional row dropdowns select any published edition and any other edition for an on-demand comparison. First releases include an explanatory file. See the download contract.

• spec/world-registration-and-discovery-0.1.0.md: the technical core and its required processing.
• profiles/: the three bounded agreements.
• docs/DIRECT-RUNTIME.md: independent provision, shared references and additive assignment.
• docs/DIRECT-RESPONSIBILITY-WIRE.md: current responsibility wire and signed evidence.
• docs/HYDRATE.md: generic preparation and self-hosting instructions.
• docs/OPERATIONS.md: key custody, updates, moderation, backup and rollback.
• docs/SECURITY.md: threat boundaries and known limitations.
• docs/STANDARD-KINDS-GUIDE.md: informative guide to the four kinds of document (specification, profile, rules, report) under CP 0000.
• docs/DECISIONS-AND-SOURCES.md: source-derived boundaries versus new engineering decisions.
• docs/TESTING.md: runnable tests and their scope.

A world registers; an operator publishes

After preparing and hosting a deployment:

node tools/register-worlds.mjs \
  --deployment /srv/cyberplanetary/public/deployment.json \
  --receipts /srv/cyberplanetary/receipts

This verifies the published worlds and submits their history over the advertised HTTP interface. It does not publish pending submissions. To carry out the deliberately selected local publication policy:

node tools/register-worlds.mjs \
  --deployment /srv/cyberplanetary/public/deployment.json \
  --receipts /srv/cyberplanetary/receipts \
  --publish --token-file /srv/cyberplanetary/keys/catalog-admin.token

Do not substitute direct database edits, a static catalog fixture, or hard-coded demo cards for these exchanges.

Independent use

The CLI supports key generation, signing a supplied statement, verification, submission and operator actions. node tools/cli.mjs prints its command forms. Publishing a signed statement does not require running the reference service. A world can have zero profiles and no entries; executable boundary fixtures test that case.

A repository, a catalog, a signing identity, a public website and a world are different things. Each world has its own signing identity, origin and data contract.

License and source

Project software is supplied under AGPL-3.0-only, as already selected for Cyberplanetary. See LICENSE. The scene generator, original scene, reading content and public documentation in this release are included in this project distribution. No font files, purchased standards, private deployment corpus, production key, customer record or licensed model is bundled in the public source.

prepare builds a complete corresponding-source archive from an explicit source whitelist and serves it at the catalog's /source.tar.gz. Any operator modifying the running code must rebuild that artifact from the code actually deployed; do not leave the unmodified upstream tarball as the only source for a modified service.

Canonical releases

This repository is the canonical public source for the protocol, profiles, catalog, and both world implementations. Journal Vaults and Cipherlot retain independent origins, signing identities and data. Website brand originals remain canonical in the private website repository; only the explicitly mapped public brand projection is copied here. Use the preparation guide for generic self-hosting.

Numbered standards

Current standards are published at https://cyberplanetary.org/standards/. standards/series/register.json owns their identity, status and released file digests. Ordered sources under standards/series/source/ are the sole authoring source for future versions; files under published/ are immutable releases. The original 0.1.0 protocol/profile files remain exact profile-claim references. Standards document 0.2.0 changes structure and informative example names, not wire requirements. Build with installed Publication Series Manager and the pinned Markdown build dependency: python3 tools/build-standards.py --register standards/series/register.json --out NEW_DIRECTORY. The build validates the register, verifies digests, composes no new release, renders released canonical artifacts, and audits every generated standards file/download.

The bounded original-proof resolution successor selects interactive-federated-world/v12, including the exact base/observation/computation/cooperation agreements in its profile artifact. Portable source checks are in standards/series/conformance/port-readiness-1/verification-v0.10.1/; its SOURCE-LOCK.json binds the selected profile, actual native release pins and 37 current/historical test groups. Older source closures and published editions remain distinct. This source and publication evidence does not establish completion of the broader proving world.

Active world sources use their public names: web/cipherlot/ and tools/cipherlot-scene.mjs own Cipherlot; web/journal-vaults/ and tools/journal-vaults-data.mjs own Journal Vaults. Prepared directories use cipherlot and journal-vaults. Legacy config keys, existing private key filenames, generator imports and public module URLs remain compatibility aliases. Signed world IDs, resource IDs, committed content and published versioned standards are unchanged by this source naming refactor.