- Bind
- Loopback only · 127.0.0.1
- Authentication
- Per-session bearer token regenerated on start
- Persistence
- File-backed state with atomic writes
- Health
- Daemon snapshot plus operator listening evidence
- Recovery
- Stop, start and verify persisted state
- Limitation
- Alpha packaging · not production-approved
product · AVC
Local-first execution and operator control.
The Local Node hosts governed runtime, health, recovery and private operator workflows.
Install, run, recover and roll back from an identified state.
The alpha runbook treats recovery and rollback as product behavior.
- 01Installcomplete
Clone, frozen install and build from an identified commit.
- 02Startactive
Launch daemon and operator, then wait for both health signals.
- 03Operatequeued
Use CLI, Mission Control and bounded operator actions through loopback.
- 04Recoverqueued
Restart from atomic file-backed stores without replaying completed occurrences.
- 05Rollbackqueued
Stop, restore state or prior software, rebuild and verify health.
Alpha boundary
Local Node packages the Kernel into one persistent local product.
The company daemon, loopback operator interface and CLI share file-backed state under a local AVC home while remaining separately observable processes.
Local trust
Operator access is loopback-only and session-bound.
The operator server binds to 127.0.0.1 and regenerates its bearer token on every start rather than sharing persistent credentials with conversational clients.
Known limits
Alpha packaging is usable, not production promotion.
Service registration, EV code signing, native Mission Control wiring and full production persistence remain explicit later gates.