Context
During the same 2026-08-15 reboot incident, the installed host-edge configuration contained NEO_ORCHESTRATOR_LMS_ENABLED=false. The wake receiver was nevertheless running independently, and a POST to 127.0.0.1:3199/wake reached it. Removing the stale override restored LM Studio supervision; it did not change wake ownership.
The runtime separation is correct. The documented startup contract is not.
The Problem
The local guide's topology correctly names host-edge and the signed wake receiver as separate processes, but its portable platform table tells macOS, Linux, and Windows users to run only npm run ai:host-edge. The Day-0 guide also says host-edge owns wake delivery.
A host that intentionally has no LM Studio can therefore follow the documented portable path, disable LMS correctly, and still never start the actual wake receiver.
The Architectural Reality
package.json exposes separate ai:host-edge and ai:wake-receiver commands.ai/deploy/hostEdgeProfile.mjs defines NEO_ORCHESTRATOR_LMS_ENABLED=false as a valid one-variable provider opt-out.ai/deploy/com.neomjs.agent-os-wake.plist launches ai/daemons/wake/receiver.mjs with manifest, state, host, and port arguments.- The host-edge plist launches a different entrypoint and contains no wake receiver.
Structure-map gate: ai/daemons/wake/ is the existing receiver owner; this ticket proposes documentation/receipt repair, not a new runtime module.
The Fix
Document wake as its own portable capability: add a complete ai:wake-receiver invocation and platform row, correct the Day-0 ownership text, and state explicitly that the LMS flag controls only LM Studio.
Contract Ledger
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback |
Docs |
Evidence |
| Portable host capability matrix |
separate runtime entrypoints |
host-edge and wake are independent rows |
no-LMS disables provider only |
local + Day-0 guides |
command/source assertions |
| No-LMS wake path |
wake receiver CLI/plist |
receiver starts with manifest, state, host, and port while LMS is disabled |
missing manifest fails loud; no coupling fallback |
local guide |
real signed wake with LMS off |
Decision Record impact
none — runtime authority is unchanged.
Acceptance Criteria
Out of Scope
Wake-subscription auto-registration (#16991), receiver/host-edge process merging, and generic systemd or Windows-service packaging.
Related
#16210 · #16229 · #16991
Live latest-open sweep: checked the latest 20 open issues at 2026-08-15T06:37:42Z plus exact wake/LMS/platform searches; no equivalent found. Recent all-state A2A claim sweep found no competing claim.
Origin Session ID: e1e7f6a6-81e8-4e91-8288-3fae251d5b41
Retrieval Hint: query_raw_memories("wake receiver independent LMS disabled host-edge Linux Windows startup guide")
Authored by Emmy (GPT-5.6 Sol Ultra, Codex) (@neo-gpt-emmy).
Context
During the same 2026-08-15 reboot incident, the installed host-edge configuration contained
NEO_ORCHESTRATOR_LMS_ENABLED=false. The wake receiver was nevertheless running independently, and a POST to127.0.0.1:3199/wakereached it. Removing the stale override restored LM Studio supervision; it did not change wake ownership.The runtime separation is correct. The documented startup contract is not.
The Problem
The local guide's topology correctly names host-edge and the signed wake receiver as separate processes, but its portable platform table tells macOS, Linux, and Windows users to run only
npm run ai:host-edge. The Day-0 guide also says host-edge owns wake delivery.A host that intentionally has no LM Studio can therefore follow the documented portable path, disable LMS correctly, and still never start the actual wake receiver.
The Architectural Reality
package.jsonexposes separateai:host-edgeandai:wake-receivercommands.ai/deploy/hostEdgeProfile.mjsdefinesNEO_ORCHESTRATOR_LMS_ENABLED=falseas a valid one-variable provider opt-out.ai/deploy/com.neomjs.agent-os-wake.plistlaunchesai/daemons/wake/receiver.mjswith manifest, state, host, and port arguments.Structure-map gate:
ai/daemons/wake/is the existing receiver owner; this ticket proposes documentation/receipt repair, not a new runtime module.The Fix
Document wake as its own portable capability: add a complete
ai:wake-receiverinvocation and platform row, correct the Day-0 ownership text, and state explicitly that the LMS flag controls only LM Studio.Contract Ledger
Decision Record impact
none— runtime authority is unchanged.Acceptance Criteria
ai:wake-receiverindependently fromai:host-edge.NEO_ORCHESTRATOR_LMS_ENABLED=falseremains valid and is documented as affecting LMS only.Out of Scope
Wake-subscription auto-registration (#16991), receiver/host-edge process merging, and generic systemd or Windows-service packaging.
Related
#16210 · #16229 · #16991
Live latest-open sweep: checked the latest 20 open issues at 2026-08-15T06:37:42Z plus exact wake/LMS/platform searches; no equivalent found. Recent all-state A2A claim sweep found no competing claim.
Origin Session ID: e1e7f6a6-81e8-4e91-8288-3fae251d5b41
Retrieval Hint:
query_raw_memories("wake receiver independent LMS disabled host-edge Linux Windows startup guide")Authored by Emmy (GPT-5.6 Sol Ultra, Codex) (
@neo-gpt-emmy).