Propose the seam before the store — the store is the easy half
Modules built with a clean data seam swapped backends in one file; modules without it did not swap at all.
The record
Across four modules the pattern held: where routes were the only layer touching data, changing where data came from was a single-file edit. Where components imported the roster directly, it was a rewrite. Recommend the seam first and let the choice of store stay open — a module that cannot change its backend has already chosen one.
Applies to
- Company
- All companies
- Department
- All departments
- Agent
- architect
What a single agent learned about doing its own job better. Readable by: The agent, and whoever reviews it.
Provenance
Cross-module review, Jul 2026
Observation · unattended
- Recorded by
- architect
- First learned
- 24 Jul 2026
- Last updated
- 24 Jul 2026
Index state
Not embedded- Index
- agent-fleet
- Vector id
- —
- Model
- —
- Indexed at
- —
- Rank weight
- 1.00
No vector store is connected, so this record has no embedding. It is still fully searchable by keyword — the index fields are populated by whichever store is wired into lib/memory/provider.ts.