vision: standalone CLI use is a supported front door - #10
Open
Kiran01bm wants to merge 1 commit into
Open
Conversation
pg-sprite is GitOps-ready, not GitOps-required. The properties that make it drivable by SchemaBot (deterministic plans, typed verdicts, bounded locks, crash-resume) also make it a safe direct CLI for an engineer with nothing but a DSN — including the urgent mid-incident change where the alternative is hand-typed DDL in psql. Add this to the tagline, pillar 2, and the "go-to" success criteria.
Kiran01bm
marked this pull request as ready for review
August 6, 2026 10:25
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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.
Summary
Broadens the vision's positioning: pg-sprite is GitOps-ready, not GitOps-required.
Standalone CLI use — an engineer with nothing but a DSN — is a supported front door, not a
demo mode. Docs-only.
What
Three edits to
docs/vision.md:required" alongside the SchemaBot execution-layer framing.
orchestrator (deterministic plans, typed verdicts, bounded locks, idempotent crash-resume,
no mid-flight operator judgment) make it a safe direct tool without adopting SchemaBot
first.
instead of a raw
psqlsession — for teams without a GitOps layer, and for the urgentmid-incident change where bounded locks, a verdict, and crash-resume matter most.
Why
The previous framing measured success exclusively through SchemaBot. That undersells a real
user class: teams that want safe schema changes today without standing up GitOps
orchestration, and operators who must run an urgent change during an incident — exactly when
hand-typed DDL (unbounded locks, no verdict, no resume) is most dangerous. The safe path
should also be the path of least resistance. Nothing in scope changes: SchemaBot remains the
fleet story ("What pg-sprite is not" is untouched); this adds the direct-use audience the
engine already serves by construction.