kandev/docs/specs/platform/README.md

status, system, specification_version, migration, owners

status	system	specification_version	migration	owners
draft	platform	1	in_progress	kandev

Platform system

Purpose

The platform system owns cross-cutting runtime services, configuration, observability, notifications, localization, lifecycle safety, and shared operational guarantees.

Ownership

This system owns startup and shutdown contracts, process and port-independent runtime safety, configuration precedence, diagnostics, notifications, localization, feature toggles, health, and shared session recovery services.

Settings discovery and interface parity belong to Platform. Each settings domain retains ownership of its values, validation, authority, and persistence.

Exclusions

• Executor-specific runtime environments belong to the executor system.
• Agent identity belongs to the agent system.
• Desktop shell behavior belongs to the desktop system.

Specification map

Requirements

• Startup lifecycle

• Agent-accessible Kandev settings

• Agent process exit and stderr drain

• Agentctl instance stop idempotency

• Agent Runtime Availability

• Background Work Liveness

• Backend restart page recovery

• Bounded Task Status Delivery

• Viewport-bounded Session Delivery

• Shared Cron Loop Safety When Office Is Disabled

• Environment-specific browser tab title prefixes

• Browser console retention

• Diagnostic logging

• Duration-aware E2E sharding and CI reliability

• External CI runner capacity

• Expected runtime log severity

• Feature Toggles

• Git Credential Lease Reissue

• Git Subprocess Admission

• Go dev launcher and minimal Node surface

• Health Endpoint — Surface the Running Version

• Watcher And Task Fallback Localization

• Additional I18n Audit Gaps

• Internationalization (i18n)

• LSP File Intelligence

• Session MCP Attachment Observability

• Mid-Turn Steering

• Semantic Notifications

• Apprise rescan

• Required Persisted Store Parity

• Provider Error Recovery

• Session Config Reconciliation Across Agent Types

• Session subscription recovery

• Setup and Launch Timeout

• Quiet benign teardown log noise on shutdown

• Do not surface backend-shutdown turn aborts as agent failures

• Startup Configuration Parity

• Prevent Host Sleep During Active Tasks

• Traditional Chinese locales (Taiwan and Hong Kong)

• Workspace Git Status

System design

• Startup lifecycle

• Agent-accessible Kandev settings

• Core settings domain adoption

• Agent process exit and stderr drain

• Agentctl instance stop idempotency

• Apprise rescan

• Background Work Liveness

• Backend restart page recovery

• Browser console retention

• Bounded Task Status Delivery

• Viewport-bounded Session Delivery

• Diagnostic logging System Design Part 1

• Diagnostic logging System Design Part 2

• Expected runtime log severity

• Duration-aware E2E sharding and CI reliability

• External CI runner capacity

• Health Endpoint — Surface the Running Version

• Internationalization (i18n)

• LSP File Intelligence System Design Part 1

• LSP File Intelligence System Design Part 2

• Session MCP Attachment Observability

• Required Persisted Store Parity

• Provider Error Recovery

• Workspace Git Status

• Go dev launcher and startup version

• Startup database selection continuity

Migration record

Migration remains in progress while legacy source detail is extracted from the canonical requirement and system-design documents above.

Related systems

• Agents: consumes shared runtime services.
• Executors: owns execution-environment details.
• Desktop: embeds platform startup and shutdown.