Files
com_r35157_nenjim-hubd-impl…/openspec/changes/81-configure-ordered-process-autorun/tasks.md
T

1.8 KiB

1. Hub configuration

  • 1.1 Add the package-private immutable Hub configuration model and strict format 2 parser for the fixed runtime path, including exact version/section/comment/termination grammar and path-and-line diagnostics.
  • 1.2 Validate canonical process IDs, duplicates, known process construction capability, and mandatory Registry/Journal positions before Registry startup.

2. Ordered runtime composition

  • 2.1 Split NenjimHubImpl composition so the complete passive dependency graph is constructed and registered only after successful Registry bootstrap and contains no canonical process instance.
  • 2.2 Add an implementation-only lazy constructor catalogue for every supported modern non-Registry process, including optional Jupiter Perps Alarm, without encoding startup order.
  • 2.3 Drive construction, registration, canonical process resolution, startup, and post-success recording from the validated configuration order while preserving fail-fast partial-startup behavior, online announcement, and final wait.

3. Configuration template and documentation

  • 3.1 Add conf/NenjimHub.conf.example as a documented copy-only format 2 template reproducing the former startup sequence without enabling Jupiter Perps Alarm.
  • 3.2 Update Nenjim architecture, public documentation, and terminology for mandatory Hub configuration, exact grammar, manual dependency order, passive versus selected construction, omission, failure semantics, and headless operation.

4. Verification

  • 4.1 Inspect the implementation to confirm no runtime reference to the example file, no fixed autorun sequence, no eager process construction, and no public API expansion remains.
  • 4.2 Run strict OpenSpec validation and the complete Gradle build, resolving all failures without running the production Hub or adding general automated tests.