83: Remove lifecycle operations from the EvelynIOUBurnerService API

2026-09-04 10:04:47 +02:00
parent 681b6feef1
commit b6a6d544b5
11 changed files with 183 additions and 111 deletions
@@ -186,6 +186,10 @@ nenjim.journal.service</code></pre>
        <code>NenjimProcess</code> so the Hub owns startup. The implementation starts its configured active
        <code>PriceSource</code> instances internally and stops those already started if Ticker startup fails; it
        exposes no general Ticker stop operation.</p>
+    <p><code>EvelynIOUBurnerService</code> follows the same separation even though its current domain-service view is
+        empty. It supplies typed Registry and dependency identity without external controls, while the same
+        <code>EvelynIOUBurnerServiceImpl</code> object separately implements <code>NenjimProcess</code> for Hub-owned
+        startup. Neither the service interface nor the implementation exposes an ordinary stop or restart operation.</p>
    <p>The Ticker still explicitly selects the Raydium EVE/USDT source ID while the hardcoded source remains a passive,
        registered component. Process Manager continues to poll immutable ordered snapshots of actual successful
        startup milestones rather than displaying configured intent or claiming current health.</p>