Clear authority
Who may start, stop, recover, or speak for a process should be explicit, testable, and durable.
01 / What I work on
Making the invisible machinery legible.
No phantom work
Messages, acknowledgements, and retries need identities strong enough to survive real failures.
Evidence over folklore
A useful trace tells the truth about what happened without exposing what should stay private.
02 / How I think
Reliability is a product feature with a state machine underneath.
Find the authority boundary.
Most hard bugs become smaller once ownership and ordering are named precisely.
Separate fact from projection.
A displayed state is not automatically the durable truth that produced it.
Make failure inspectable.
The recovery path needs stronger evidence than the happy path, not less.
Keep the fix narrow.
Change the contract that is wrong, preserve the ones that are already right.