Files
headquarter/openspec/changes/archive/2025-05-18-user-config-management/.pi-map.md
T
Developer 070cd4d5a5 chore: track all project map and index files
Add generated .pi-map.md and .pi-map.index.md files across the repository
so the project navigation maps are shared and versioned. These artifacts
are maintained by project_map_init/patch/validate and must be kept in
sync with source edits.

Note: .cache/ remains ignored (added in previous commit).
2026-06-12 13:46:23 +00:00

1.3 KiB

openspec/changes/archive/2025-05-18-user-config-management

dir: openspec/changes/archive/2025-05-18-user-config-management

index: openspec/changes/archive/2025-05-18-user-config-management/.pi-map.index.md

role

Design and planning package for a JSONB-backed user configuration management feature

files

  • .openspec.yaml | Defines an OpenSpec configuration file with schema type and creation date metadata
  • design.md | Design document for a simple key-value user configuration system using PostgreSQL JSONB | dep: PostgreSQL, JSONB
  • proposal.md | Proposes a feature to add persistent user preference storage and management through a JSONB-backed config system with API endpoints and frontend settings UI. | dep: database, API, frontend, UserConfig model, AppShell
  • tasks.md | Project task tracking document for implementing a user settings/config feature with backend API, frontend UI, and verification steps | dep: SQLAlchemy, Alembic, FastAPI/HTTP endpoints, React/frontend router, Docker Compose, ruff, mypy, pytest, TypeScript tooling

arch

Specification-driven development with phased implementation (proposal → design → tasks), using OpenSpec schema metadata and PostgreSQL JSONB for flexible schema-less storage

tags

design, user, jsonb, api, frontend, configuration, .openspec, document

symbols

workflows

dirty