Objective
Get the kernel running on a local development machine without containers or external infrastructure.
Scope
- Local mode without containers or external infrastructure
- Filesystem-backed persistence through memory subsystem
- Graceful shutdown and basic observability
Subsystems
- kernel/ — local mode configuration, startup/shutdown
- memory/ — filesystem persistence implementation
Dependencies
Depends on Objectives: Kernel Core Loop, Kernel Interface, Skills and MCP Integration.
Planning Notes
Observer Pattern Subsumes Structured Logging
The structured logging concern originally planned for this objective has been absorbed by Objective #2 (Kernel Interface), sub-issue #25 (Kernel observer). The kernel now adopts the orchestrate/observability.Observer pattern, which replaces the ad-hoc *slog.Logger with structured event emission. A slog adapter provides backward-compatible logging output.
This objective should focus on subsystem-level observer integration if needed beyond what Objective #2 establishes:
- memory — Observer events for key operations (list, load, save, delete)
- tools — Observer events for registration and execution
- session — Observer events for message operations
- agent — Observer events for provider requests
The kernel-level observer integration (iteration events, tool calls, run lifecycle) is fully handled by Objective #2.
Objective
Get the kernel running on a local development machine without containers or external infrastructure.
Scope
Subsystems
Dependencies
Depends on Objectives: Kernel Core Loop, Kernel Interface, Skills and MCP Integration.
Planning Notes
Observer Pattern Subsumes Structured Logging
The structured logging concern originally planned for this objective has been absorbed by Objective #2 (Kernel Interface), sub-issue #25 (Kernel observer). The kernel now adopts the
orchestrate/observability.Observerpattern, which replaces the ad-hoc*slog.Loggerwith structured event emission. A slog adapter provides backward-compatible logging output.This objective should focus on subsystem-level observer integration if needed beyond what Objective #2 establishes:
The kernel-level observer integration (iteration events, tool calls, run lifecycle) is fully handled by Objective #2.