decision: commit to Datomic as the MongoDB migration target#86
Open
lambduhh wants to merge 1 commit into
Open
Conversation
Reverses the 2026-06-01 decision that ruled out a schema-bearing database, now that the vision's data-model workstream needs an explicit target. Migration mechanics and hosting choice are deliberately left for separate follow-up decisions. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the project’s decision log to formally commit to Datomic as the migration target away from MongoDB, explicitly superseding the earlier 2026-06-01 decision that rejected schema-bearing storage assumptions.
Changes:
- Adds a new 2026-07-17 decision entry documenting the Datomic migration target, rationale, alternatives, and open risks.
- Updates the decision log frontmatter
modifieddate to reflect the new entry.
| ## 2026-07-17 — Commit to Datomic as the MongoDB migration target | ||
|
|
||
| ### Status | ||
| Decided — supersedes the [2026-06-01 decision](#2026-06-01--dual-format-entity-model-documentation)'s rejection of a schema-bearing database. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The 2026 vision names an explicit, extensible data model as the keystone investment that the verification pipeline, quality signals, REPL embed, multi-library support, and community/resource graph workstreams all depend on. entity-model-rfc.md (2026-06-09) already flagged Datomic as "under evaluation as the migration target," but no decision had formally committed to it.
Problem
The 2026-06-01 decision explicitly ruled out a schema-bearing database, reasoning "the system uses MongoDB (schemaless); a relational DDL would be misleading about the actual storage model." Proceeding with Datomic schema work without addressing that standing decision would leave the decision log silently contradicted.
Solution
Add a decisions.md entry committing to Datomic as the migration target, explicitly superseding 2026-06-01 with rationale. Migration mechanics (cutover strategy, downtime window) and Datomic edition/hosting choice are deliberately left open for separate follow-up decisions — this entry commits to the target, not the timeline.
This is the first landed milestone of a broader roadmap (RDF/knowledge-graph alignment, Claude Design UX prototyping, AI-scraped OSS example prepopulation, DevRel community campaign) sequenced via a
/grill-mealignment interview.Father Watson Questions
🤖 Generated with Claude Code