# ADR-013: Storage produces graphology format, flowgraph consumes it

## Status

Accepted

## Context

Graph data needs to flow between storage (persistence) and flowgraph (in-memory operations). The question is whether storage should depend on graphology directly.

## Decision

Storage doesn't need a graphology dependency. It produces the JSON serialization format (`SerializedGraph`) that `@alkdev/flowgraph`'s `FlowGraph.fromJSON()` and `SerializedGraph` consume. The Module entries validate data flowing in both directions. Storage defines the data shapes; flowgraph operates on them in memory.

## Consequences

- `@alkdev/storage` has zero dependency on graphology
- The `SerializedGraph` factory signature stays the same — its schema arguments come from Module entries instead of standalone schemas
- Storage produces format, flowgraph consumes format
- `moduleToGraphology()` and `fromGraphologyExport()` bridge functions will be added in Phase 4

## References

- [metagraph-module.md](../metagraph-module.md)