docs: spec for sequa adopt (detect/convert existing DB tooling) - #29
Merged
Conversation
Design for a deterministic pipeline that fingerprints a project's DB tooling (sqlc/golang-migrate/goose/dbmate/atlas/…) and detects/plans/ applies conversion into sequa. Covers the source-system matrix with per-transform determinism levels, the "sequa is its own oracle" method (dry-run the real analyzer for exact suitability), the adopt detect|plan|apply surface, and a measured-signal scoring rubric.
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.
What
Adds
docs/specs/adopt.md— the design for a proposedsequa adoptcommand that deterministically detects a project's existing DB approach and suggests/performs conversion into sequa. Linked fromdocs/README.md.Highlights
readUpMigrations+AnalyzeQueriesin dry-run — proof per migration/query, not heuristics.sequa adopt {detect|plan|apply}— detect/plan read-only & fully deterministic; apply does only mechanical transforms, flagging the rest as TODO stubs.Docs-only; no code change. Grounded in a real trial across a tree of Postgres projects (models codegen proven on 11; engine gate proven on a SQLite project).