Why My Publisher Does Not Retry POST After a Timeout
How persisting intent before POST blocks another publication when the outcome is unknown, and why a success log alone cannot guarantee duplicate-free delivery.
ci-cd
When a Contract Test Knows Too Much
How LLMs can accelerate contract-test overengineering and why observable behavior matters more than implementation details.
Documentation as a Contract: Keeping CI Documentation in Sync with the Pipeline
How to turn critical claims about CI into contract tests that make documentation drift visible when the pipeline changes.
Prompts Define the Work, Checks Define Done
Why the definition of done should move from prompts into a verifiable contract, with an independent review of the agent’s result.
Why Verification Should Be Defined Before Implementation
Why acceptance criteria and verification methods should be defined before implementation, so that the meaning of done is not adjusted to fit the resulting solution.
Public Explanation as a Test of an Engineering Solution
How a public draft helps reconstruct a causal chain, expose hidden dependencies, and define the guarantees of an engineering solution.
How CI/CD and Flux Split Responsibilities in a DocOps Project
How an article moves through two repositories, where CI ends, and which part of delivery belongs to Flux.
Why CI in a GitOps Repository Is Not a Deployment Gate
Why CI does not block Flux after a direct push, and how a Merge Request with required checks moves validation before the watched branch.