Skip to content

docs: position pg-sprite by problem class — online executor, peers not competitors - #54

Merged
Kiran01bm merged 4 commits into
mainfrom
kiran01bm/docs-tool-positioning
Aug 20, 2026
Merged

docs: position pg-sprite by problem class — online executor, peers not competitors#54
Kiran01bm merged 4 commits into
mainfrom
kiran01bm/docs-tool-positioning

Conversation

@Kiran01bm

Copy link
Copy Markdown
Collaborator

Positions pg-sprite by problem class in vision.md's ecosystem section so comparisons with other tools land on the right grounds.

Why

Readers keep comparing pg-sprite against convergence planners (pg-schema-diff, pg-delta) on object-model breadth — a category error: those tools produce a DDL artifact, they don't manage a live operation. The doc set never stated the split explicitly, so vision.md now does.

What

  • Extend "Where the existing ecosystem stops" with the two problem classes: convergence planners (schema change as an artifact) vs online executors (schema change as a production operation).
  • State that pg-sprite is an online executor and should be judged on execution grounds against pgroll and pg-osc — framed as peers solving the same problem under different design criteria, not competitors.
  • Note the planners meet pg-sprite only at its declarative front door, as potential complements, not alternatives.

Docs-only change; no code or behavior affected.

Name the two problem classes — convergence planners (pg-schema-diff,
pg-delta) vs online executors (pgroll, pg-osc, pg-sprite) — so
comparisons land on execution grounds: peers under different design
criteria, with planners as potential complements at the declarative
front door, not alternatives.
Replace the "judge it on execution grounds" framing: pg-sprite exists
to satisfy the design criteria in design-principles.md; pgroll and
pg-osc are peers built to different criteria.
The peers in the comparison list are linked; link pg-sprite the same
way so the three executors read in parallel.
@Kiran01bm
Kiran01bm marked this pull request as ready for review August 20, 2026 08:34
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@Kiran01bm
Kiran01bm merged commit 74422c2 into main Aug 20, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants