LostSouls.world

Production / 15 October 2026

What changed.
What comes next.

The release record and open choices, in one place. Current protocols are Building R05 and District R05.

The 15 October release record below is historical. District R05 controls current district workflow.

Production desk release / 15 October 2026

The creator requested a human-facing brief for Quik, Vice Villas replacing Canopy Works, and website pages for developers, the Black Vault, Crown Key building planning and pertinent production records.

Implemented: one connected production desk, browsable developer collections, 31 searchable building/structure cards with 217 task records, Grove image plan, scale history, district-ID recommendation, recap and two Black Vault sessions. The repo remains the source of record. Site pages preserve proposed/accepted/unverified distinctions.

Current protocols are Building R05 and District R04. Previous R04/R03 releases remain archived. The new guides clarify authorized publication and current naming while retaining the measured-shell, aerial, package and review requirements. Downloads are regenerated from the same source as the pages.

Quik's brief now explains story/production context, the connected-city goal, known scale uncertainty, responsibilities, a first current-world report, integration sample and success criteria before the technical plan.

Open: current UE measurements and authoritative-world selection, final scale, interior selection and dimensioned drawings, connected sample/launcher verification, multiplayer/persistence proof, recovered topo LFS intake, selected Grove original intake and later repo-wide cleanup. District renumbering is a discussion, not an approved migration. Recommendation: stable IDs with separately curated geographic/display order.

Earlier release recap / Building R04 and District R03
On this page

Production recap / 15 October 2026

Decisions carried into this release

  • One connected city: one project, one selected authoritative World Partition world, shared coordinates, work by region and stream at runtime.
  • Hundreds of concurrent users is the online design target; capacity, durable-state services and the exact launch count require tests.
  • Preserve the approved visual blueprint. Final island size, imported transforms, building shell fit and clear interior dimensions require measured reconciliation; this release selects no new physical scale.
  • Reusable developer collections: Relentless Development for cutting-edge architecture, with Canopy Works and Tidemark Estates as proposed complementary collections. Global asset IDs remain unchanged.
  • District protocol family is PI-PROT-DISTRICT. D01 remains Atlantis; Crown Key is D02 and The Grove D03. Historical D01 R02 document labels remain aliases.
  • The Black Vault captures ideas, dates, status and promotion decisions in this private repo. Optical cloaking and comfortable unseen control are creator directions; hybrid ASI terminology/capabilities and the Part 4 power struggle remain open. Future part numbers still need a franchise mapping.

Implemented release contents

DeliverableLocation
Brainstorm system, template, register and first sessionstory/black-vault/
Building R04 and District R03, updated templates, PDFs/DOCX, consolidated baselines and ZIP manifestsproduction/protocols/ and /protocols/
Quik's integration, daily workflow and online proof planproduction/world/SHARED_WORLD_BRIEF.md and /protocols/world/
Measured source history and scale decision sequenceproduction/world/SCALE_REGISTER.md
Developer metadata and reuse rulesproduction/developers/
25 building variants + six structures, 217 task records, proposed room programs and drawing checklistproduction/districts/D02-CrownKey/planning/
Grove reference/image and starter-archetype planproduction/districts/D03-TheGrove/README.md
Current-pointer publishing and release verificationtools/build_protocols.py, tools/build_production.py, tools/verify_protocol_release.py

The registry, source index, asset tracker and working atlas build-status notes are aligned with this release. The historical atlas and issued source artwork stay intact. UE instructions receive a companion update pointing to the new production direction; no Unreal world binaries are edited.

The three original Crown Key source ZIPs were checked for integrity and inventoried separately from the protocol handoff. The topology reference archive is recovered locally but still awaits LFS publication; it is not represented as an available repo download. Historical v01 exact views must be reconciled with v02 before a current build handoff is accepted.

What is left to decide or do

  1. Now: current engine measurements. Quik exports map/actor/component scale and dimensions, connections and evidence at a named commit. Select the final Crown Key/archipelago frame and size from matched image/blockout/route comparisons.
  2. Now: first connected sample. Choose the authoritative map, integrate Crown Key and its west-coast neighbor in a protected branch, and test the bridge/street/interior route. Launcher readiness and clean-machine reproduction remain unverified.
  3. Next: Crown Landmark fit. Confirm L18/L19 host/parcel/levels, taper/core fit, circulation and sightlines against EXT R06 / INT R02. Other buildings' everyday interiors are candidate programs; select the first playable set before commissioning detailed drawings.
  4. Next: Grove art. Select one controlling aerial/layout revision; reconcile the newer Grove/South Beach/west-coast images; develop the courtyard home, village shop/courtyard and waterfront pavilion first. Produce measured plans/sections and reusable kits before many cosmetic variations.
  5. Engineering: online proof. Dedicated-server crowded/distributed-load tests, client/server budgets, AI density, persistence schema and restart/reconnect tests. The architecture target is adopted, not implemented or benchmarked by these documents.
  6. Source intake: recovered originals. Publish the recovered topo ZIP through the repo's LFS workflow; ingest selected new Grove originals with hashes and authority. The package inventory keeps these gaps visible.
  7. Later: story room. Cloak behavior and failures, AGI/ASI terminology, island selection/population logic, who assigns human value, and how Parts 3/4 map to the existing transmedia plan. Capture them in the Vault; do not overwrite locked events by implication.
  8. Follow-up: whole-repo consistency sweep. Compare current decisions, bible/editions, atlas, asset IDs, protocol pointers, engine evidence, redirects and duplicated web outputs. Propose moves/aliases before reorganizing historical material. This broad sweep remains a separate task after the current production corrections.

These are repository-backed plans and production controls. The per-building register specifies which drawings and tests must be made; it is not a claim that final exterior/interior blueprints or hundreds-player networking now exist.