MAYBE: generalized schema-gate pattern (defer until a live-DB stack) #23
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
external-review
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence-archived#23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tier: MAYBE · decide deliberately
schema-gate pattern (generalized): "detect a change class that makes verification lie, then force a task." GSD-core's concrete version is ORM/DB-web specific.
Why consider: excellent idea in the abstract.
Decision needed: port the pattern only if a project runs a live-DB stack. John's work is Rust/CLI, so probably not yet. Defer until a project needs it?
Source: internal GSD comparison note, 2026-07-18.