LostSouls.world

Architecture / reusable collections

Different signatures.
Shared foundations.

A manageable set of building families, room kits and meaningful variants. Developer collections give repeated architecture a believable reason to exist.

On this page

Developer collections

Adopted production method, 15 October 2026. The fictional developer names organize architecture and reuse; corporate histories, owners and political ties remain unwritten.

Stable IDDeveloperCollection directionFirst application
PI-DEV-RELENTLESSRelentless DevelopmentCutting-edge sculptural structures, expressive frames, adaptive skins and integrated technologyCrown Key landmark/tower families; selected experimental work elsewhere
PI-DEV-VICEVice VillasShaded courtyards, garden terraces, tactile stone/timber, low-rise homes and village commerceThe Grove's residential and arts streets
PI-DEV-TIDEMARKTidemark EstatesCoastal hospitality, resort terraces, waterfront public rooms and service-aware promenadesHotels, marina edges and resort neighborhoods

These are reusable production collections, not exclusive territory boundaries. A district may mix developers according to a deliberate composition. A collection assignment does not change a global asset ID or approve a story owner.

Vice Villas replaces the working name Canopy Works by creator direction on 15 October 2026. The former metadata key PI-DEV-CANOPY resolves to PI-DEV-VICE; issued building and district IDs do not change. Corporate ownership remains an open story choice.

Website collections · Production desk

The unit of reuse

developer → shell family → geometry variant → interior kit → appearance preset → district placement

Keep PI-BLD and PI-STR global IDs. Add developer and base-shell metadata rather than renaming issued assets. A cosmetic variation changes color, finish, shading, planting, signage or furniture within the reviewed envelope. Changes to footprint, core, openings, accessible layout or structural silhouette are geometry work and require a documented variant/revision. Never randomly stretch a shell to obtain a different “look.”

Author one representative shell and one playable room kit first; test it, then roll out variations. Use materials and instancing where they fit the mesh and interaction requirements. Share repeated facade bays and non-interactive props; independently interactive doors, lifts and persistent objects need appropriate identities and behavior.

Grove starter collection (planning scope)

Start with eight candidate archetypes, then reduce or expand after the first block test: courtyard house; compact garden house; paired/row garden homes; small apartment terrace; courtyard mixed-use block; village shop/cafe bay; waterfront hospitality block; performance pavilion. This is a proposed starting mix, not eight approved designs or a permanent maximum. First test three representatives: courtyard home, shop/courtyard block and waterfront pavilion.

Each archetype gets a measured plan, entrance/core arrangement, section, approved shell and reusable room kit where enterable. Generate a few meaningful facade/roof/landscape options from that baseline. District identity comes from proportions, roofscape, setbacks, lot composition, materials, activity and landscape as well as facade color.

The asset register and placement manifest must record developer_id, base_shell_id, shell_revision, geometry_variant, interior_kit_id, appearance_preset_id, placement_id and scale_exception_id (normally null). See the current Building Protocol templates. The illustrative 1,000 foundations / 88,000 looks discussion sets no numerical production quota.