Modeling
Make object, document, and path layout explicit.
The problem is not “another ORM”
If data should stay inside a user-shaped boundary, developers need a modeling approach that fits pods instead of pretending everything is a relational table.
Access
Separate read patterns from exact write targets.
Extension
Keep bringing more sources, workflows, and domain models into the same system.
Why it matters to the whole system
The system cannot stop at chat history. It eventually has to understand more objects, states, and workflows. drizzle-solid is the layer that makes those objects durable and extendable.
- Make structure explicit
- Keep writes pointed at controlled locations
- Leave stable integration points for future extensions
Who needs it
Start with drizzle-solid when you need to connect your own data, domain objects, or workflows as a developer.
Next step
Start with the data layer
If your first question is how to bring more data and workflows in, start here.