The Life EnginePersistent world system Alpha · Enter world

Verified release chronicle / 2801 waves

Many worlds.
One engine.

This is the feature record from First Light through Review Ready. Each Alpha era captures a shipped capability group while every world keeps its declared access, lifecycle, and review contract.

45 release dossiers21 Alpha eras2105 recorded changes37 canonical systems

Alpha program

Alpha 1.9 · current

Review Ready

Waves 2702–2801

Final review packets, source slots, localization queues, and evidence gates

Alpha 1.8 · complete

Content Atlas

Waves 2502–2701

Deep catalogs for every era and distinct authored profiles for every region

Alpha 1.7 · complete

Living Portfolio

Waves 2402–2501

Twenty-two operational worlds, bounded rotation, structured populations, and selectable observatories

Alpha 1.6 · complete

Complete Horizons

Waves 2202–2401

Complete declared epoch and variant portfolio, World Hub, isolation, and validation

Alpha 1.5 · complete

Owner Ready

Waves 2102–2201

Complete reviewer, translator, player-cohort, world-admission, recovery, and VPS handoff

Alpha 1.4 · complete

Closure Evidence

Waves 1902–2101

Contract worlds, century endurance, transition stress, regional dossiers, scale probes, and isolated restoration

Alpha 1.3 · complete

Connected Epochs

Waves 1702–1901

Era breadth, transition rehearsal, review operations, endurance evidence, and infrastructure equivalence

Alpha 1.2 · complete

Measured Horizons

Waves 1602–1701

Completion evidence, staged world promotion, portfolio validation, and Chronicle foundations

Alpha 1.1 · complete

Shared Continuum

Waves 1502–1601

Bounded runtime, private live polling, verified backups, capacity protection, and migration readiness

Alpha 1.0 · complete

Shared Horizon

Waves 1202–1501

Public contract, World Foundry, continuity, responsible play, signed operations, and shared-host completion

Alpha 0.11 · complete

Household Years

Waves 1112–1201

Seasonal conditions, livelihoods, bonds, household branches, milestones, and annual evidence

Alpha 0.10 · complete

Lineages

Waves 1022–1111

Kinship, seasonal care, conflict repair, succession, and generation continuity

Alpha 0.9 · complete

Long Lives

Waves 932–1021

Era places, households, branching lives, private archives, and human promotion gates

Alpha 0.8 · complete

Deep Time

Waves 842–931

Complete era packages, deterministic rehearsal, balance evidence, and rollback proof

Alpha 0.7 · complete

Becoming

Waves 772–841

Identity, supported arrival, and a truthful public product record

Alpha 0.6 · complete

Open World

Waves 622–771

Free access, living geography, contested truth, newsrooms, and cultural institutions

Alpha 0.5 · complete

Institutions

Waves 472–621

Exchange, due process, population scale, creator packages, and accountable ownership

Alpha 0.4 · complete

Living History

Waves 292–471

Civilization, epoch infrastructure, Chronicles, operations, and accessibility

Alpha 0.3 · complete

Material Life

Waves 150–291

Mobility, careers, deeper households, health, homes, and persistent possessions

Alpha 0.2 · complete

Persistent World

Waves 40–149

World contracts, autonomous residents, multiplayer trust, generations, and family resilience

Alpha 0.1 · complete

First Light

Waves 1–39

The observatory, playable life, city systems, power, enterprise, government, and the underworld

Alpha 1.943 changesVerified feature group
Waves 2702–2801 · Review Ready

Everything code can prepare for external approval is packaged

Alpha 1.9 finishes the remaining machine-preparable scope without claiming human approval. Regional and era review packets now cover scholarship, source maps, community perspective, localization, accessibility, safety, law, material life, health, audiovisual direction, and transition mapping. Candidate source slots are prepared for real citations, localization queues are expanded as source-language placeholders, and evidence runs prove the packets exist while preserving zero self-certified human approvals.

  1. Create the non-human completion program
  2. Keep final review preparation repeat-safe
  3. Prepare regional technical preflight packets
  4. Prepare regional scholarship source-map packets
  5. Prepare regional community perspective packets
  6. Prepare regional language localization packets
  7. Prepare regional accessibility comprehension packets
  8. Prepare regional safety and rights packets
  9. Prepare era source-map packets
  10. Prepare era law and institution packets
  11. Prepare era material-life packets
  12. Prepare era health and safety packets
  13. Prepare era audiovisual-review packets
  14. Prepare era transition-mapping packets
  15. Queue packets for every regional content profile
  16. Queue packets for every validated era package
  17. Create candidate source slots for material life
  18. Create candidate source slots for institutions and law
  19. Create candidate source slots for ordinary life
  20. Create candidate source slots for critical perspectives
  21. Create candidate source slots for regional and community voice
  22. Create candidate source slots for language and terminology
  23. Create candidate source slots for health and disability
  24. Create candidate source slots for visual and audio reference
  25. Preserve candidate slots as unreviewed until real sources are attached
  26. Expand the localization queue across target locales
  27. Keep queued localization values as English source placeholders
  28. Expose review-ready packet totals on the Epoch catalog
  29. Expose candidate source slot totals on the Epoch catalog
  30. Expose localization queue totals on the Epoch catalog
  31. Record machine-closure evidence for regionalization
  32. Record machine-closure evidence for the Epoch SDK
  33. Record machine-closure evidence for external-review packaging
  34. Harden era catalog repeat runs across all active worlds
  35. Keep all twenty-two worlds operational
  36. Keep Test and Private access restricted by contract
  37. Keep every economy isolated
  38. Keep real money, checkout, cash-out, and paid power absent
  39. Keep completed human-review count at zero
  40. Add repeat-safety tests for final packet preparation
  41. Add regression coverage for the closure command
  42. Advance the public record to Alpha 1.9
  43. Reconcile Changelog and Patch Notes through Wave 2801
Alpha 1.860 changesVerified feature group
Waves 2502–2701 · Content Atlas

Every era gains material depth; every region gains a distinct authored foundation

Alpha 1.8 closes the builder-controlled epoch-depth and regionalization gaps without pretending that generated structure is qualified historical or cultural approval. All twenty-three era packages now carry deep, checksummed catalogs across seventeen content domains. All sixty-three regions now carry distinct language, naming, belief, law, status, household, health, ecology, trade, demographic, visual, sound, interface, and starting-state profiles. The content is operational, queryable, repeat-safe, isolated, and visibly human-review gated.

  1. Create the deep-content program
  2. Keep deep content repeat-safe
  3. Create a durable era-catalog registry
  4. Create a durable regional-content-profile registry
  5. Deepen all twenty-three validated era packages
  6. Deepen all sixty-three operational regions
  7. Create ordinary-goods catalogs
  8. Create property-form catalogs
  9. Create era-bounded transport catalogs
  10. Create illness and population-health pressures
  11. Create treatment and care-response catalogs
  12. Create safety-bounded conflict abstractions
  13. Create additional regional careers
  14. Create accountable institution catalogs
  15. Create rights, property, labor, family, mobility, and public-power laws
  16. Create era-bounded technology catalogs
  17. Create disaster and recovery catalogs
  18. Create explicit demographic profiles
  19. Create named regional organizations
  20. Create region-specific opening states
  21. Create material and palette art direction
  22. Create people and ordinary-life art direction
  23. Create built-environment art direction
  24. Create evidence and uncertainty visual language
  25. Create regional ambient sound direction
  26. Create household and work sound direction
  27. Create captioned institution and alert language
  28. Create sacred-sound review boundaries
  29. Create era-specific UI vocabulary
  30. Give UI terms plain-language fallbacks
  31. Create private-use language identifiers within the production schema
  32. Create household, trade, civic, and ceremonial language registers
  33. Create naming policies without fabricating cultural authenticity
  34. Create plural belief and non-observance structures
  35. Create legal domains, due process, appeals, and oppression pressures
  36. Create class, status, mobility, and access structures
  37. Create plural family and chosen-kin household structures
  38. Create health, disability, care, and caregiver representation
  39. Create climate, ecology, restoration, and disaster pressure
  40. Create trade, labor, material life, and anti-extraction rules
  41. Normalize synthetic demographic age bands to one hundred percent
  42. Create per-region population, household, urbanization, migration, and access-need baselines
  43. Create food, water, shelter, care, trust, route, inequality, and ecological opening indicators
  44. Create source-confidence matrices
  45. Keep historical-specificity confidence low until scholarship review
  46. Keep language-authenticity confidence low until translation review
  47. Keep community-acceptance confidence zero until community review
  48. Carry regional variants into every era catalog entry
  49. Add catalog depth to versioned package manifests
  50. Expose catalog totals on the public Epoch catalog
  51. Expose regional depth in every live world observatory
  52. Expose source-confidence status publicly
  53. Preserve Open, Controlled, Test, and Private admission contracts
  54. Keep human review incomplete
  55. Keep every world economy isolated
  56. Keep real money, checkout, cash-out, and paid power absent
  57. Add 939 focused content assertions
  58. Add repeat-safety and public-surface coverage
  59. Advance the public record to Alpha 1.8
  60. Reconcile Changelog and Patch Notes through Wave 2701
Alpha 1.741 changesVerified feature group
Waves 2402–2501 · Living Portfolio

Every declared world becomes a continuously operating simulation

Alpha 1.7 activates the complete twenty-two-world portfolio without collapsing its contracts or economies together. A repeat-safe operations program gives every world an active era, continuous simulation, foundational residents, households, institutions, services, law, environment, culture, markets, archive events, and health evidence. The shared-host runner advances one rotating world per minute, so every world moves while work remains bounded. Each world now opens in its own live observatory; public and controlled Alpha admission remains separate from the resettable Test laboratory and invite-only Private studio.

  1. Create the portfolio operations program
  2. Keep operationalization repeat-safe
  3. Ensure the City One flagship exists in clean installations
  4. Activate all twenty-two world simulations
  5. Preserve nineteen Eternal, one Chronicle, one Test, and one Private contract
  6. Keep all world economies and assets isolated
  7. Give every world continuous simulation mode
  8. Give every world an active primary era
  9. Activate versioned simulation content
  10. Give every region persistent NPC residents
  11. Give every region persistent households
  12. Give every region essential NPC services
  13. Give every region a foundational institution
  14. Give every region a working business and housing baseline
  15. Give every region environmental state
  16. Give every world a continuity organization
  17. Give every world a dignity and no-surprise-loss charter
  18. Create a permanent operational-entry event
  19. Seed world-specific atlas records
  20. Remove Aurelia-specific language from non-Aurelia atlas records
  21. Seed plural culture and public-memory systems
  22. Seed journalism and cultural governance
  23. Seed responsible fictional-currency chance systems
  24. Seed world-specific securities and resource trusts
  25. Scope shipment delivery to its owning world
  26. Scope dividends to securities in the current world
  27. Keep real funds, checkout, cash-out, and paid power absent
  28. Create bounded round-robin world scheduling
  29. Advance one world per minute instead of twenty-two at once
  30. Give every world a persisted simulation tick
  31. Give every world a persisted simulation-health record
  32. Add queryable live observatories for every world
  33. Show operational and registered counts separately
  34. Add contract links beside live-observatory links
  35. Allow character admission only under public or controlled Alpha contracts
  36. Keep Test admission restricted
  37. Keep Private admission invite-only
  38. Preserve incomplete human-review state honestly
  39. Add full-portfolio pulse regression coverage
  40. Update homepage, Guide, Roadmap, Changelog, and Patch Notes to Alpha 1.7
  41. Reconcile the public release record through Wave 2501
Alpha 1.648 changesVerified feature group
Waves 2202–2401 · Complete Horizons

Every declared world receives a real contract and a visible home

Alpha 1.6 completes the master world portfolio. Eleven additional Eternal worlds now cover every later-candidate historical era, speculative future, and distinct variant named in the requirements. The World Hub presents all twenty-two worlds and all four contract types in one place while Aurelia remains the sole live Alpha. Every other world has isolated regions, expansion translations, an era package, validation evidence, and explicit review gates before character admission.

  1. Create the complete-world portfolio program
  2. Keep portfolio creation repeat-safe
  3. Create Prehistoric & Neolithic
  4. Create Late Antiquity & Migration Age
  5. Create Age of Revolutions
  6. Create World Wars & Interwar
  7. Create Postwar & Cold War
  8. Create Post-Collapse Reconstruction
  9. Create Far Future & Posthuman
  10. Create Alternate History Laboratory
  11. Create Mythic Realms
  12. Create Hidden Supernatural World
  13. Create Frontier & Settlement World
  14. Give every new world three distinct regional foundations
  15. Translate City One systems into every new world
  16. Translate Enterprise systems into every new world
  17. Translate Underworld systems into every new world
  18. Translate Dominion systems into every new world
  19. Translate Beyond systems into every new world
  20. Create an isolated versioned world package for each
  21. Create a technically validated era package for each
  22. Create professions, resources, recipes, institutions, technologies, norms, overlap rules, and compatibility findings
  23. Queue eight interface locales per era package
  24. Create scholarship, cultural, and localization assignments
  25. Create regional source and community-review dossiers
  26. Run zero-player validation
  27. Run few-player validation
  28. Run synthetic-population validation
  29. Run decade endurance validation
  30. Run capacity-boundary validation
  31. Run century endurance validation
  32. Run regional-capacity stress validation
  33. Preserve exactly one active world
  34. Keep all new character admissions closed
  35. Keep every world economy isolated
  36. Keep real funds and paid power absent
  37. Turn /world into the complete World Hub
  38. Show every world contract on /world
  39. Show Eternal, Chronicle, Test, and Private totals
  40. Keep Aurelia Observatory on the same hub
  41. Fix contract filtering to use authoritative world type
  42. Remove the public completion route
  43. Remove completion from global navigation
  44. Remove completion from the footer
  45. Remove public completion calls to action
  46. Retain restricted operational evidence for administrators
  47. Advance the public record to Alpha 1.6
  48. Reconcile Changelog and Patch Notes through Wave 2401
Alpha 1.544 changesVerified feature group
Waves 2102–2201 · Owner Ready

Every remaining external dependency receives an executable handoff

Alpha 1.5 reaches one hundred percent of builder-controlled work. Eight versioned handoff packages now turn every honest remainder into an explicit sequence for qualified reviewers, translators, community participants, invited players, operators, and the later VPS. Each packet records prerequisites, instructions, acceptance evidence, prohibited claims, ownership, preparation time, and a checksum. The public completion ledger now distinguishes builder readiness from shared-host completeness and the entire human-and-infrastructure vision.

  1. Define builder-controlled readiness separately from full-vision completion
  2. Create a durable handoff-package registry
  3. Create eight checksummed handoff packages
  4. Prepare the qualified historical and cultural review packet
  5. Prepare reviewer qualification and conflict-of-interest requirements
  6. Prepare the human localization workbench
  7. Preserve eight locale queues without calling placeholders translations
  8. Prepare regional scholarship and citation-map instructions
  9. Require ordinary-life, institutional, critical, and regional-voice sources
  10. Require uncertainty, dissent, omission, and revision records
  11. Prepare a deliberately varied closed-Alpha cohort protocol
  12. Cover onboarding, ordinary life, economy, social play, governance, eras, safety, and recovery
  13. Require consent, participant matrices, session notes, severity, and retesting
  14. Prepare world-specific admission packets for every closed world
  15. Require technical, human, cohort, capacity, localization, and rollback evidence before opening
  16. Prepare the flagship Chronicle acceptance program
  17. Require independent review of both adjacent transitions
  18. Require player comprehension and pacing evidence
  19. Prepare the thirty-day production observation program
  20. Prepare recurring restore, RTO, and RPO evidence requirements
  21. Prepare disposable-database restoration acceptance
  22. Prepare the VPS and multi-node acceptance harness
  23. Preserve APP_KEY and one-authoritative-database rules
  24. Require Redis worker restart evidence
  25. Require authenticated socket authorization evidence
  26. Require polling fallback
  27. Require replica lag, failover, load, PITR, and rollback reports
  28. Create a restricted final handoff console
  29. Show prerequisites, instructions, acceptance evidence, blocked claims, and next actor
  30. Add a complete JSON handoff export
  31. Keep the handoff admin-only
  32. Add builder readiness to the public completion ledger
  33. Reach 100% builder-controlled readiness
  34. Keep shared-host and full-vision scores independent
  35. Keep qualified review incomplete until people perform it
  36. Keep real-player evidence incomplete until invited players participate
  37. Keep VPS evidence incomplete until the upgraded host exists
  38. Keep every staged world closed
  39. Keep the product free-first
  40. Keep real USD, checkout, cash-out, and paid power absent
  41. Add repeat-safe handoff preparation
  42. Add handoff ownership and export tests
  43. Advance the public record to Alpha 1.5
  44. Reconcile Changelog and Patch Notes through Wave 2201
Alpha 1.489 changesVerified feature group
Waves 1902–2101 · Closure Evidence

The remaining host-compatible gaps become reproducible evidence

Alpha 1.4 completes the strongest remaining technical work that can be proven without inventing players, translators, scholars, or a multi-node host. Test and Private contracts now exist as real closed worlds alongside the Eternal and Chronicle portfolio. Every staged region receives an implementation-ready dossier and three explicit human-review assignments. Chronicle transitions survive baseline, rights-floor, occupancy, archive, rollback, and catastrophe stress across up to seventy-five synthetic years and 250,000 households. Century-scale civilization continuity, billion-resident aggregate representation, accessibility journeys, specialization probes, contract lifecycle checks, and isolated backup extraction all enter durable evidence ledgers.

  1. Create completion methodology v3
  2. Separate closure evidence from human acceptance
  3. Create durable requirement-evidence runs
  4. Give every evidence run a stable key
  5. Store named checks, scale, evidence, duration, checksum, and completion time
  6. Keep failed probes visible instead of silently counting them
  7. Create six account and accessibility journey probes
  8. Verify the complete character-to-life route contract
  9. Verify keyboard focus and skip navigation
  10. Verify reduced-motion support
  11. Verify high-contrast and interface scaling support
  12. Verify polite screen-reader live regions
  13. Verify privacy, consent, support, and archive routes
  14. Create four five-year City One continuity probes
  15. Model fifty thousand households without production mutation
  16. Verify treasury continuity
  17. Verify housing and household safety routes
  18. Verify education, work, and mobility continuity
  19. Verify institutions, markets, voting, and information correction
  20. Create five expansion specialization probes
  21. Verify City One specialization independently
  22. Verify Enterprise specialization independently
  23. Verify Underworld specialization independently
  24. Verify Dominion specialization independently
  25. Verify Beyond specialization independently
  26. Create four World Foundry contract lifecycle probes
  27. Verify Eternal contract staging
  28. Verify Chronicle contract staging
  29. Verify Test contract staging
  30. Verify Private contract staging
  31. Create the Systems Validation Laboratory
  32. Stage a real resettable Test world
  33. Create the Invited World Studio
  34. Stage a real invite-only Private world
  35. Keep both support worlds closed
  36. Prohibit production asset transfer
  37. Give each support world an isolated package and profile
  38. Translate all five expansion contracts into each support world
  39. Represent all four world contract types in production
  40. Create century-zero-player validation
  41. Simulate 36,500 unattended world days
  42. Create regional-capacity stress validation
  43. Represent one hundred thousand synthetic players through bounded aggregation
  44. Run deep endurance evidence across every closed staged world
  45. Create ten-million-resident aggregate civilization evidence
  46. Create one-hundred-million-resident aggregate civilization evidence
  47. Create one-billion-resident boundary evidence
  48. Preserve the synthetic-not-live-concurrency distinction
  49. Record six phase benchmarks for every aggregate scale run
  50. Keep production residents unchanged during scale evidence
  51. Expand Chronicle from two baseline rehearsals to six stress rehearsals
  52. Add rights-floor and occupancy stress
  53. Add archive rollback catastrophe stress
  54. Model forty-year transition pressure
  55. Model seventy-five-year catastrophe recovery
  56. Represent up to 250,000 synthetic households per transition
  57. Verify non-regressive rights floors
  58. Block forced displacement in transition projections
  59. Verify archive recovery
  60. Verify catastrophic rollback boundaries
  61. Keep human and localization gates false
  62. Create regional readiness dossiers
  63. Prepare material-life coverage requirements
  64. Prepare plural-institution requirements
  65. Prepare mobility and exchange requirements
  66. Prepare rights, coercion, and safety requirements
  67. Prepare human language workflows
  68. Require citation maps and uncertainty notes
  69. Create region-level scholarship assignments
  70. Create region-level community-review assignments
  71. Create region-level language assignments
  72. Expand the qualified review queue without self-certifying completion
  73. Create automated isolated artifact restore verification
  74. Match application and database checksums
  75. Verify environment secrets are excluded
  76. Extract the application archive into an isolated temporary target
  77. Parse the restored dependency manifest
  78. Verify SQL schema statements are readable
  79. Remove the temporary restore target after evidence capture
  80. Never overwrite production data during a restore rehearsal
  81. Recognize isolated artifact restoration as a shared-host outcome
  82. Keep disposable-database import and point-in-time recovery for the upgraded host
  83. Raise shared-host completion only from passing evidence
  84. Keep human scholarship and real-player testing visibly unresolved
  85. Keep every staged world inaccessible to character creation
  86. Keep the entire system free
  87. Keep checkout, cash-out, real USD, and paid power absent
  88. Advance the public record to Alpha 1.4
  89. Reconcile Changelog and Patch Notes through Wave 2101
Alpha 1.3136 changesVerified feature group
Waves 1702–1901 · Connected Epochs

The portfolio gains complete era structure and rehearsed continuity

The largest remaining host-compatible gaps move from intention into evidence. Twelve technically validated era packages now span Aurelia and the staged portfolio. Every new package contains professions, resources, transformations, institutions, technologies, norms, overlap policy, compatibility findings, multilingual review queues, and explicit production boundaries. The Long Chronicle rehearses both future transitions across twenty-five synthetic years without satisfying its human-review gates. Infrastructure completion now measures delivered outcomes, recognizing the shared-host queue, polling, capacity, backup, observability, and release systems already operating while preserving a clean VPS scale path.

  1. Create completion methodology v2
  2. Measure infrastructure outcomes instead of vendor-specific technology names
  3. Keep full-vision and shared-host scores separate
  4. Preserve historical checkpoints under their original methodology
  5. Create an infrastructure-capability registry
  6. Record eight infrastructure outcomes
  7. Recognize the bounded minute runner as continuous world work
  8. Recognize short-lived database workers as durable queue execution
  9. Recognize private authenticated polling as near-live delivery
  10. Recognize capacity gates as host protection
  11. Recognize verified application and database archives as recovery capability
  12. Recognize public and restricted ledgers as operational observability
  13. Recognize backup-first maintenance releases as release safety
  14. Preserve a documented horizontal-scale path
  15. Keep Redis optional until scale evidence justifies it
  16. Keep WebSockets optional while polling satisfies the product outcome
  17. Keep resident workers optional while bounded workers satisfy the product outcome
  18. Preserve SQL operational evidence after any future transport migration
  19. Keep multi-node concurrency as an unproven future claim
  20. Keep failover and replication as future evidence
  21. Create epoch-transition rehearsal records
  22. Give transition rehearsals deterministic checksums
  23. Preserve transition before-state
  24. Preserve transition after-state
  25. Model twenty-five transition years
  26. Model twenty-five thousand synthetic households
  27. Verify lineage continuity
  28. Verify archive immutability
  29. Verify zero currency export
  30. Verify restricted-item isolation
  31. Verify occupancy protection
  32. Require supervised profession recognition
  33. Apply the stronger rights floor during overlap
  34. Verify rollback snapshots
  35. Keep qualified review false until a human records it
  36. Keep localization review false until a human records it
  37. Advance technically rehearsed transition readiness to 88%
  38. Prevent technical rehearsal from reaching production-ready 100%
  39. Create decade-zero-player world validation
  40. Simulate 3,650 unattended world days
  41. Create five-thousand-player capacity-boundary validation
  42. Preserve non-destructive validation state
  43. Run both endurance scenarios across eight staged worlds
  44. Keep the original Chronicle launch scenarios failed
  45. Allow technical Chronicle endurance validation at the 80% transition threshold
  46. Keep public admission dependent on 100%-ready transitions
  47. Ensure Aurelia retains two playable isolated era packages
  48. Create the Networked Present package
  49. Create the Industrial Century package
  50. Create Connected Crowns
  51. Create Classical Exchange Worlds
  52. Create Sail and Exchange
  53. Create First Cities and River States
  54. Create Independent Beyond Commonwealths
  55. Create Chronicle I: First Cities
  56. Create Chronicle II: Connected Worlds
  57. Create Chronicle III: Beyond Commonwealth
  58. Reach twelve technically validated era packages
  59. Give every new package eight professions
  60. Give every new package six material resources
  61. Give every new package five transformation recipes
  62. Give every new package four accountable institutions
  63. Give every new package six technology paths
  64. Give every new package four plural social norms
  65. Give every new package five transition-overlap rules
  66. Give every new package three open compatibility findings
  67. Create Provision Steward roles
  68. Create Maker and Repairer roles
  69. Create Carekeeper roles
  70. Create Route Keeper roles
  71. Create Record Witness roles
  72. Create Commons Steward roles
  73. Create Builder roles
  74. Create Mediator roles
  75. Represent food, construction, energy, tools, records, and care materials
  76. Create preserved-provision transformations
  77. Create repair-kit transformations
  78. Create safe-household-system transformations
  79. Create public-record transformations
  80. Create community-care-cache transformations
  81. Create provision councils
  82. Create works assemblies
  83. Create witness and archive circles
  84. Create care compacts
  85. Create water and sanitation practices
  86. Create measured storage
  87. Create route and measure standards
  88. Create public record practices
  89. Create energy stewardship paths
  90. Keep allocation advisers optional and retireable
  91. Protect minimums before prestige
  92. Require visible records for power
  93. Require consent in care
  94. Preserve plural memory
  95. Block cross-era currency conversion
  96. Protect occupancy across property transitions
  97. Supervise professional recognition
  98. Apply common rights floors
  99. Preserve health history without unsafe equivalence
  100. Label technical packages as non-production foundations
  101. Keep real-money use false
  102. Keep cross-world asset transfer false
  103. Create 240 multilingual review assignments
  104. Queue Spanish, French, German, Portuguese, Japanese, Arabic, Hindi, and Chinese coverage
  105. Store source-language placeholders without calling them translations
  106. Keep every queued localization unreviewed
  107. Create thirty qualified human-review assignments
  108. Separate scholarship review from cultural-sensitivity review
  109. Separate localization review from scholarship
  110. Require a named reviewer
  111. Require relevant qualification or lived expertise
  112. Require substantive findings and corrections
  113. Require explicit review limitations
  114. Require human attestation
  115. Preserve the account recording review evidence
  116. Never open a world automatically after a review
  117. Mark an era package human-reviewed only after all three assignments complete
  118. Keep world activation as a separate gate
  119. Create a restricted human-review program interface
  120. Show queued and completed review counts
  121. Expose assignment acceptance requirements
  122. Link World Foundry to the review program
  123. Make completion evidence render strings and numbers safely
  124. Add repeat-safe completion advancement
  125. Prevent duplicate packages, localization assignments, review tasks, rehearsals, and endurance runs
  126. Add complete portfolio-structure regression tests
  127. Add Chronicle technical-versus-human gate tests
  128. Add infrastructure-equivalence tests
  129. Add review-attestation tests
  130. Keep staged worlds inactive
  131. Keep inactive regions out of character creation
  132. Keep the Alpha free
  133. Keep checkout and cash-out absent
  134. Keep paid gameplay power absent
  135. Advance the public record to Alpha 1.3
  136. Reconcile Changelog and Patch Notes through Wave 1901
Alpha 1.286 changesVerified feature group
Waves 1602–1701 · Measured Horizons

Completion becomes evidence, and the world portfolio becomes real

The original requirements now have a durable, versioned completion program instead of a floating estimate. Validated Foundry drafts can become real but closed worlds, undergo three declared simulation scenarios, receive named human-review evidence, and open for Alpha admission only after every gate passes. Eight initial portfolio foundations now exist as isolated staged worlds—including a deliberately blocked multi-era Chronicle—without presenting technical scaffolding as completed historical authorship.

  1. Create twelve authoritative requirement milestones
  2. Separate shared-host completion from the full original vision
  3. Weight every requirement area explicitly
  4. Store measured percentages independently by area
  5. Preserve evidence and blockers as structured data
  6. Create immutable completion snapshots
  7. Version the scoring methodology
  8. Publish a public completion ledger
  9. Show completion history over time
  10. Expose an administrator checkpoint action
  11. Add completion to canonical navigation
  12. Add completion to the footer record
  13. Drive homepage completion figures from measured evidence
  14. Remove the unsupported static 100% homepage claim
  15. Create a validated-draft promotion service
  16. Create a real world from a ready Foundry draft
  17. Keep promoted worlds inactive by default
  18. Set promoted world access to closed
  19. Set promoted simulation to staged validation
  20. Generate a permanent world profile and contract
  21. Generate the first staged epoch
  22. Generate regional records from Foundry configuration
  23. Generate accessible arrival-center location nodes
  24. Generate an isolated versioned content package
  25. Generate content definitions with provenance
  26. Preserve a checksummed launch manifest
  27. Declare real-money transfer false
  28. Declare production-asset transfer false
  29. Require zero-player simulation evidence
  30. Require few-player simulation evidence
  31. Require synthetic-population simulation evidence
  32. Store every validation run with before-and-after state
  33. Store validation checks and deterministic checksums
  34. Model 365 zero-player days
  35. Model 180 days with twelve synthetic players
  36. Model 90 days with one thousand synthetic players
  37. Keep validation non-destructive to authoritative world state
  38. Test population continuity
  39. Test treasury solvency
  40. Test regional depth
  41. Test package presence
  42. Test employment viability
  43. Test political stability
  44. Block Chronicles without ready transitions
  45. Create a qualified-human-review attestation flow
  46. Preserve reviewer identity, qualification, notes, recorder, and time
  47. Never let code self-certify human scholarship
  48. Require all validation scenarios before Alpha access
  49. Require human review before Alpha access
  50. Open only reviewed and validated worlds
  51. Keep closed worlds out of character creation
  52. Keep the server-side inactive-world admission rejection
  53. Label inactive directory entries as closed staged validation
  54. Create the Modern World foundation
  55. Create the Age of Industry foundation
  56. Create the Age of Crowns foundation
  57. Create the Classical Worlds foundation
  58. Create the Age of Sail and Exchange foundation
  59. Create the First Civilizations foundation
  60. Create the independent Beyond Commonwealth foundation
  61. Create The Long Chronicle foundation
  62. Give each portfolio world three full-depth technical regions
  63. Give every region explicit localization and rights-review obligations
  64. Translate all five expansion pillars into each staged world
  65. Keep all eight foundations isolated and closed
  66. Create three explicit Chronicle era foundations
  67. Create two explicit Chronicle transition plans
  68. Preserve lineage, memory, public history, and archives across planned transitions
  69. Block currency, technology advantage, and restricted-item transfer
  70. Keep Chronicle transition readiness below launch threshold
  71. Make repeated portfolio initialization idempotent
  72. Prevent duplicate failed validation evidence on repeat runs
  73. Add operator commands for portfolio initialization
  74. Add operator commands for completion capture
  75. Document what counts toward completion
  76. Document what can never be auto-completed
  77. Add feature tests for completion scope separation
  78. Add feature tests for snapshot persistence
  79. Add feature tests for all eight staged worlds
  80. Add feature tests for Chronicle transition blocking
  81. Add feature tests for review-gated activation
  82. Add feature tests for active-world-only character admission
  83. Advance the public record to Alpha 1.2
  84. Reconcile Changelog and Patch Notes through Wave 1701
  85. Keep the entire current system free
  86. Keep real USD, checkout, cash-out, and paid gameplay power absent
Alpha 1.197 changesVerified feature group
Waves 1502–1601 · Shared Continuum

The shared-host Alpha becomes a self-operating service

The production operating layer now runs end to end within shared-host constraints. A minute scheduler orchestrates bounded simulation work, short-lived queue workers, health scans, trade expiry, presence aging, evidence retention, verified backups, capacity enforcement, and private near-live updates without requiring resident daemons. Public and restricted evidence surfaces make that runtime visible, while a dedicated runbook and VPS migration playbook preserve the exact upgrade path.

  1. Create a minute-keyed shared-host runtime ledger
  2. Make runtime cycles idempotent by default
  3. Allow intentional forced verification cycles
  4. Record stage durations and outcomes
  5. Recover stale operational job locks
  6. Bound each operational processing batch
  7. Cap operational backlog before overload
  8. Retry failed operational work with delayed backoff
  9. Stop retrying terminal failures after three attempts
  10. Run short-lived database queue workers every minute
  11. Limit queue work by job count and wall time
  12. Prevent overlapping runner and worker cycles
  13. Enqueue world pulses on a fifteen-minute cadence
  14. Enqueue service health on a five-minute cadence
  15. Expire protected trades automatically
  16. Refund trade escrow exactly once
  17. Age player presence from online to away to offline
  18. Retain completed evidence for declared periods
  19. Add automatic accessibility audit scheduling
  20. Create daily application and database backups
  21. Exclude environment secrets from archives
  22. Use consistent database snapshots
  23. Open and verify every application archive
  24. Reject empty database backups
  25. Record SHA-256 checksums and byte counts
  26. Rotate only backups inside the protected backup root
  27. Support an optional mounted off-host backup destination
  28. Expose manual dry-run and verified backup actions
  29. Create a permanent backup manifest ledger
  30. Add runner freshness to service health
  31. Add backup freshness to service health
  32. Add terminal job failures to service health
  33. Treat the current runner as healthy during its own first scan
  34. Expose shared-host runtime evidence publicly
  35. Expose detailed runtime ledgers to administrators
  36. Expose backup manifests to administrators
  37. Expose capacity events to administrators
  38. Create world character admission limits
  39. Respect both host and world-declared capacity
  40. Preserve rejected admissions as capacity evidence
  41. Create an online-player soft boundary
  42. Create a hard operational backlog boundary
  43. Keep capacity boundaries configurable
  44. Add an authenticated private live-poll endpoint
  45. Refresh presence from active authenticated play
  46. Return unread notification snapshots privately
  47. Return server and world time snapshots
  48. Return capacity evidence privately
  49. Pause polling in background tabs
  50. Degrade quietly during connectivity loss
  51. Update unread badges without navigation
  52. Show shared-host live state in the canonical header
  53. Throttle private polling requests
  54. Publish the shared-host operating contract
  55. Document exact cron and environment requirements
  56. Document operator commands and evidence surfaces
  57. Document restore drills and incident handling
  58. Document safe shared-host release procedure
  59. Document the boundary between Alpha operation and VPS infrastructure
  60. Create a one-place VPS migration playbook
  61. Preserve free-first rules through infrastructure migration
  62. Define evidence-based VPS readiness triggers
  63. Define the target VPS service topology
  64. Define secret, key, and encrypted-data continuity
  65. Define immutable release deployment
  66. Define Redis queue, cache, and session migration
  67. Preserve SQL operational ledgers after Redis adoption
  68. Define managed worker process groups
  69. Define authenticated WebSocket rollout
  70. Retain polling as a real-time fallback
  71. Define off-host encrypted backups and restore drills
  72. Define staging acceptance gates
  73. Define DNS and certificate cutover
  74. Define one-authoritative-database rules
  75. Define rollback with player-write reconciliation
  76. Define post-cutover observation and scale-out
  77. Add shared-host runtime migration tables
  78. Add backup manifest migration tables
  79. Add capacity event migration tables
  80. Add shared-host runtime feature tests
  81. Test minute idempotency and stage bounds
  82. Test abandoned-lock recovery
  83. Test exactly-once escrow refunds
  84. Test socket-free presence aging
  85. Test private polling and notification snapshots
  86. Test character capacity refusal evidence
  87. Test backup dry-run evidence
  88. Test scheduler and admin operations surfaces
  89. Run a real local verified application backup
  90. Run a real local verified database backup
  91. Keep real USD and funds outside the game
  92. Keep Aurels explicitly fictional
  93. Keep checkout and cash-out absent
  94. Keep paid gameplay power absent
  95. Advance the public record to Alpha 1.1
  96. Reconcile Changelog and Patch Notes through Wave 1601
  97. Prepare the shared-host Alpha for verified live deployment
Alpha 1.0101 changesVerified feature group
Waves 1202–1501 · Shared Horizon

The complete shared-host product contract

The final shared-host completion program closes the remaining public, creator, continuity, responsible-play, discovery, and operating requirements. World Foundry can compose isolated world drafts from declared contracts, validate regional and expansion depth, version content, sign artifacts, plan branches, and rehearse retention. Players gain inactive-life delegation and bounded fictional games of chance. The public product now explains every expansion, epoch, world promise, safety boundary, accessibility commitment, support path, and free-first rule without implying VPS-scale infrastructure or real-money play.

  1. Create a consent-scoped public interest registry
  2. Encrypt contact addresses at rest
  3. Hash contact addresses for repeat-safe matching
  4. Keep interest registration separate from entitlement
  5. Create durable support requests with public references
  6. Separate support categories for access, safety, privacy, and technical help
  7. Never request account secrets in support evidence
  8. Publish City One as a complete product pillar
  9. Publish Enterprise depth, connections, and long-term outcomes
  10. Publish Underworld depth without teaching real wrongdoing
  11. Publish Dominion governance and accountability promises
  12. Publish Beyond civilization and settlement promises
  13. Publish the Epoch catalog independently from login
  14. Publish world contracts before character entry
  15. Publish founder and community information
  16. Publish a comprehensive public FAQ
  17. Publish legal and free-first terms
  18. Publish a privacy and data-portability statement
  19. Publish an accessibility commitment
  20. Publish community conduct expectations
  21. Publish safety and consent boundaries
  22. Link every public information surface from stable navigation
  23. Create Eternal, Chronicle, Test, and Private world templates
  24. Create isolated world drafts with stable public identifiers
  25. Declare lifecycle, mortality, progression, access, and risk before launch
  26. Create region-depth configuration with language and rights context
  27. Require authored government, currency, and mobility context
  28. Create versioned world-content entries
  29. Create City One regional translations
  30. Create Enterprise regional translations
  31. Create Underworld regional translations
  32. Create Dominion regional translations
  33. Create Beyond regional translations
  34. Preserve safety review and confidence on every content entry
  35. Preserve transition mappings between compatible institutions
  36. Validate world contract completeness
  37. Validate required full-depth regions
  38. Validate five core system translations
  39. Validate cross-world asset isolation
  40. Validate content safety review
  41. Calculate evidence-backed Foundry readiness
  42. Create checksummed content package exports
  43. Create signed content artifacts
  44. Create package-to-package diffs
  45. Preserve human-readable artifact changes
  46. Create snapshot-bound world branch plans
  47. Keep source worlds active during branch planning
  48. Block money, office, and property transfer across branches
  49. Create dry-run retention reports
  50. Protect historical ledgers from retention deletion
  51. Expire only eligible export artifacts
  52. Create inactive-player continuity delegation
  53. Let players declare an ordinary absence state
  54. Delegate home, business, care, contracts, travel, and communications independently
  55. Require warnings and preparation for hostile high-impact actions
  56. Prevent continuity delegation from exporting production authority
  57. Create three bounded fictional games of chance
  58. Resolve every chance result on the server
  59. Give every chance play an idempotency key
  60. Return the original result for repeated submissions
  61. Publish minimum and maximum fictional stakes
  62. Publish bounded house-edge evidence
  63. Create daily fictional stake ceilings
  64. Create daily fictional loss ceilings
  65. Create voluntary cool-off periods
  66. Create voluntary self-exclusion periods
  67. Block new play while a pause is active
  68. Create immutable chance wager references
  69. Preserve seed commitments and resolution evidence
  70. State real-money false on every wager
  71. State cash-out false on every wager
  72. Remove dollar symbols from in-world financial interfaces
  73. Name Aurels as fictional world currency
  74. Preserve free access with no checkout
  75. Preserve zero paid gameplay power
  76. Add lifecycle filtering to the public world directory
  77. Add epoch filtering to the public world directory
  78. Add language filtering to the public world directory
  79. Add access-model filtering to the public world directory
  80. Add mortality-contract filtering to the public world directory
  81. Show an honest empty state for unmatched world promises
  82. Expose language and mortality in every world card
  83. Add responsive World Foundry presentation
  84. Add responsive responsible-play presentation
  85. Add responsive directory-filter presentation
  86. Test public legal, safety, support, and access surfaces
  87. Test encrypted noncommercial interest registration
  88. Test Foundry authorization and four templates
  89. Test full draft readiness from real evidence
  90. Test signed export and diff artifacts
  91. Test branch separation guarantees
  92. Test retention history protection
  93. Test continuity delegation boundaries
  94. Test responsible chance idempotency
  95. Test fictional-currency and no-cash-out evidence
  96. Test voluntary play pauses
  97. Test world contract filters
  98. Reconcile Changelog and Patch Notes through Wave 1501
  99. Advance the public release record to Alpha 1.0
  100. Document shared-host completion separately from VPS infrastructure
  101. Preserve future authored content as an ongoing editorial program rather than a false completion claim
Alpha 0.11110 changesVerified feature group
Waves 1112–1201 · Household Years

A lineage gains seasons, livelihoods, bonds, and related hearths

Lineages now continue through deterministic household years rather than isolated button presses. Members practice bounded vocations, record consent-based bonds, establish protected household branches, face four seasonal conditions, age across completed year boundaries, leave material provenance, reach agency milestones, and receive checksummed annual reviews without touching production-world funds.

  1. Create a persistent lineage-season registry
  2. Bind every season to one owned lineage
  3. Number seasons independently from world time
  4. Group four seasons into one household year
  5. Declare a seasonal climate condition
  6. Declare a material household pressure
  7. Declare an ordinary household opportunity
  8. Preserve structured seasonal effects
  9. Preserve a household snapshot after each season
  10. Generate a deterministic seasonal checksum
  11. Prevent duplicate lineage-season records
  12. Create a persistent member-vocation registry
  13. Bind one active vocation to one member
  14. Keep vocation identity revisable
  15. Require a member to be at least fourteen
  16. Create the Carekeeper vocation
  17. Create the Maker and repairer vocation
  18. Create the Commons steward vocation
  19. Create the Chronicler and teacher vocation
  20. Create the Provisioner vocation
  21. Create the Mediator vocation
  22. Derive aptitude from existing member capabilities
  23. Track mastery independently from aptitude
  24. Advance mastery through completed seasons
  25. Preserve vocation contributions as structured evidence
  26. Keep vocation output isolated from production work
  27. Create persistent lineage bonds
  28. Require two different active lineage members
  29. Canonicalize member ordering for repeat safety
  30. Represent partnerships with an adult gate
  31. Represent siblinghood without biological privilege
  32. Represent mentorship as a revisable relationship
  33. Represent household pacts
  34. Preserve explicit bond agreements
  35. Track closeness independently
  36. Track strain independently
  37. Let shared seasons deepen active bonds
  38. Create persistent household branches
  39. Give each branch a public UUID
  40. Require an active adult branch leader
  41. Prevent one member from leading duplicate branches
  42. Name related hearths independently
  43. Preserve the founding generation
  44. Preserve a structured household charter
  45. Preserve the founding season
  46. Allocate bounded common reserves
  47. Protect a ten-unit lineage reserve floor
  48. Keep branch assets isolated from production property
  49. Create branch membership records
  50. Designate the founding branch steward
  51. Create a permanent lineage resource ledger
  52. Attribute resource entries to members when applicable
  53. Preserve season, resource, delta, and resulting balance
  54. Preserve a human-readable material reason
  55. Record branch allocations as negative common entries
  56. Record each seasonal reserve change
  57. Attach production-isolation evidence to every entry
  58. Create persistent lineage milestones
  59. Record household-branch founding as a milestone
  60. Record coming of age as an agency milestone
  61. Avoid assigning permanent class at adulthood
  62. Avoid assigning automatic inheritance at adulthood
  63. Preserve milestone significance and evidence
  64. Create persistent household-year reviews
  65. Score material resilience
  66. Score care continuity
  67. Score household belonging
  68. Score practiced capability
  69. Score lineage continuity
  70. Preserve annual highlights
  71. Preserve material and care pressures
  72. Publish bounded recommendations
  73. Generate deterministic review checksums
  74. Create persistent household-year runs
  75. Give every run a public UUID
  76. Give every run an idempotency key
  77. Return the original run for a repeated key
  78. Generate a deterministic run seed
  79. Preserve before and after household state
  80. Resolve exactly four seasons per run
  81. Advance member age only across completed year boundaries
  82. Advance vocation mastery season by season
  83. Advance bond closeness season by season
  84. Calculate adult labor and dependent care load
  85. Apply bounded pressure costs
  86. Apply bounded opportunity gains
  87. Bound reserves and dwelling integrity
  88. Bound member wellbeing
  89. Warn when common reserves cross the protection floor
  90. Preserve the complete run checksum
  91. Keep production export false in every run snapshot
  92. Enforce ownership on every new mutation
  93. Reject members from another lineage
  94. Add four new authenticated Lineage routes
  95. Expose Household Years in Epochs
  96. Expose vocation assignment controls
  97. Expose bond and agreement controls
  98. Expose household-branch controls
  99. Expose one-year resolution controls
  100. Expose vocation, bond, and branch ledgers
  101. Expose the resolved-season timeline
  102. Expose annual review scorecards
  103. Expose life milestones
  104. Add responsive Household Years presentation
  105. Test vocation, bond, branch, year, age, provenance, ownership, isolation, and interface contracts
  106. Update the homepage to 1201 documented waves
  107. Update the Player Guide for seasonal lineages
  108. Update the Roadmap around Alpha 0.11
  109. Reconcile Changelog and Patch Notes
  110. Preserve free access and zero paid gameplay power
Alpha 0.10105 changesVerified feature group
Waves 1022–1111 · Lineages

A completed life can become a living lineage

Long Lives now continue across generations. Players can found a private lineage from a completed era archive, welcome descendants or chosen kin, mentor and care for family members, build shared resources, repair conflict, designate an adult successor, and preserve a checksummed transition into the next generation without exporting anything into the production economy.

  1. Create a persistent era-lineage registry
  2. Require a completed Long Life before lineage founding
  3. Require a private checksummed campaign archive
  4. Prevent one campaign from founding duplicate lineages
  5. Bind every lineage to its originating campaign
  6. Bind every lineage to its owning character
  7. Give every lineage a public UUID
  8. Name lineages independently from campaigns
  9. Preserve the originating era package
  10. Preserve the originating place and household
  11. Carry campaign state into bounded common assets
  12. Keep lineage assets isolated from production balances
  13. Record production export as false
  14. Create a persistent lineage-member registry
  15. Create the completed-life protagonist as founder
  16. Carry household cast into the lineage
  17. Preserve each member relationship
  18. Preserve each member role
  19. Preserve each member age
  20. Track member generation explicitly
  21. Track member wellbeing independently
  22. Track member trust independently
  23. Track member capabilities as structured evidence
  24. Distinguish active, elder, and departed membership
  25. Designate one current steward
  26. Represent biological children without privileging inheritance
  27. Represent adopted children equally
  28. Represent apprentices as legitimate continuity paths
  29. Represent chosen kin as legitimate continuity paths
  30. Create persistent lineage commitments
  31. Seed care as a founding commitment
  32. Seed knowledge continuity as a founding commitment
  33. Assign responsible members without erasing shared duty
  34. Track commitment progress from resolved action evidence
  35. Create persistent lineage conflicts
  36. Seed one continuity conflict at founding
  37. Publish conflict stakes and repair requirements
  38. Track open and reconciled conflict states
  39. Require reconciliation before generation transition
  40. Create five server-authoritative seasonal actions
  41. Mentor another lineage member
  42. Care for another lineage member
  43. Build shared lineage reserves
  44. Reconcile an open conflict
  45. Prepare a commitment for continuity
  46. Require actors to belong to the lineage
  47. Require targets to belong to the lineage
  48. Reject cross-lineage action targets
  49. Give every action an idempotency key
  50. Return prior evidence for repeated keys
  51. Preserve action before-state
  52. Preserve action after-state
  53. Preserve actor and target identities
  54. Advance exactly one season per resolved action
  55. Advance ages after every four seasons
  56. Bound wellbeing, trust, and capabilities
  57. Preserve a permanent lineage action ledger
  58. Create a permanent lineage event stream
  59. Record founding in the lineage chronicle
  60. Record member welcomes in the chronicle
  61. Record seasonal work in the chronicle
  62. Record conflict repair in the chronicle
  63. Record succession planning in the chronicle
  64. Record generation transitions in the chronicle
  65. Welcome new dependents without treating people as assets
  66. Create persistent succession plans
  67. Require successor membership in the same lineage
  68. Require a successor to be at least sixteen
  69. Prevent the current steward from succeeding themselves
  70. Preserve designation rationale
  71. Allow a plan to be revised before transition
  72. Require at least five evidenced seasonal actions
  73. Require all conflicts to be reconciled
  74. Create persistent generation transitions
  75. Move the prior steward into an elder role
  76. Promote the designated successor to steward
  77. Increment the lineage generation atomically
  78. Preserve a continuity snapshot
  79. Generate a deterministic transition checksum
  80. Create persistent generation reports
  81. Score care continuity
  82. Score intermember trust
  83. Score shared resilience
  84. Score knowledge continuity
  85. Preserve report strengths and pressures
  86. Bind reports to their exact transition
  87. Keep prior-generation evidence readable
  88. Expose lineage founding in Epochs
  89. Expose lineage cast and generations
  90. Expose commitments with progress meters
  91. Expose conflicts and repair controls
  92. Expose all five seasonal action controls
  93. Expose member-welcome controls
  94. Expose succession designation controls
  95. Expose gated generation-transition controls
  96. Expose generation reports and transition history
  97. Expose the complete lineage event stream
  98. Keep all lineage surfaces authenticated
  99. Enforce lineage ownership on every mutation
  100. Test founding, kinship, action, succession, transition, isolation, and interface contracts
  101. Update the homepage to 1111 documented waves
  102. Update the Player Guide for multigeneration era lives
  103. Update the Roadmap around Alpha 0.10
  104. Reconcile Changelog and Patch Notes
  105. Preserve free access and zero paid gameplay power
Alpha 0.9142 changesVerified feature group
Waves 932–1021 · Long Lives

An era becomes a household, a place, and a remembered life

Deep Time expands beyond short systems rehearsals into sustained four-chapter lives. Players inhabit authored places, join era-specific households, face material and civic dilemmas, preserve permanent outcomes in private archives, compare lives across eras, and produce human-reviewed promotion evidence without mutating production history.

  1. Create a persistent era-place registry
  2. Bind every era place to one validated package
  3. Give places stable package-local keys
  4. Distinguish wards, commons, ports, habitats, stations, and settlements
  5. Describe material place conditions
  6. Track represented place capacity
  7. Declare amenities as structured data
  8. Declare hazards as structured data
  9. Measure place stability independently
  10. Create Reedbank Quarter
  11. Create North Gate Fields
  12. Create Copper Landing
  13. Create Lattice One
  14. Create Terminus Yard
  15. Create Selene Ward
  16. Create a persistent era-household registry
  17. Bind household structures to one era package
  18. Give household archetypes stable keys
  19. Describe household composition explicitly
  20. Describe household livelihood explicitly
  21. Declare recurring obligations
  22. Declare isolated starting resources
  23. Declare household pressures
  24. Create Courtyard Kin Household
  25. Create Barge Crew Household
  26. Create Granary Steward Household
  27. Create Maintenance Cluster
  28. Create Cycler Family
  29. Create Founding Cohort Home
  30. Represent multigenerational care
  31. Represent working partnerships
  32. Represent apprentices and sponsored residents
  33. Represent dependent children
  34. Represent elder care without erasing agency
  35. Create persistent era dilemmas
  36. Bind every dilemma to one life chapter
  37. Give dilemmas stable package-local keys
  38. Classify household, livelihood, governance, and legacy domains
  39. Publish dilemma prompts and stakes
  40. Give every dilemma three declared responses
  41. Give every response a stable key
  42. Publish response costs before choice
  43. Publish narrative consequences before choice
  44. Declare metric effects as structured data
  45. Preserve protected essentials separately
  46. Create four historical dilemmas
  47. Create four future dilemmas
  48. Create the household-minimum water dilemma
  49. Create the guild-debt dilemma
  50. Create the disputed-gate dilemma
  51. Create the contested-ledger dilemma
  52. Create the protected-air dilemma
  53. Create the uncovered-shift dilemma
  54. Create the independence-charter dilemma
  55. Create the allocation-model dilemma
  56. Create persistent Long Life campaigns
  57. Require a completed era rehearsal first
  58. Require passing rollback evidence first
  59. Prevent one rehearsal from spawning duplicate campaigns
  60. Require place and household from the rehearsed package
  61. Give every campaign a public UUID
  62. Generate deterministic campaign seeds
  63. Preserve a private campaign state
  64. Track security independently
  65. Track belonging independently
  66. Track purpose independently
  67. Track knowledge independently
  68. Track reserves independently
  69. Track household trust independently
  70. Track place stability independently
  71. Record that production export remained false
  72. Create four named life chapters
  73. Lock future chapters before their turn
  74. Open Making a Home first
  75. Open Obligations Arrive second
  76. Open The Public Choice third
  77. Open What Endures fourth
  78. Preserve chapter opening state
  79. Preserve chapter closing state
  80. Preserve chapter summaries
  81. Create a deterministic household cast
  82. Give cast members era-appropriate names
  83. Give cast members roles and ages
  84. Give cast members relationship context
  85. Give cast members explicit needs
  86. Track trust per cast member
  87. Create server-authoritative campaign decisions
  88. Require the active chapter dilemma
  89. Reject foreign-package dilemmas
  90. Reject future-chapter dilemmas
  91. Give every decision an idempotency key
  92. Return prior evidence for repeated decisions
  93. Preserve decision before-state
  94. Preserve decision after-state
  95. Bound all life metrics from zero to one hundred
  96. Preserve chosen response labels
  97. Preserve structured costs and effects
  98. Create permanent campaign outcomes
  99. Bind outcomes to evidence and chapter
  100. Advance exactly one chapter per valid decision
  101. Advance campaign time by thirty days per chapter
  102. Complete a Long Life after four decisions
  103. Create private era campaign archives
  104. Preserve campaign chronology
  105. Preserve every choice in the archive
  106. Preserve every outcome in the archive
  107. Generate deterministic SHA-256 archive checksums
  108. Keep campaign archives private by default
  109. Create cross-era campaign comparisons
  110. Require two completed lives from different eras
  111. Require both lives to belong to one character
  112. Compare seven material and social dimensions
  113. Preserve left, right, and difference values
  114. Explain differences without ranking societies
  115. Generate comparison checksums
  116. Make repeated comparisons idempotent
  117. Create era-package promotion reviews
  118. Restrict promotion review to administrators
  119. Require human approval in every review
  120. Count completed rehearsals as evidence
  121. Count passing rollbacks as evidence
  122. Count completed Long Lives as evidence
  123. Count unresolved critical findings
  124. Publish unmet evidence gates
  125. Distinguish evidence hold from evidence ready
  126. Never auto-transition production history
  127. Never change package status during evidence review
  128. Preserve reviewer and review time
  129. Generate promotion-review checksums
  130. Add places and households to the Epochs interface
  131. Add Long Life launch controls
  132. Add chapter and cast visualization
  133. Add branching dilemma controls
  134. Add private archive dossiers
  135. Add cross-era comparison panels
  136. Add promotion evidence panels
  137. Publish the no-auto-transition contract to every player
  138. Update the homepage to 1021 documented waves
  139. Update the Player Guide for sustained era lives
  140. Update the Roadmap around Alpha 0.9
  141. Reconcile Changelog and Patch Notes
  142. Preserve free access and zero paid gameplay power
Alpha 0.8143 changesVerified feature group
Waves 842–931 · Deep Time becomes playable

History can be rehearsed; the future can be tested

The validated Epoch SDK gains its first complete fictional historical and future packages, then opens deterministic player rehearsals with isolated resources, production chains, institutions, technology, social norms, balance evidence, compatibility findings, and verified rollback.

  1. Create a dedicated era-package registry
  2. Bind every era package to one persistent world
  3. Bind packages to declared historical or future epochs
  4. Bind era packages to validated content packages
  5. Give every era package a stable unique key
  6. Version era packages independently from engine code
  7. Distinguish historical and future package categories
  8. Preserve a human-readable chronology label
  9. Publish an explicit era summary
  10. Publish a player-facing era contract
  11. Declare era rules as structured data
  12. Declare isolated starting state as structured data
  13. Preserve engine and world compatibility metadata
  14. Generate deterministic SHA-256 era checksums
  15. Require validated status before rehearsal entry
  16. Create The River Covenant historical package
  17. Place the River Covenant in Aurelia’s fictional documented past
  18. Model a riverine-mechanical technology baseline
  19. Model courier communication delay
  20. Model human, animal, water, and wind energy
  21. Model foot, barge, and cart transport
  22. Model covenant marks without conversion to production currency
  23. Model ledger and oral-witness recordkeeping
  24. Create the Orbital Commonwealth future package
  25. Bind the Orbital Commonwealth to the existing Orbital Threshold epoch
  26. Model closed-loop orbital settlement constraints
  27. Model solar, storage, and recovered thermal energy
  28. Model shuttle, tug, and cycler transport
  29. Model habitat credits without production conversion
  30. Model distributed civic recordkeeping
  31. Declare that future content is rehearsal rather than prediction
  32. Declare that era packages never require AI
  33. Declare that era packages contain no real-money access
  34. Create sixteen era-specific professions
  35. Give every profession a stable package-local key
  36. Give professions explicit sectors and descriptions
  37. Bind professions to capability evidence instead of permanent classes
  38. Give professions era-specific entry thresholds
  39. Give professions structured material and social outputs
  40. Expose professional risks instead of hiding them
  41. Create canal keeping, reed craft, grain stewardship, courier, healing, scribal, barge, and assembly work
  42. Create life-support, fabrication, systems ecology, piloting, civic audit, radiation medicine, planning, and settlement diplomacy work
  43. Create twelve era-specific resources
  44. Distinguish renewable and finite era resources
  45. Give every resource an explicit scarcity score
  46. Declare practical uses for every resource
  47. Preserve regional resource notes
  48. Create ten explicit resource-transformation recipes
  49. Require declared inputs before output creation
  50. Consume inputs atomically
  51. Create traceable recipe outputs
  52. Give recipes explicit energy costs
  53. Gate recipes by rehearsal knowledge
  54. Associate recipes with accountable institutions
  55. Create eight era institutions
  56. Give institutions explicit mandates
  57. Give institutions bounded powers
  58. Publish accountability mechanisms for every institution
  59. Track baseline legitimacy independently
  60. Create eight era-specific social norms
  61. Name groups supported by each norm
  62. Name groups pressured by each norm
  63. Score pluralism without presenting consensus as universal
  64. Represent historical structural exclusion as pressure instead of a locked player role
  65. Represent essential future services as protected common systems
  66. Create twelve era technology paths
  67. Give technologies prerequisites, effects, and research costs
  68. Distinguish retireable technologies
  69. Keep automated allocation optional and replaceable
  70. Prevent historical care from being presented as modern clinical equivalence
  71. Create ten cross-era overlap rules
  72. Compare legacy and incoming behavior per system
  73. Declare transition resolutions explicitly
  74. Give every overlap a bounded duration
  75. Declare reversibility per overlap
  76. Protect occupancy during property-system transition
  77. Prevent cross-era currency arbitrage
  78. Require supervised professional recognition across eras
  79. Preserve a common rights floor across governance transitions
  80. Prevent rehearsal mortality from exporting to production
  81. Create package compatibility findings
  82. Give findings severity, system, mitigation, and lifecycle status
  83. Flag lineage exclusion as a historical identity risk
  84. Flag historical treatment equivalence as a critical health risk
  85. Flag essential-service coercion as a future life-support risk
  86. Flag small-settlement governance capture
  87. Flag automated allocation as a dependency risk
  88. Create private player-owned era scenarios
  89. Give every scenario a public UUID
  90. Choose an era profession before rehearsal
  91. Generate deterministic scenario seeds
  92. Preserve structured scenario state
  93. Track scenario days independently from world time
  94. Track energy, wellbeing, knowledge, influence, and era tokens
  95. Track isolated inventory by resource key
  96. Track technology progress independently
  97. Track institution trust independently
  98. Create six server-authoritative rehearsal actions
  99. Practice era professions without changing production finances
  100. Gather package-scoped resources
  101. Craft through declared transformation recipes
  102. Participate in era institutions
  103. Research declared technology paths
  104. Make rest a material ordinary-life action
  105. Advance one rehearsal day per resolved action
  106. Bound energy, wellbeing, influence, and knowledge
  107. Create immutable before-and-after action evidence
  108. Give every action an idempotency key
  109. Return prior outcomes for repeated idempotency keys
  110. Preserve action target type and identity
  111. Create a permanent scenario event stream
  112. Give events category, description, significance, effects, and day
  113. Reject resources, recipes, institutions, and technologies from another package
  114. Reject actions against another player’s scenario
  115. Block new actions after scenario completion
  116. Require five actions before balance generation
  117. Create multidomain era balance reports
  118. Score survival, agency, economy, knowledge, trust, and reversibility
  119. Identify material pressure points from actual rehearsal state
  120. Publish bounded balance recommendations
  121. Scale confidence with accumulated evidence
  122. Generate deterministic report checksums
  123. Create automatic rollback rehearsals at completion
  124. Checksum the restored starting snapshot
  125. Verify scenario isolation explicitly
  126. Verify the production character remained unchanged
  127. Verify currency was not exported
  128. Verify package checksum continuity
  129. Verify event preservation
  130. Record rollback duration
  131. Create findings from rehearsal pressure evidence
  132. Keep new balance findings open for later review
  133. Add Epochs as the thirty-seventh canonical life chamber
  134. Keep the Epochs surface authenticated
  135. Publish full package contracts in the interface
  136. Publish profession, resource, recipe, institution, technology, norm, overlap, and compatibility dossiers
  137. Expose scenario vitals and isolated inventory
  138. Expose recent event history
  139. Expose completed balance and rollback evidence
  140. Update the Player Guide for era rehearsal boundaries
  141. Update the Roadmap around the completed Alpha 0.8 program
  142. Update the public homepage to 931 documented waves
  143. Preserve permanent free access and zero paid gameplay power
Alpha 0.770 changesVerified feature group
Waves 772–841 · Becoming a person

Arrival becomes a supported, evidence-backed journey

The public site finally reflects the breadth of the current product while character creation expands into identity, background, appearance, privacy, access, planning, guidance, and a first-life journey grounded in real world state.

  1. Reframe the homepage around the current playable Alpha instead of the original five-system promise
  2. Publish twelve current-capability domains spanning self, home, work, economy, belonging, society, power, shadow, movement, frontier, creation, and continuity
  3. Publish an explicit consequence chain from person to household, region, institution, and history
  4. Publish documented build-wave, system, arrival, and world-continuity signals
  5. State free access and the absence of real-money mechanics in the hero
  6. Remove dollar-denominated language from character origin choices
  7. Publish the free-first, consent-first, and evidence-first product contract
  8. Add a seven-era Alpha history to the public homepage
  9. Create a dedicated public player guide
  10. Document a practical first-hour path
  11. Explain authoritative world time and idempotent simulation
  12. Document all canonical life chambers in one public systems map
  13. Document trust, blocking, consent, moderation, and protected mortality
  14. Document saved accessibility preferences and private character support
  15. Publish honest current-Alpha limitations
  16. Create a dedicated public roadmap
  17. Separate shipped systems from active depth work
  18. Separate shared-hosting capabilities from VPS and dedicated-server gates
  19. Keep monetization explicitly unresolved and deferred
  20. Add Player Guide, Roadmap, and Changelog to consistent global navigation
  21. Add social sharing metadata to public pages
  22. Expand the footer into a complete public information index
  23. Create layered persistent character profiles
  24. Make pronouns a first-class revisable identity field
  25. Support optional gender identity and presentation
  26. Support body frame, height, skin tone, hair, and distinguishing features
  27. Support player-authored style tags
  28. Preserve formative place and household context
  29. Preserve education and economic context
  30. Preserve worldview tags, formative events, strengths, and pressures
  31. Keep character access needs private by default
  32. Separate identity disclosure from access disclosure
  33. Support private, trusted, community, and public identity boundaries
  34. Create a permanent profile-revision ledger
  35. Record the account responsible for every profile revision
  36. Create persistent eight-chapter arrival journeys
  37. Make Arrival a canonical system visible from every life page
  38. Seed arrival steps idempotently
  39. Verify identity progress from a real character profile
  40. Verify shelter from the character’s actual housing state
  41. Verify aspiration progress from persistent aspirations
  42. Verify livelihood from real education or employment
  43. Verify connection from relationships or organization membership
  44. Verify agency from the life-action ledger
  45. Verify planning from an active life plan
  46. Calculate arrival completion from evidence rather than page visits
  47. Complete arrival without making it a gate to ordinary play
  48. Create an explicit world-contract acknowledgement
  49. Preserve optional private world-contract reflections
  50. Create revisable private life plans
  51. Support next-season, one-year, five-year, and lifetime horizons
  52. Let plans span self, home, learning, work, relationships, community, craft, public life, and exploration
  53. Preserve concrete next actions separately from intention
  54. Support plan review dates
  55. Create regional orientation-guide assignments
  56. Prefer high-agency living regional residents as guides
  57. Provide a civic orientation fallback when no guide exists
  58. Prevent guides from spending, deciding, or exposing private records for a player
  59. Record voluntary orientation check-ins
  60. Create private access-support requests
  61. Support mobility, vision, hearing, cognition, communication, sensory, chronic-health, and other needs
  62. Scope accommodations to interface, home, work, education, travel, or social participation
  63. Preserve known accommodations as structured records
  64. Expand first-life creation before world entry
  65. Create identity, origin, district, formative-history, access, and disclosure stages
  66. Redirect every new life into Arrival instead of a generic dashboard
  67. Keep all starting resources denominated in fictional Aurels
  68. Add a public Alpha 0.7 status across the product
  69. Increase the canonical system menu from thirty-five to thirty-six chambers
  70. Preserve free access with zero checkout and zero paid gameplay power
Alpha 0.660 changesVerified feature group
Waves 712–771 · The public record

Power meets an institution that remembers

Hierarchical places, community revision, independent newsrooms, accountable investigations, visible corrections, cultural institutions, negotiated norms, and transparency reporting deepen the world’s civic memory.

  1. Map existing location nodes into the world atlas
  2. Represent civic districts as persistent places
  3. Represent neighborhoods as persistent places
  4. Represent buildings and stations as persistent places
  5. Connect every local place to a regional parent
  6. Preserve estimated local population
  7. Preserve stylized coordinate provenance
  8. Create community-proposed atlas revisions
  9. Preserve the current atlas value
  10. Preserve the proposed replacement value
  11. Require an evidence-based revision rationale
  12. Name communities affected by a revision
  13. Keep revisions pending human review
  14. Support approved, rejected, and revision-required decisions
  15. Apply approved revisions to the authoritative atlas
  16. Keep rejected proposals in the permanent ledger
  17. Create formal source-review records
  18. Preserve the reviewer’s method
  19. Preserve known source limitations
  20. Update reliability only through a recorded review
  21. Create regional media organizations
  22. Give every newsroom a public-interest charter
  23. Measure editorial independence explicitly
  24. Track newsroom public trust
  25. Track newsroom audience independently
  26. Publish newsroom funding disclosures
  27. Declare advertising absent from the baseline newsrooms
  28. Create public editorial policies
  29. Require evidence before certainty
  30. Require visible corrections
  31. Require dignity-preserving source protection
  32. Let characters join a newsroom
  33. Preserve each contributor’s reporting beats
  34. Require active membership before investigation
  35. Give investigations stable public identifiers
  36. Require a testable investigation hypothesis
  37. Score public interest independently
  38. Score vulnerable-source risk independently
  39. Attach reviewed atlas evidence
  40. Preserve source-protection instructions
  41. Keep new evidence pending verification
  42. Support verified and rejected evidence review
  43. Require two verified records before publication
  44. Create an administrator editorial-review gate
  45. Preserve editorial rationale
  46. Preserve disclosed conflicts
  47. Support publish, revise, and reject decisions
  48. Preserve publication time
  49. Issue corrections without deleting the original statement
  50. Create accountable cultural institutions
  51. Track mandate, capacity, legitimacy, and independence
  52. Create accessible cultural programs
  53. Track program accessibility and reach
  54. Accept supportive, critical, curious, and unmoved participation
  55. Prevent duplicate participation without forcing consensus
  56. Create persistent cultural tensions with named groups
  57. Advance dialogue and intensity through world time
  58. Create reasoned norm proposals and unique ballots
  59. Require participation, support, and dialogue before norm acceptance
  60. Publish pulse-driven transparency counts with zero real-world funds and zero automated editorial decisions
Alpha 0.692 changesVerified feature group
Waves 622–711 · Free worlds, living places, contested truth

Access opens; culture moves

The alpha retires its experimental commerce surface in favor of permanent free access, then adds a provenance-aware world atlas and evolving cultural information layer.

  1. Declare the entire current product free to access
  2. Remove active checkout routes
  3. Remove active refund routes
  4. Remove active fraud-review routes
  5. Remove the commerce controller from the runtime
  6. Remove the commerce engine from the runtime
  7. Remove the commerce view from the product
  8. Retire Store from canonical navigation
  9. Redirect the retired Store path to Library
  10. Archive every legacy catalog product
  11. Create a dedicated free-resource library
  12. Give library resources stable keys
  13. Give library resources explicit free access policies
  14. Keep price metadata null
  15. Keep currency metadata null
  16. Declare payment required false
  17. Declare competitive advantage false
  18. Create persistent free access grants
  19. Make each account-resource grant unique
  20. Make repeated free claims idempotent
  21. Create immutable free-access events
  22. Preserve the granting account
  23. Preserve the granting source
  24. Preserve the grant time
  25. Expose already-claimed state
  26. Refuse non-free resources through the free claim path
  27. Add Library to canonical navigation
  28. State that no payment system is active
  29. Guarantee no paid gameplay power
  30. Add automated no-financial-record coverage
  31. Create hierarchical geographic areas
  32. Bind atlas areas to persistent worlds
  33. Bind atlas areas to existing regions
  34. Preserve area population
  35. Preserve stylized geometry references
  36. Mark baseline geography explicitly fictional
  37. Create time-bounded jurisdiction profiles
  38. Describe governance models structurally
  39. Preserve enumerated civil rights
  40. Preserve explicit jurisdiction restrictions
  41. Create regional language profiles
  42. Support official and vernacular languages
  43. Track writing systems
  44. Track prevalence independently from literacy
  45. Create living cultural profiles
  46. Preserve values, norms, etiquette, and heritage
  47. Mark cultural descriptions explicitly fictional
  48. Create source provenance records
  49. Preserve author and publisher provenance
  50. Preserve source type
  51. Preserve publication year
  52. Preserve reliability estimates
  53. Preserve bounded scope notes
  54. Queue player-submitted sources for review
  55. Prevent submissions from crossing worlds
  56. Keep pending sources out of accepted evidence
  57. Seed approved in-world institutional references
  58. Create human sensitivity reviews
  59. Preserve communities considered during review
  60. Preserve risks, recommendations, and remediation
  61. Create persistent traditions per place
  62. Preserve tradition origin stories and practices
  63. Track adoption independently from institutional support
  64. Create plural belief communities
  65. Preserve community values and membership
  66. Track public trust independently from pluralism
  67. Create authored cultural media
  68. Support journals, performance, broadcast, visual art, and oral history
  69. Preserve cultural authorship
  70. Preserve cultural themes
  71. Prevent cultural works from crossing worlds
  72. Create cross-region cultural diffusion
  73. Track influence independently from resistance
  74. Advance diffusion through authoritative world time
  75. Distinguish emerging, circulating, and adopted states
  76. Create public claims with stable identifiers
  77. Mark new claims unverified
  78. Support public and restricted classifications
  79. Attach provenance-reviewed citations
  80. Describe citations as support, dispute, or context
  81. Prevent citations from crossing worlds
  82. Create claim-confidence calculations
  83. Create permanent claim disputes
  84. Preserve original statements during disputes
  85. Prevent disputes from crossing worlds
  86. Support human dispute resolution
  87. Create auditable corrections
  88. Create auditable declassification
  89. Score public interest independently from harm risk
  90. Create idempotent cultural snapshots
  91. Feed culture and information into every world pulse
  92. Add Atlas and Zeitgeist to canonical navigation
Alpha 0.590 changesVerified feature group
Waves 532–621 · Scale, creation, and ownership

A world can grow without losing its soul

Tiered population orchestration, an accountable Epoch Creator Studio, and sandbox entitlement commerce move three major platform programs from architecture into tested product systems.

  1. Create a persistent population-fidelity registry per world
  2. Define individual-life fidelity for the most material residents
  3. Define household-cohort fidelity for growing populations
  4. Define district aggregation for metropolitan scale
  5. Define regional macro cohorts for world-scale populations
  6. Give every tier explicit population boundaries
  7. Give every tier an independent fidelity target
  8. Give every tier an update cadence
  9. Give every tier a hard entity-processing budget
  10. Create persistent regional population segments
  11. Preserve represented population separately from sampled entities
  12. Preserve demographic composition per segment
  13. Preserve employment and wealth signals per segment
  14. Preserve housing, care, and mobility pressure per segment
  15. Advance segments only at their declared cadence
  16. Create subsystem processing budgets
  17. Budget civilization, economy, relationships, health, and governance independently
  18. Declare a graceful-degradation policy for every budget
  19. Create persistent synthetic scale scenarios
  20. Give every scenario a public identifier
  21. Declare target population, duration, pulse size, and deterministic seed
  22. Preserve production-mutation constraints explicitly
  23. Benchmark allocation, economy, households, relationships, governance, and reconciliation
  24. Record represented and sampled entities per benchmark phase
  25. Record duration, throughput, memory estimate, and warnings
  26. Keep synthetic benchmarks distinct from production capacity claims
  27. Run million-resident scenarios without duplicating production people
  28. Preserve scenario status, result, start, and completion times
  29. Feed tiered representation statistics into every world pulse
  30. Expose a restricted Population Scale Lab
  31. Create authenticated private creator projects
  32. Give creator projects stable public and package keys
  33. Support world, epoch, expansion, and scenario categories
  34. Keep every project private by default
  35. Create a structured first revision automatically
  36. Preserve immutable numbered revisions
  37. Generate deterministic SHA-256 checksums per revision
  38. Accept reviewable JSON content instead of executable code
  39. Require schema-version declarations
  40. Require declared functional systems
  41. Require structured content definitions
  42. Require safety and consent declarations
  43. Require localization keys
  44. Reject mandatory AI dependencies
  45. Reject paid gameplay power
  46. Enforce a bounded revision size
  47. Persist every validation result and severity
  48. Separate valid and invalid revision states
  49. Generate deterministic non-mutating previews
  50. Preserve preview seeds, samples, counts, and warnings
  51. Require validation before publication submission
  52. Create a human publication-review queue
  53. Support published and rejected decisions
  54. Preserve reviewer identity and rationale
  55. Convert approved revisions into versioned content packages
  56. Adopt approved creator packages into their target world
  57. Preserve creator publication history
  58. Keep cross-account creator projects server-private
  59. Add Creator Studio to the canonical authenticated navigation
  60. Add automated creator ownership, validation, preview, and publication coverage
  61. Create a versioned commerce catalog
  62. Limit the catalog to cosmetic expression and optional content access
  63. Declare the no-pay-to-win contract in product rules and UI
  64. Create regional prices for USD, GBP, CAD, and AUD
  65. Preserve subtotal, tax, total, country, and currency
  66. Create globally identifiable purchase intents
  67. Require idempotency keys for purchase creation
  68. Prevent duplicate receipts and entitlements
  69. Create explicit sandbox-provider metadata
  70. State that no real payment was captured
  71. Create durable sandbox receipts
  72. Give every receipt a stable receipt number
  73. Create persistent account entitlements
  74. Preserve entitlement source, status, grant time, and metadata
  75. Create immutable entitlement event history
  76. Grant entitlements only after a completed sandbox intent
  77. Create velocity-based fraud risk signals
  78. Hold elevated-risk intents for human review
  79. Prevent held intents from silently granting ownership
  80. Create administrator fraud-review decisions
  81. Create user-owned refund requests
  82. Prevent refunds against another account’s receipt
  83. Create administrator refund decisions
  84. Revoke entitlements after approved refunds
  85. Preserve refunded amount and resolution evidence
  86. Keep denied refunds in the permanent record
  87. Add Store to the canonical authenticated navigation
  88. Keep all commerce and refund operations server-authoritative
  89. Expose an ownership ledger, receipt history, and sandbox warning
  90. Add automated pricing, idempotency, receipt, entitlement, refund, fraud, and authorization coverage
Alpha 0.560 changesVerified feature group
Waves 472–531 · Exchange and due process

Capital moves; power answers

Interregional freight, securities, inflation evidence, wealth safeguards, appeal rights, citizen councils, and concurrency-safe ballots deepen the economy and the social contract.

  1. Create a persistent securities registry per world
  2. Support index, equity, bond, and community instruments
  3. Give every security a stable world-unique symbol
  4. Track total issuance, price, distribution rate, and risk independently
  5. Create durable character security holdings
  6. Preserve units, average cost, and lifetime distributions
  7. Create globally identifiable limit orders
  8. Fund buy orders before market entry
  9. Reserve sell units before market entry
  10. Prevent unfunded or uncovered order placement
  11. Support explicit buy and sell limits
  12. Expire stale orders after seven days
  13. Return cash when buy orders expire
  14. Return units when sell orders expire
  15. Allow players to cancel open orders
  16. Return every reserved asset on cancellation
  17. Clear eligible orders server-authoritatively
  18. Lock orders before settlement
  19. Prevent already-settled orders from executing twice
  20. Calculate weighted holding cost after settlement
  21. Settle sale proceeds into persistent in-world bank balances
  22. Move security prices through bounded clearing pressure
  23. Pay evidence-backed periodic distributions
  24. Create persistent interregional freight bookings
  25. Price cargo and distance freight separately
  26. Preserve origin, destination, cargo, value, and route provenance
  27. Deliver shipments through authoritative world time
  28. Publish daily inflation and target-rate evidence
  29. Publish base rate, money-supply index, and wealth concentration
  30. Apply a bounded treasury-funded liquidity floor without resetting wealth
  31. Give enforcement actions a formal appeal right
  32. Limit each account to one appeal per enforcement action
  33. Preserve appeal grounds independently from the original report
  34. Keep immediate safety protections active during appeal
  35. Create an administrator appeal-review queue
  36. Record reviewer, recommendation, rationale, and reviewed evidence
  37. Support upheld, modified, and overturned decisions
  38. Clear account restrictions when an action is overturned
  39. Preserve appeal decisions in the moderation audit stream
  40. Move unreviewed appeals into an explicit review state
  41. Expire timed enforcement automatically
  42. Create persistent citizen governance councils
  43. Give councils explicit scope, quorum, and lifecycle
  44. Support voluntary council membership
  45. Require membership before proposing policy
  46. Create safety, trade, accessibility, and community proposals
  47. Give proposals stable public identifiers
  48. Preserve title, rationale, proposer, and closing time
  49. Open every proposal for a seven-day deliberation
  50. Require council membership before voting
  51. Support reasoned support and opposition ballots
  52. Enforce one ballot per member per proposal
  53. Give every ballot submission an idempotency key
  54. Create durable interaction receipts
  55. Return completed receipts without duplicating votes
  56. Lock proposals while tallying concurrent ballots
  57. Resolve proposals against explicit quorum
  58. Distinguish adopted, rejected, and no-quorum outcomes
  59. Add Trust and Exchange to the canonical authenticated navigation
  60. Add automated settlement, freight, policy, appeal, council, concurrency, and access coverage
Alpha 0.459 changesVerified feature group
Waves 412–471 · Operations and access

Reliability becomes visible; access becomes personal

Durable operational jobs, service probes, incident history, restore-drill evidence, public status, application-wide preferences, accessibility audits, and honest translation coverage move the alpha toward production accountability.

  1. Create a durable operational-job ledger
  2. Give every job a globally unique idempotency key
  3. Prevent duplicate enqueueing for the same operational intent
  4. Track queued, running, completed, and failed job states
  5. Record scheduled, locked, and completed times
  6. Count every execution attempt
  7. Measure job duration in milliseconds
  8. Preserve bounded failure messages for diagnosis
  9. Reject unsupported operational job types safely
  10. Support health-scan jobs
  11. Support Chronicle-advancement jobs
  12. Support queued world-pulse jobs
  13. Process due work in bounded batches
  14. Retry failed jobs without duplicating completed work
  15. Schedule the durable job worker every minute
  16. Schedule health probes every five minutes
  17. Protect scheduled workers against overlap
  18. Probe database connectivity
  19. Probe storage writability
  20. Probe simulation telemetry continuity
  21. Probe content-registry validity
  22. Probe durable-job failure pressure
  23. Record service status and latency independently
  24. Preserve structured details from every service probe
  25. Open operational incidents automatically on degradation
  26. Distinguish warning and critical incident severity
  27. Prevent duplicate open incidents for one failing service
  28. Require root cause and resolution before incident closure
  29. Create non-destructive restore-drill records
  30. Preserve restore stages, backup reference, checksum, duration, operator, and notes
  31. Publish a public system-status surface
  32. Display the latest result for each operational service
  33. Publish current incident state and resolved history
  34. Expose world-clock continuity on the status page
  35. Add System Status to the global footer
  36. Expand the administrator surface into an operations center
  37. Queue jobs through restricted administrator controls
  38. Process due jobs through restricted controls
  39. Run combined service and accessibility scans
  40. Expose failed job errors without leaking secrets
  41. Create automated accessibility evidence records
  42. Audit seven representative application surfaces
  43. Measure eleven WCAG-oriented criteria per surface
  44. Separate automated passes from manual review requirements
  45. Preserve severity, evidence, and remediation per criterion
  46. Add a keyboard-accessible skip link to every page
  47. Add globally visible focus indicators
  48. Apply reduced-motion preferences across the whole application
  49. Apply high-contrast tokens across the whole application
  50. Apply larger text across the whole application
  51. Add a reduced-decoration focus mode
  52. Add a dyslexia-friendly font mode
  53. Add spacious minimum control targets
  54. Apply saved preferences outside the Social Hub
  55. Set the document language from account locale
  56. Expand locale choices to English, Spanish, French, German, Portuguese, and Japanese
  57. Add date-format, number-format, and color-scheme preferences
  58. Measure reviewed translation coverage per locale
  59. Publish missing translation keys instead of claiming false completeness
Alpha 0.460 changesVerified feature group
Waves 352–411 · Epoch SDK and Chronicle

History advances only with evidence

World content becomes checksummed, dependency-aware, localized, migration-ready, and research-sourced while Chronicles gain measurable objectives, contributions, retirement, and fully gated epoch transition dossiers.

  1. Add explicit engine-version constraints to every content package
  2. Give packages a declared default locale
  3. Generate deterministic SHA-256 package checksums
  4. Track pending, valid, and invalid package states
  5. Record package validation time independently from release time
  6. Require every package manifest to declare functional systems
  7. Validate package schema versions
  8. Reject incompatible engine-major constraints
  9. Parse declared package dependencies from manifests
  10. Store dependency keys and version constraints independently
  11. Distinguish required from future optional dependencies
  12. Resolve installed dependencies against the registry
  13. Preserve missing-dependency failures instead of hiding them
  14. Create an immutable validation-result ledger
  15. Give validation results check name, severity, message, and context
  16. Revalidate packages when package data changes
  17. Associate City One definitions with their owning core package
  18. Generate deterministic checksums for content definitions
  19. Give definitions explicit schema descriptions
  20. Give definitions stable localization keys
  21. Create reviewed source-language localization entries
  22. Track localization locale, source locale, status, notes, and review time
  23. Create durable content-migration plans between package versions
  24. Preserve migration operations and checksums before application
  25. Expose installed-package validation directly in the Chronicle interface
  26. Show dependency resolution counts per installed package
  27. Show package validation-check counts
  28. Show package and definition checksum fragments for operational inspection
  29. Add package-validation statistics to the autonomous world pulse
  30. Keep package validation server-authoritative
  31. Add explicit rules to epoch records
  32. Give epochs readiness percentages
  33. Declare gated transition policy per epoch
  34. Declare archive retirement policy per epoch
  35. Create persistent Chronicle arcs tied to worlds and epochs
  36. Give Chronicles a premise, target, progress, lifecycle, and completion policy
  37. Create knowledge, infrastructure, civilization, and provenance objectives
  38. Weight Chronicle objectives independently
  39. Calculate objective progress from actual world state
  40. Include completed research in Chronicle knowledge progress
  41. Include completed public works in infrastructure progress
  42. Include completed resident goals in civilization progress
  43. Include approved sources in provenance progress
  44. Accept player contributions with documented evidence
  45. Charge contributions from persistent in-world bank balances
  46. Preserve contribution method, amount, character, evidence, and world time
  47. Prevent contributions to completed or foreign-world objectives
  48. Complete objectives without deleting contributions
  49. Complete a Chronicle only when all weighted objectives are satisfied
  50. Record Chronicle completion as a permanent historical milestone
  51. Retire completed Chronicles into read-only history
  52. Create formal epoch transition plans between adjacent epochs
  53. Measure package, research, provenance, and Chronicle transition gates
  54. Generate compatibility reports for each transition
  55. Generate ordered migration sequences before execution
  56. Keep under-ready transitions explicitly gated
  57. Restrict epoch execution to administrators
  58. Require exactly 100% readiness before execution
  59. Preserve executed transition plans and historical milestones
  60. Add Chronicle as the twenty-ninth canonical authenticated system
Alpha 0.460 changesVerified feature group
Waves 292–351 · Circulation and intention

An economy clears; a civilization plans

Regional supply and demand now produce durable prices, consumption, savings, labor pressure, and wealth provenance while autonomous residents pursue goals, meet obligations, hold authority, form strategy, and respond to crises.

  1. Create persistent food, energy, housing, care, materials, and transport markets in every region
  2. Give each commodity an independent reference price
  3. Measure regional supply from active productive capacity
  4. Measure demand from represented regional population
  5. Apply resource-specific demand pressure
  6. Clear market prices once per world day
  7. Prevent repeated same-day market clearing
  8. Track rising, falling, and stable price trends
  9. Calculate commodity volatility from price pressure
  10. Preserve supply, demand, price, trend, and clearing time
  11. Create persistent buy and sell limit orders
  12. Restrict player orders to their current region
  13. Track order quantity, limit price, fill, and settlement
  14. Fill eligible orders during a later clearing cycle
  15. Preserve unfilled orders instead of silently discarding them
  16. Add labor-pressure signals to every operating business
  17. Connect labor scarcity to employment conditions
  18. Give businesses a persistent supply-resilience measure
  19. Degrade resilience during regional shortages
  20. Recover resilience when circulation stabilizes
  21. Create household food-security state
  22. Create household utility-security state
  23. Create configurable automatic household savings rates
  24. Create explicit consumer-debt state for future credit consequences
  25. Purchase food, energy, care, and transport at regional clearing prices
  26. Charge household consumption from persistent in-world bank balances
  27. Record quantity, price, need before, and need after for consumption
  28. Create an auditable player wealth ledger
  29. Settle NPC household consumption once per world day
  30. Track NPC household food security, care capacity, savings, debt, and wealth
  31. Create persistent personal goals for autonomous residents
  32. Select resident goals from security, belonging, purpose, age, and agency
  33. Support economic, community, learning, care, and legacy goals
  34. Give each goal priority, criteria, progress, and status
  35. Advance resident goals no more than once per world day
  36. Increase progress through agency and stable employment
  37. Complete goals without deleting their developmental history
  38. Publish goal completion as a permanent life event
  39. Create ongoing household and family obligations
  40. Assign beneficiaries, monthly cost, and moral importance to obligations
  41. Fulfill obligations from actual resident cash
  42. Apply security pressure when residents cannot meet obligations
  43. Create persistent roles inside public institutions
  44. Select stewards and coordinators from high-agency residents
  45. Track authority, performance, appointment, status, and end time
  46. Create explicit one-year resident strategies
  47. Preserve strategy reason, confidence, horizon, and planned actions
  48. Review and replace strategies on a three-month cadence
  49. Connect strategies to current personal-goal domains
  50. Create economic, safety, and family-strain incidents
  51. Derive crisis category from resident needs and risk orientation
  52. Give incidents explicit severity and material effects
  53. Select self-managed or organized responses from agency
  54. Preserve open crises instead of resolving them invisibly
  55. Resolve aged incidents through recorded regional follow-through
  56. Expose goals and progress inside the resident ledger
  57. Expose obligations and institutional roles per resident
  58. Expose long-horizon strategy and confidence per resident
  59. Add a dedicated pressure-and-response observatory
  60. Feed circulation and NPC-continuity statistics into every simulation tick
Alpha 0.361 changesVerified feature group
Waves 232–291 · Health and habitat

A life is embodied; a home is remembered

Longitudinal care and persistent property stewardship turn health and shelter into evolving systems with consequences, records, recovery, utilities, permits, construction, maintenance, and autonomous change.

  1. Classify injury, chronic, mental-health, addiction, and infectious conditions
  2. Record diagnosis severity at authoritative world time
  3. Distinguish chronic conditions from temporary illness
  4. Mark infectious conditions for future transmission rules
  5. Calculate functional impact separately from clinical severity
  6. Give conditions positive, neutral, or restorative progression rates
  7. Track treatment adherence as its own health signal
  8. Preserve diagnoses in a permanent health-event chronology
  9. Create measurable care plans against individual conditions
  10. Support self-managed, weekly, intensive, and residential care
  11. Supersede care plans without deleting prior treatment history
  12. Set formal review dates for active plans
  13. Issue prescriptions with finite dose inventories
  14. Track medication purpose, effectiveness, and side-effect risk
  15. Charge fictional carried Aurels for prescribed treatment
  16. Record no more than one dose per world day
  17. Improve condition severity according to medication effectiveness
  18. Improve adherence through recorded dosing
  19. Complete prescriptions when the final dose is consumed
  20. Create home, work, travel, and education accommodations
  21. Reduce functional barriers without erasing the underlying condition
  22. Start persistent addiction, injury, burnout, and behavioral recovery programs
  23. Track recovery risk, progress, support, and completion independently
  24. Charge and record accountable recovery sessions
  25. Prevent repeated same-day recovery sessions
  26. Improve wellbeing through sustained recovery participation
  27. Advance active conditions through the autonomous world pulse
  28. Let active care offset natural condition progression
  29. Resolve conditions through time and care with a permanent resolution event
  30. Expose a readable health continuum, care ledger, recovery registry, and event history
  31. Create a dedicated Home system in the canonical navigation
  32. Unify owned and occupied property into one private dossier
  33. Give every property zoning, land envelope, security, utility capacity, and development level
  34. Create named rooms with purpose, area, condition, comfort, and use state
  35. Support bedrooms, kitchens, workshops, offices, clinics, storage, common rooms, and accessible rooms
  36. Prevent room plans from exceeding the property development envelope
  37. Charge construction costs from persistent in-world bank balances
  38. Connect power, water, network, waste, and climate utilities
  39. Give utilities capacity, usage, recurring cost, and active or limited service states
  40. Settle utility obligations once per world day
  41. Limit service when the responsible character cannot cover daily cost
  42. Require permits before regulated property projects
  43. Support renovation, expansion, rezoning, security, efficiency, and accessibility permits
  44. Resolve permit decisions against zoning constraints
  45. Preserve permit fees, decisions, application time, and decision time
  46. Fund construction projects before autonomous work begins
  47. Track project budget, quality, progress, status, and completion time
  48. Advance construction no more than once per world day
  49. Translate completed projects into lasting property effects
  50. Increase development envelopes through completed expansions
  51. Improve security through completed defensive projects
  52. Improve utility capacity through completed efficiency work
  53. Improve property condition through renovation and accessibility work
  54. Calculate maintenance liability through registered inspection
  55. Restore property and room condition through paid maintenance
  56. Cap restored room condition at full integrity
  57. Accrue maintenance pressure autonomously on occupied property
  58. Degrade neglected properties gradually instead of instantly
  59. Upgrade layered security without making homes invulnerable
  60. Preserve room, inspection, maintenance, security, and construction events in property history
  61. Add automated longitudinal-health, recovery, property, permit, utility, construction, navigation, privacy, and daily-idempotency coverage
Alpha 0.330 changesVerified feature group
Waves 202–231 · Material history

Every object leaves a trail

Items become persistent material entities with stacking, unique serials, legality, quality, durability, equipment, storage, repair, transfer, and reconciled release documentation.

  1. Separate stackable consumables from individually serialized durable objects
  2. Assign every durable object a globally unique serial
  3. Record market purchase provenance and acquisition world time
  4. Track item quality independently from current condition
  5. Add legal, regulated, restricted, and contraband-ready legality states
  6. Give item definitions weight, durability, stackability, equipment slot, and provenance requirements
  7. Create carried, stored, equipped, broken, and transferred object states
  8. Apply consumable effects through server-authoritative character updates
  9. Consume stack quantities atomically and remove empty stacks
  10. Use durable objects without destroying their unique identity
  11. Reduce durability according to item quality
  12. Automatically mark zero-condition objects broken
  13. Automatically unequip objects when they break
  14. Create tool, travel, and future expandable equipment slots
  15. Prevent one unique object from occupying multiple slots
  16. Create home locker, bank vault, workshop, and warehouse storage
  17. Track storage capacity, security, access, and contents
  18. Reject storage moves that exceed weight capacity
  19. Unequip an object before secured storage
  20. Repair objects through priced registered workshops
  21. Preserve before condition, after condition, method, cost, and repair time
  22. Transfer unique ownership only inside the same world
  23. Remove equipment and storage bindings during ownership transfer
  24. Append transfers to immutable object provenance
  25. Record purchase, use, wear, equip, storage, repair, and transfer events
  26. Apply daily equipped wear through the autonomous world pulse
  27. Prevent repeated same-day equipment wear
  28. Expose an equipment rack, serialized possessions, storage registry, and provenance ledger
  29. Publish /patch-notes as a first-class alias of the complete public changelog
  30. Reconcile footer terminology, current wave history, internal development ledger, and automated patch-note checks
Alpha 0.330 changesVerified feature group
Waves 172–201 · Professional identity

A title is earned; trust is contextual

Career development becomes a persistent evidence-based system while reputation separates profession, industry, community, region, organization, and public visibility.

  1. Create twelve reusable professional tracks spanning health, engineering, education, law, government, research, finance, journalism, logistics, trades, safety, and enterprise
  2. Define capability-based entry requirements instead of permanent character classes
  3. Give every track apprentice, practitioner, senior, lead, and master levels
  4. Track independent experience, performance, specialization, mentor, level, and status
  5. Allow multiple professional identities without erasing earlier work
  6. Add paid professional-development sessions with material time and energy costs
  7. Increase development value when a qualified mentor is recorded
  8. Select mentors from persistent high-agency regional residents
  9. Advance active careers autonomously once per world day
  10. Prevent repeated same-day background progression
  11. Use level-scaled experience thresholds for advancement
  12. Promote careers without requiring a page visit
  13. Create deterministic professional assessments grounded in skill, performance, experience, and mentorship
  14. Preserve the evidence used to calculate every assessment score
  15. Separate developmental failure from punitive lockout
  16. Create visible developmental incidents after an unsuccessful assessment
  17. Keep failed candidates eligible to train and reassess
  18. Issue professional licenses only after a passing assessment
  19. Give credentials explicit level, score, status, issue date, and expiration
  20. Support license renewal through current evidence
  21. Charge licensing and assessment costs through persistent in-world bank balances
  22. Create profession-scoped reputation independent from regional standing
  23. Create industry-scoped standing when credentials are issued
  24. Create community standing through trusted peer endorsements
  25. Track reputation visibility separately from score
  26. Translate scores into unknown, known, trusted, exemplary, distrusted, and notorious tiers
  27. Preserve the last twenty auditable reputation signals per context
  28. Decay old low-visibility reputation slowly toward neutral
  29. Never let one respected role automatically create universal trust
  30. Add Career to the canonical twenty-seven-system authenticated navigation
Alpha 0.322 changesVerified feature group
Waves 150–171 · City One completion

Movement becomes material

The final City One foundation closes the vehicle, transportation, accessible-map, content-minimum, and launch-readiness gaps identified in the master requirements.

  1. Create a versioned catalog of electric, hybrid, cargo, accessible, and specialist vehicles
  2. Purchase vehicles from persistent in-world bank balances with permanent ownership provenance
  3. Separate purchase from registration and baseline insurance
  4. Track vehicle condition, energy, mileage, seats, cargo, range, efficiency, and safety
  5. Restore energy through priced local consumption
  6. Perform maintenance with before-and-after condition records
  7. Block unsafe or under-fueled private journeys
  8. Create directional rail, air, and coach routes across every active region
  9. Track route fare, time, distance, capacity, reliability, and operating status
  10. Book server-authoritative public transportation
  11. Drive registered private vehicles across the same regional network
  12. Consume fuel, add mileage, reduce condition, and advance world time during travel
  13. Preserve every public and private journey in a durable ledger
  14. Create hierarchical district, neighborhood, building, and station location nodes
  15. Render a responsive stylized map without requiring a walkable 3D world
  16. Provide a complete text directory as a non-map alternative
  17. Add Mobility to the canonical twenty-six-system authenticated navigation
  18. Version career, business-category, and crime-action content independently from engine code
  19. Register twenty civilian careers and ten business categories for City One
  20. Register thirty server-authoritative crime-operation definitions
  21. Measure regions, careers, businesses, crimes, vehicles, routes, locations, firms, and organizations against launch gates
  22. Expose a restricted administrator City One launch-readiness contract
Alpha 0.222 changesVerified feature group
Waves 128–149 · Family resilience

Care becomes infrastructure

Families gain shared financial plans, long-term goals, emergency authority, conflict repair, public assistance, and eldercare that resolve through the same persistent world.

  1. Create a weekly household budget across housing, food, care, education, and savings
  2. Set reserve targets and expose a legible family resilience score
  3. Process recurring family obligations once per world day
  4. Track budget shortfalls as persistent household stress
  5. Move successful savings allocations into shared family wealth
  6. Create reserve, education, home, care, and reunion goals
  7. Fund shared goals from persistent in-world bank balances
  8. Complete goals atomically and reward durable family prestige
  9. Name family conflict across money, care, boundaries, education, inheritance, and time
  10. Record conflict context, intensity, participants, and open status
  11. Resolve disputes through direct conversation, family council, or professional mediation
  12. Preserve the written agreement and mediation method
  13. Designate prioritized medical, childcare, financial, and household emergency contacts
  14. Record temporary decision permissions without granting universal authority
  15. Apply for childcare, education, caregiver, housing, or scholarship assistance
  16. Resolve eligibility from documented family pressure during the world pulse
  17. Fund approved benefits from the public treasury with visible decisions
  18. Arrange check-ins, home support, daily care, or residential eldercare
  19. Track eldercare cost, quality, continuity, and caregiver strain
  20. Improve supported elder health while preserving the caregiver wellbeing tradeoff
  21. Feed budget, benefit, and eldercare metrics into simulation operations
  22. Add automated resilience, goal, mediation, safety-network, benefit, and eldercare coverage
Alpha 0.222 changesVerified feature group
Waves 106–127 · The lived family

Growing up becomes part of the world

Generational continuity expands into adoption, care, education, support, shared time, wellbeing, milestones, and preparation for independent adulthood.

  1. Finalize regional adoptions with permanent equal family standing
  2. Create adoption records distinct from biological birth history
  3. Open full guardianship automatically when adoption is finalized
  4. Enroll children in age-appropriate early, primary, or secondary education
  5. Choose general, arts, science, civic, or practical educational focus
  6. Track persistent progress, attendance, support, enrollment, and completion
  7. Advance education once per world day instead of once per page visit
  8. Record graduation as a permanent civilization life event
  9. Translate completed schooling into durable educational capability
  10. Arrange family, community, private, or after-school care
  11. Record care schedule, quality, weekly cost, status, and history
  12. Supersede prior care arrangements without deleting them
  13. Spend family time through conversation, outings, study, celebrations, and traditions
  14. Turn shared activities into permanent family memories
  15. Improve child belonging, purpose, and agency through attentive care
  16. Transfer allowances, education, health, housing, or adult-launch support
  17. Preserve the purpose and provenance of every family support transfer
  18. Show each child’s school stage and progress inside Generations
  19. Add a family chronicle of recent meaningful experiences
  20. Expose eligible adoption placements without duplicating existing family membership
  21. Feed education and graduation metrics into simulation operations
  22. Add automated adoption, school, care, activity, support, and graduation coverage
Alpha 0.216 changesVerified feature group
Waves 84–105 · Generational continuity

A lineage becomes playable

Partnership, parenthood, aging, mortality consent, estates, succession, and remembrance now form one protected multi-generation lifecycle.

  1. Record marriage only from a trusted partnership with explicit property, care, parenthood, and exit agreements
  2. Support no-fault separation while preserving family history
  3. Plan pregnancy separately from marriage and resolve birth only after the world-time due date
  4. Create persistent child identities, family membership, and guardianship chains
  5. Age children through the autonomous simulation and close guardianship at legal adulthood
  6. Grant independent status, occupation, and agency through a permanent adulthood event
  7. Sign or revise wills with an executor, heir distribution, charitable share, asset directives, and funeral preference
  8. Require age 70, explicit consent, a full world-day reflection period, and expired starter protection before life conclusion
  9. Never trigger player death automatically or through an ordinary world pulse
  10. Create permanent death records, funerals, memorials, attendance, epitaphs, and public visits
  11. Open itemized estates with liquid, property, and enterprise valuations
  12. Apply transparent estate tax above the protected threshold and preserve charitable distributions
  13. Pause settlement during inheritance disputes and record administrator findings
  14. Settle an undisputed estate into a new successor life with inherited assets, responsibilities, reputation, and history
  15. Add the Generations chamber to the canonical twenty-five-system navigation
  16. Add autonomous generation statistics to every simulation tick
Alpha 0.222 changesVerified feature group
Waves 62–83 · Multiplayer trust, consent, and enforcement

Together—with boundaries

The shared world gains consent-first presence, parties, protected trade, immediate blocking, structured reporting, moderation operations, and durable accountability.

  1. Publish explicit online, away, or focused presence with activity and visibility controls
  2. Separate directory, presence, trade, party, message, and competitive-contact consent instead of treating access as universal
  3. Save reduced-motion, higher-contrast, large-text, language, and timezone preferences at account scope
  4. Create invite-code parties with capacity, roles, readiness, voluntary departure, closure, and automatic leadership succession
  5. Fund direct player trade offers in escrow before delivery
  6. Accept trades atomically so both ledgers settle in one database transaction
  7. Decline or cancel offers with automatic escrow return and persistent final status
  8. Block accounts immediately in both interaction directions across discovery, messages, trades, and parties
  9. Submit categorized, severity-ranked safety reports with captured evidence metadata
  10. Convert reports into prioritized moderation cases with permanent status and resolution
  11. Apply warnings, timed mutes, timed suspensions, clearances, or dismissals through restricted administrator tools
  12. Record enforcement type, duration, target, moderator, reason, evidence context, and expiration
  13. Preserve social and moderation audit logs with privacy-safe network fingerprints
  14. Filter blocked accounts and messages from community discovery
  15. Enforce message consent plus mute and suspension state at delivery time
  16. Throttle report, trade, presence, and party-join endpoints against abuse
  17. Show personal report status and block management in the Social Hub
  18. Provide a restricted moderation queue, enforcement ledger, and audit stream
  19. Keep trust and safety controls authenticated while exposing no private evidence publicly
  20. Extend canonical navigation to twenty-four authenticated systems
  21. Add automated escrow, blocking, party, consent, reporting, and enforcement tests
  22. Document the multiplayer trust contract directly in the interface
Alpha 0.29 changesVerified feature group
Waves 54–61 · Zero-player civilization

Lives continue without an audience

Aurelia residents become persistent economic and social actors whose work, households, relationships, institutions, migration, and life transitions continue through the world pulse.

  1. Create persistent NPC employment with businesses, wages, hours, satisfaction, career changes, income, and living costs
  2. Form independent households with income, wealth, housing security, membership, merging, and relocation
  3. Build NPC-to-NPC relationships with affinity, trust, tension, partnership formation, and shared homes
  4. Let residents join real regional organizations when belonging needs drive civic participation
  5. Relocate pressured households toward lower-pressure regions while preserving origin, destination, and material effects
  6. Record employment, household, civic, family, and migration transitions in an auditable life-event stream
  7. Publish regional cohort snapshots for population, median age, employment, wellbeing, and pressure
  8. Add a Living Civilization observatory and extend canonical navigation to twenty-three authenticated systems
  9. Include civilization statistics inside every simulation tick for operational inspection
Alpha 0.29 changesVerified feature group
Waves 46–53 · Beyond becomes a civilization layer

The sky is not an escape hatch

Off-world progress becomes a persistent economy of research, vehicles, launch risk, settlements, logistics, hazards, and government rather than a decorative technology unlock.

  1. Charter and fund accountable space programs with technical-readiness and safety records
  2. Construct orbital shuttles, cargo tugs, and colony transports with persistent capacity, integrity, fuel, and systems
  3. Plan missions separately from launch, declare objectives and manifests, and resolve travel against destination distance and risk
  4. Discover orbital, lunar, and deep-space locations with gravity, atmosphere, radiation, resources, and habitability conditions
  5. Found chartered outposts from arrived missions while preserving founder roles and resident rights
  6. Dispatch food, water, and energy through costly world-time logistics chains
  7. Govern rationing, expansion, and life-support investment as material colony policy
  8. Record mission hazards, mitigation, vehicle damage, launch time, arrival, and permanent outcomes
  9. Add Beyond to the canonical twenty-two-system authenticated navigation
Alpha 0.26 changesVerified feature group
Waves 40–45 · Worlds, contracts, archives, and portability

Choose the rules before the life

The platform gains a public world registry, explicit lifecycle contracts, versioned content manifests, verifiable snapshots, and private account export.

  1. Browse worlds by lifecycle, access, capacity, simulation mode, status, and installed content
  2. Read permanent-history, mortality, inheritance, PvP, economy, and inactive-continuity guarantees before entry
  3. Register City One, Dominion, and Underworld as versioned packages with schema and dependency manifests
  4. Capture checksum-verified world snapshots and optionally publish them as read-only archive records
  5. Generate authenticated structured account exports without exposing passwords or authentication secrets
  6. Extend the canonical authenticated menu with Worlds and Archive while preserving every prior system
Alpha 0.15 changesVerified feature group
Waves 34–39 · The machinery of government

Authority becomes administration

Dominion expands from elections and laws into budgets, agencies, appointments, construction, diplomacy, and organized public pressure.

  1. Create persistent fiscal-period budgets with revenue, available funds, and departmental appropriations
  2. Operate regional agencies with mandates, staff, capacity, legitimacy, leadership, and accountable terms
  3. Fund infrastructure projects that consume budgets and advance through simulation time into permanent regional effects
  4. Negotiate trade, transit, research, and environmental agreements that alter diplomatic relations and access
  5. Open civic petitions, record support or opposition, trigger formal review, and preserve government responses
Alpha 0.15 changesVerified feature group
Waves 29–33 · Navigation and the persistent underworld

Every system stays visible; every secret leaves a trail

A canonical system menu removes navigation drift while criminal play gains organizations, operations, investigation, and continuity.

  1. Replace seventeen divergent page menus with one shared, automatically active navigation component
  2. Found or join persistent crews with ranks, permissions, treasuries, influence, heat, and succession-ready ownership
  3. Plan abstract operations whose outcomes resolve server-side against skill, risk, stake, and world time
  4. Generate evidence with provenance and strength plus witnesses with credibility, fear, loyalty, and status
  5. Keep incarceration playable through work, education, exercise, appeals, rehabilitation, sentence progress, and release
Alpha 0.15 changesVerified feature group
Waves 25–28 · Supply, treasury, protection, recovery

The economy learns to absorb shocks

Enterprise inputs, public obligations, regulated risk, and protected recovery connect private decisions to institutional continuity.

  1. Consume business inputs and automatically create location-sensitive procurement orders
  2. Accrue business and citizen tax obligations into persistent accounts and the public treasury
  3. Bind health, property, income, and business insurance with premiums, deductibles, limits, and claims
  4. Restructure qualifying liabilities through supervised insolvency without erasing essential assets
  5. Preserve viable re-entry paths so old worlds do not become permanently closed economies
Alpha 0.15 changesVerified feature group
Waves 21–24 · Agency, community, escrow, time

The world acts between visits

NPC autonomy, real player correspondence, protected agreements, and biological time deepen the persistent simulation.

  1. Generate and archive need-driven NPC work, social, learning, stability, and migration decisions
  2. Expose a privacy-aware citizen directory with persistent player messaging
  3. Deliver lifecycle and contract notifications through a unified inbox
  4. Protect player service payments in escrow through delivery, acceptance, release, and dispute states
  5. Anchor characters to birth dates, simulate birthdays, and establish explicit mortality-protection windows
Alpha 0.15 changesVerified feature group
Waves 18–20 · Contracts, ecology, truth

The shared world gains enforceable layers

Player work, environmental pressure, and information now persist as connected regional systems.

  1. List player-created professional services with skill-derived quality
  2. Hire guaranteed NPC alternatives or fund enforceable player contracts
  3. Track obligations, payment, jurisdiction, deadlines, collateral, and evidence
  4. Simulate regional weather, air, water, ecological health, resource depletion, and disaster risk
  5. Publish attributed intelligence whose credibility and visibility change through verification
Alpha 0.15 changesVerified feature group
Waves 16–17 · Ambition and culture

A life can pursue—and participate

Long-term aspirations and a cultural calendar turn progress into personal direction.

  1. Create measurable ambitions across wealth, life, social, collection, and civic paths
  2. Automatically synchronize goal progress against the living character record
  3. Unlock permanent achievements and prestige distinctions
  4. Discover region-specific venues, festivals, exhibitions, performances, and civic gatherings
  5. Purchase admission and preserve attendance in personal social history
Alpha 0.15 changesVerified feature group
Waves 13–15 · Body, belongings, capital

Health, possessions, and personal finance

The private realities behind public ambition became persistent systems.

  1. Track health, wellbeing, medical conditions, and private treatment history
  2. Access preventive, clinical, therapeutic, and emergency care
  3. Browse stocked regional goods and build a persistent personal inventory
  4. Transfer money between carried cash and civic bank accounts
  5. Apply through credit underwriting for funded personal loans
Alpha 0.15 changesVerified feature group
Waves 10–12 · Bloodlines and operations

Relationships become generations

Citizens gained intimate histories, heirs, and continuity beyond a single lifetime.

  1. Build affinity, trust, tension, and remembered interactions
  2. Form partnerships, families, and designate heirs
  3. Retire a character and continue through a successor
  4. Transfer cash, property, enterprises, reputation, and legacy
  5. Monitor world health through restricted simulation operations
Alpha 0.15 changesVerified feature group
Waves 7–9 · Power and permanence

Institutions remember

Individual action began changing law, enterprise, and historical time.

  1. Campaign for public office and resolve elections
  2. Write proposals and enact supported policy into active law
  3. Create player enterprises with staffing, capital, distress, and failure
  4. Record court, police, milestone, epoch, and legacy histories
  5. Establish the Eternal world contract and generational permanence
Alpha 0.15 changesVerified feature group
Waves 4–6 · The connected world

Markets, society, and the frontier

Aurelia became a network of reacting public systems.

  1. Generate dynamic regional prices, vacancy, and market dispatches
  2. Join organizations, contribute resources, vote, and take underground risks
  3. Travel between regions with persistent journey records
  4. Fund shared infrastructure and long-horizon research
  5. Feed economic activity back into regional conditions
Alpha 0.15 changesVerified feature group
Waves 2–3 · A playable life

From citizen to livelihood

The observatory became a persistent playable life.

  1. Register securely and create a regional character origin
  2. Manage needs, skills, decisions, consequences, and personal chronology
  3. Study through institutions and qualify for skill-gated careers
  4. Work paid shifts and build employment performance
  5. Rent or purchase homes while autonomous households and businesses operate
Alpha 0.15 changesVerified feature group
Wave 1 · First light

The observatory opens

The visual and technical foundation of the persistent world came online.

  1. Launch the cinematic public identity and World Observatory
  2. Establish Aurelia, its regions, districts, institutions, and population
  3. Create the simulation clock, treasury, and economic indicators
  4. Publish dispatches and autonomous world status
  5. Build the Laravel, MySQL, and shared-hosting foundation for future migration