[P0] Implement validated configuration and privacy profiles #6

New issue

Closed

opened 2026-07-17 23:58:35 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-17 23:58:35 +00:00

(Migrated from github.com)

Goal

Provide one validated configuration system for all runtime behavior and privacy modes.

Requirements

Versioned configuration schema with safe defaults.
Profiles: privacy-strict, local-only, and local-first.
Remote providers disabled unless explicitly enabled.
Per-application, title-pattern, workspace, and metadata-source rules.
Capture cadence, retention, model, encryption, and storage settings.
Environment-variable overrides for non-secret settings.
Secrets referenced through key providers, never embedded in config.
Configuration reload must be atomic and fail closed.

Acceptance criteria

Invalid or incomplete security configuration prevents capture from starting.
Effective configuration can be inspected with secrets omitted.
Default configuration records nothing until explicitly enabled.
Schema migration behavior is documented and tested.

Depends on

## Goal Provide one validated configuration system for all runtime behavior and privacy modes. ## Requirements - Versioned configuration schema with safe defaults. - Profiles: `privacy-strict`, `local-only`, and `local-first`. - Remote providers disabled unless explicitly enabled. - Per-application, title-pattern, workspace, and metadata-source rules. - Capture cadence, retention, model, encryption, and storage settings. - Environment-variable overrides for non-secret settings. - Secrets referenced through key providers, never embedded in config. - Configuration reload must be atomic and fail closed. ## Acceptance criteria - Invalid or incomplete security configuration prevents capture from starting. - Effective configuration can be inspected with secrets omitted. - Default configuration records nothing until explicitly enabled. - Schema migration behavior is documented and tested. ## Depends on - #5