After defining the deployment contract in the previous level, this article focuses on validating a changeset before it reaches production. Rehearsal across environments ensures that execution order, rollback behavior, and baseline alignment all behave exactly as expected.
2026-05-20
468 reads
Level 2 formalizes the behavioral guarantees that a changeset must provide in order to be safely deployed and rolled back. It introduces the deployment contract, checkpoint semantics, and the structural scope of Create and Rollback scripts. Data changes are addressed through a dedicated Update mechanism, with clear boundaries and limitations. By the end of this level, a changeset becomes a predictable and well-defined unit that can be reasoned about independently of execution context.
2026-05-06
732 reads
By Arun Sirpal
Claude is more than a chat window. The desktop experience includes structured workspaces, generated...
A sequential scan is not always a problem — PostgreSQL's planner often chooses one...
I’ve been thinking a lot lately about what it actually takes to make an...
Good Morning. I have a T-SQL Script which has been developed to execute a...
Comments posted to this topic are about the item Stop Prompting Your AI Agent....
Comments posted to this topic are about the item Finish the quote
Finish this quote (for a fun Memorial Day question):
Do not try and bend the spoon. That's impossible. ...See possible answers