bu5hm4nn/vault-dash
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record CORE-001D1 completion

Browse Source
This commit is contained in:
Bu5hm4nn
2026-03-25 13:35:54 +01:00
parent 132aaed512
commit 1a2dfaff01
3 changed files with 30 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/roadmap/backlog/CORE-001D-decimal-boundary-cleanup.yaml
View File

@@ -7,13 +7,14 @@ depends_on:
- CORE-001B
- CORE-001C
tags: [core, decimal, persistence]
summary: Make Decimal/unit-safe values reliable across persistence, APIs, and provider boundaries.
summary: Complete the remaining Decimal/unit-safe boundary cleanup after the shipped persistence seam.
acceptance_criteria:
- Persistence format for unit-safe values is explicit and stable.
- Decimal-bearing JSON/API serialization is documented and tested.
- Float-heavy integrations have named conversion boundaries.
- Provider and cache adapter boundaries are explicit, documented, and tested.
- Decimal-bearing JSON/API serialization expectations are documented for remaining external seams.
- Float-heavy service entrypoints are narrowed or wrapped in named normalization adapters.
- Remaining raw-float domain hotspots are identified or removed.
technical_notes:
- Prioritize portfolio/workspace persistence, provider normalization, and cache serialization seams.
- `CORE-001D1` is complete: portfolio/workspace persistence now uses an explicit unit-aware schema with strict validation and atomic saves.
- Remaining focus is `CORE-001D2` provider/cache normalization and `CORE-001D3` service entrypoint tightening.
- Pre-launch policy: unit-aware schema changes may be breaking until persistence is considered live; old flat payloads may fail loudly instead of being migrated.
- See `docs/CORE-001D_BOUNDARY_CLEANUP_PLAN.md` for the current hotspot inventory and proposed sub-slices.