Skip to content

Roadmap

This roadmap records completed implementation slices and the next planned milestone. It avoids dates until the architecture and working slices need a calendar-based release plan.

0.1 - First Private World

  • Repository architecture - 0.1.1
  • Documentation - 0.1.1
  • Local private-server bootstrap - 0.1.1
  • Basic server lifecycle - 0.1.1
  • One-tick smoke validation - 0.1.1
  • Artifact capture - 0.1.1
  • Basic subject configuration - 0.1.2

0.2 - Observation and Interaction

Status: complete through 0.2.5.

0.2.0 - Meta Milestone

Defines the beginning of server observation and operator interaction work.

0.2.1 - Observation Layer

  • structured server lifecycle events - 0.2.1
  • server stdout/stderr capture - 0.2.1
  • tick observation - 0.2.1
  • live CLI rendering - 0.2.1
  • observation artifacts - 0.2.1

0.2.2 - Operator Console API

  • Operator Console API - 0.2.2

0.2.3 - Creative Mode

  • Explicit npm run play -- --creative enablement - 0.2.3
  • Typed Creative Mode command namespace in play sessions - 0.2.3
  • Creative Mode status, room targeting, and local player reporting - 0.2.3
  • Direct creep creation with validated body parts and ownership - 0.2.3
  • Selected structure and construction-site creation - 0.2.3
  • Explicit object and named-creep removal - 0.2.3
  • Energy set, fill, and drain for compatible objects - 0.2.3
  • Owned controller level changes - 0.2.3
  • Private-runtime checkpoint note command - 0.2.3
  • Creative command JSON Lines artifact log - 0.2.3

0.2.4 - External Subject Deployment

  • External subject path resolution and validation - 0.2.4
  • External Screeps repository subject adapter - 0.2.4
  • Explicit local subject build configuration - 0.2.4
  • Subject build stdout/stderr capture - 0.2.4
  • Screeps module collection and validation - 0.2.4
  • Subject Git revision and dirty-tree provenance - 0.2.4
  • Deterministic module manifest and checksum - 0.2.4
  • Private-server branch installation through the server adapter - 0.2.4
  • Transaction-safe replacement of installed subject code - 0.2.4
  • Controlled-tick external subject execution verification - 0.2.4
  • External subject deployment artifacts - 0.2.4
  • Interactive subject status and manual redeployment - 0.2.4

0.2.5 - Automated World Bootstrap

  • Operator command npm run world:bootstrap - 0.2.5
  • Non-destructive compatible-state reuse by default - 0.2.5
  • Explicit destructive --reset private-world recreation - 0.2.5
  • Private player reuse/creation through the server adapter - 0.2.5
  • Deterministic requested-room creation and active-room metadata - 0.2.5
  • Owned controller bootstrap at requested RCL - 0.2.5
  • Deterministic spawn placement with explicit coordinate support - 0.2.5
  • Spawn ownership, energy store, and runtime-valid structure fields - 0.2.5
  • Source and mineral seed objects for a playable fixture - 0.2.5
  • Controlled-tick post-bootstrap verification from authoritative state - 0.2.5
  • Run-specific world bootstrap artifacts and latest pointer - 0.2.5
  • External subject deployment verified against a bootstrapped room - 0.2.5

Interactive World Control

  • Persistent play command - 0.1.1
  • Explicit world reset flag - 0.1.1
  • Serialized controlled tick loop - 0.1.1
  • Pause, resume, manual step, and speed presets - 0.1.1
  • Local game/CLI port reporting - 0.1.1
  • Play artifacts - 0.1.1
  • Server output observation - 0.2.1
  • Operator Console API - 0.2.2
  • Creative Mode operator authority - 0.2.3
  • Synthetic subject code deployment - 0.1.2
  • Automated player bootstrap - 0.1.2
  • Memory observation - 0.1.2
  • External code deployment - 0.2.4
  • Automated room/spawn bootstrap - 0.2.5
  • Snapshot artifact inspection - 0.2.0
  • Reset-only snapshot sandbox import - 0.2.0
  • Non-reset compatible snapshot import - deferred (future patch)

0.3 - Scenario Engine

  • Status: scenario suites and regression baselines implemented through 0.3.5.

0.3.1 - Scenario Engine Foundation

  • Typed engine and scenario result contracts - 0.3.1
  • Inspectable queued/preparing/deploying/executing/observing/evaluating/reporting/cleanup/terminal lifecycle - 0.3.1
  • Terminal report invariant for pass, assertion fail, subject error, timeout, and preparation failure paths - 0.3.1
  • Run-isolated scenario artifacts and human summary output - 0.3.1
  • Bounded controlled-tick execution with timeout classification - 0.3.1
  • Basic assertion evaluation with pass/fail/error separation - 0.3.1
  • Representative synthetic scenario fixtures for contract validation - 0.3.1
  • Operator commands npm run scenario:run -- <scenario-id> and npm run scenario:smoke - 0.3.1

0.3.2 - External Subject Scenario Runner

  • External subject scenario contract and factory - 0.3.2
  • Scenario runner composition of external subject preparation, world bootstrap, deployment, controlled ticks, observation, assertions, reporting, and cleanup - 0.3.2
  • Operator command npm run scenario:run -- external-subject-smoke --subject-path ../screeps - 0.3.2
  • Bootstrap world strategy with explicit reset, room, RCL, spawn, and local player identity - 0.3.2
  • External subject build log, Git provenance, dirty-tree status, module manifest, and checksum artifacts - 0.3.2
  • Private-server branch installation and activation during the deployment lifecycle phase - 0.3.2
  • Bounded serialized controlled-tick execution with requested/completed tick reporting - 0.3.2
  • Generic assertions for subject execution, exact tick completion, no subject errors, and read-only Memory path existence - 0.3.2
  • Lab-owned external-subject subject-error fixture scenario - 0.3.2

0.3.3 - Snapshot-Backed External Subject Scenarios

  • Additive snapshot world strategy for external subject scenarios - 0.3.3
  • Operator command npm run scenario:run -- mmo-snapshot-smoke --subject-path ../screeps --snapshot <snapshot.json> --ticks <count> --reset - 0.3.3
  • Snapshot validation before private-server mutation - 0.3.3
  • Reset-only snapshot reconstruction through the existing server importer - 0.3.3
  • Additive schema-v1 multi-room terrain catalogs with legacy room.terrain fallback, terrain-only auxiliary reconstruction, and authoritative verification - 0.3.8
  • Snapshot provenance, import evidence, and combined terminal reporting - 0.3.3
  • Generic snapshot smoke assertions without colony-specific behavior - 0.3.3
  • Terminal classifications for pass, assertion failure, subject error, timeout, preparation error, deployment error, orchestration error, and cleanup error - 0.3.2
  • Run-isolated external scenario artifacts and latest pointer support - 0.3.2
  • Unit coverage for external scenario composition, artifact serialization, assertion failure classification, and subject error classification - 0.3.2

0.3.4 - Subject-Owned Assertion Contract

  • Versioned declarative JSON assertion manifest owned by the external subject checkout - 0.3.4
  • Operator command option --subject-assertions <subject-relative-json> for external subject scenarios - 0.3.4
  • Preparation-time manifest resolution, schema validation, checksum, byte size, assertion count, and subject Git provenance - 0.3.4
  • Safe Memory path observation with rejected traversal and prototype-pollution segments - 0.3.4
  • Generic subject assertion catalog: path-exists, path-absent, equals, not-equals, numeric-comparison, allowed-values, collection-size, changed, unchanged, increased, and decreased - 0.3.4
  • Separate Lab-owned and subject-owned assertion reporting and artifacts - 0.3.4
  • Focused unit coverage for manifest validation, provenance, temporal comparisons, failure classification, artifact serialization, and compatibility without a manifest - 0.3.4

Future 0.3 Work

  • Committed fixture repositories for broader controlled external-subject examples

0.3.5 - Scenario Suites and Regression Baselines

  • Committed, versioned suite definitions referencing registered scenarios - 0.3.5
  • Sequential isolated execution with continue and stop-on-failure policies - 0.3.5
  • One shared external-subject build and provenance record per suite - 0.3.5
  • Snapshot-backed suite world preparation through the existing import adapter - 0.3.5
  • Deterministic terminal aggregation and expected-failure contract fixtures - 0.3.5
  • Explicit, operator-created baselines with structured regression findings - 0.3.5
  • Run-isolated suite reports, repairable JSON index, and latest pointer - 0.3.5
  • Parallel execution, richer CPU/telemetry comparison, and CI integration - deferred

0.3.5.1 - Suite Operator Status Panel

  • Serializable suite/scenario progress events and run-local JSONL artifact - 0.3.5.1
  • Automatic TTY panel with stable plain-mode fallback - 0.3.5.1
  • Suite, subject, scenario lifecycle, tick, throughput, result, and artifact visibility - 0.3.5.1
  • Server-owned discrete simulation-speed presets and bounded benchmark diagnostic - 0.3.5.1
  • Interactive runtime throttle keys remain deferred because exact controlled ticks temporarily require the 1000 ms safety floor
  • Web dashboard and parallel suite execution remain deferred

0.3.6 - Release Candidate Qualification

  • Exact clean external-subject revision locking and source-drift detection - 0.3.6
  • One-build qualification with the tested module map preserved for later use - 0.3.6
  • Explicit validated snapshot and destructive private-world reset requirement - 0.3.6
  • Versioned candidate manifest with eligible, rejected, and error policy - 0.3.6
  • Run-isolated candidate evidence, integrity checks, index, latest pointer, and read-only inspection - 0.3.6
  • MMO upload, deployment, promotion, rollback, and credentials - deferred

0.3.6.1 - Candidate Artifact Identity Clarification

  • Separate direct subject-build identity from instrumented qualified-artifact identity - 0.3.6.1
  • Backward-compatible schema-version-1 candidate inspection - 0.3.6.1
  • Subject-build manifest provenance without duplicating the uninstrumented module map - 0.3.6.1

Infrastructure and Road Integration Validation

  • Ten-scenario snapshot-backed Lab suite, deterministic local mutations, infrastructure/route assertions, focused artifacts, telemetry percentiles, and candidate CPU gate - implemented and checked
  • Full 3,300-tick operator suite against the real MMO snapshot - pending operator run
  • Screeps 0.3.6.3 MMO beta validation - not performed
  • Public beta deployment or activation - not performed

Future 0.3 Follow-Up

0.3.8 - Accelerated Simulations and Screeps Telemetry Capture

  • Explicit backward-compatible controlled and bounded accelerated execution - implemented
  • Reduced intermediate persistence with mandatory final persistence - implemented
  • Generic streamed Memory.stats JSONL/CSV/summary artifacts - implemented
  • Performance summaries and lifecycle timeline artifacts - implemented
  • Long 500-tick and economy-cycle validation on the operator gaming PC - pending operator run

0.3.7 - MMO Deployment and Promotion

  • Artifact-driven MMO adapter and guarded upload/readback workflow - 0.3.7
  • Execution-verification contract, beta-first promotion, and exact-byte rollback - 0.3.7
  • Offline planning and fake-adapter validation - 0.3.7

  • Real beta/default validation - pending explicit operator authorization

  • Snapshot scenario report payload reduction: keep terminal scenario reports concise with remapping counts and summaries, preserve detailed source-to-private object-ID maps in snapshot-import.json or another dedicated detailed artifact, reference that artifact from scenario-report.json, and avoid duplicating large remapping tables while preserving snapshot import traceability.

  • Controlled-tick scenario performance: measure where the approximately ten-second-per-tick latency is spent across official-server tick cost, Lab orchestration, polling, persistence waiting, observation, and artifact writing; add useful phase telemetry and optimize before larger regression suites without weakening serialized tick guarantees or persistence verification.

0.4 - Overlord Orchestration

  • Agent protocol
  • Delegation
  • Session lifecycle
  • Structured observations and actions

Later

  • Parallel runs
  • Replays
  • Telemetry comparisons
  • Web dashboard
  • CI integration
  • Package testing beyond the primary colony bot