Labels: ready-to-code
Depends on: Issue 2
Implement the runtime configuration engine: RuntimeConfigResolver with cacheService, AdminConfigService with DB overrides, and Zod schema-driven validation as single source of truth.
Tasks
From openspec/changes/platform-operations-deployment/tasks.md sections 1 and 2:
- 1.1 All backend services depend on
coreServices.cache
- 1.2
RuntimeConfigResolver with 30s TTL and immediate invalidation
- 1.7 Config resolution: single cache layer
- 2.1 Define Zod schemas for all admin-configurable fields
- 2.2 Generate
config.d.ts types from Zod schemas
- 2.3 Validate all config writes via Zod
.parse()
- 2.4 Annotate each field with
configScope
- 2.5 Add Zod schemas for new config fields
- 2.7 Implement credential encryption for sensitive DB-stored values
- 2.8 Implement schema version tracking
Specifications
openspec/changes/platform-operations-deployment/design.md — Decisions 1-3
openspec/changes/platform-operations-deployment/specs/runtime-config/spec.md
openspec/changes/platform-operations-deployment/specs/cache-migration/spec.md — RuntimeConfigResolver scenario
Labels:
ready-to-codeDepends on: Issue 2
Implement the runtime configuration engine:
RuntimeConfigResolverwith cacheService,AdminConfigServicewith DB overrides, and Zod schema-driven validation as single source of truth.Tasks
From
openspec/changes/platform-operations-deployment/tasks.mdsections 1 and 2:coreServices.cacheRuntimeConfigResolverwith 30s TTL and immediate invalidationconfig.d.tstypes from Zod schemas.parse()configScopeSpecifications
openspec/changes/platform-operations-deployment/design.md— Decisions 1-3openspec/changes/platform-operations-deployment/specs/runtime-config/spec.mdopenspec/changes/platform-operations-deployment/specs/cache-migration/spec.md— RuntimeConfigResolver scenario