Code review was not enough.
We initially treated the pull request as the main review surface for website changes. That was insufficient. Customer-visible changes now require a real browser staging instance before production approval.
Field notes
Things worth keeping.
Not a feed for the sake of a feed. This is where Widerloom can preserve useful observations, changed minds, failures, removals, experiments, and public resources that deserve a longer life than a social post.
Changed our mind
Revision is a feature.
When better evidence changes a decision, the correction should become part of the record.
“Built” was too broad.
Architecture, implementation, deployment, reliability, governance, and proof are different states. The public trust vocabulary now preserves those distinctions.
Failures & recovery
Useful failures leave the system better.
Public-safe notes can show what failed, what was learned, and what changed without exposing sensitive infrastructure.
A preview path failed before it became dependable.
The first preview implementation hit GitHub environment and Cloudflare Pages permission boundaries. The staging path was changed to use the already-authorized Workers staging capability while preserving fail-closed commerce.
A workaround should become architecture only if it earns the role.
The temporary path is useful because it produces a real review surface. It remains separately governed from the intended production deployment model.
Subtraction log
Things we chose not to add.
Good product work includes protecting attention and maintenance capacity.
No engagement feed.
The site should feel alive because useful things change, not because an infinite stream is designed to keep someone scrolling.
No uptime chart yet.
Reliability history remains intentionally empty until enough real production observation exists to make the visualization honest.
Free first
Useful before you buy.
Public tools and resources should expand agency even when they never lead to a purchase.
Reversibility check
Separate easy-to-undo choices from commitments that deserve more evidence.
Use it freeCheapest useful next proof
Turn a big uncertainty into a smaller bounded experiment.
Use it freeIntegration inventory
Map systems and data boundaries before assuming replacement is necessary.
Use it freeResearch notes
Questions we are thinking with.
Short observations can become products, experiments, or simply remain useful ideas.
What does a customer actually need to own?
Source code is only one part of possession. Credentials, deployment knowledge, data export, runbooks, dependencies, recovery expectations, and operating authority matter too.
When is optionality worth paying for?
Not every reversible architecture is economically justified. The useful question is which future moves are valuable enough to preserve now.
Collections
Explore by situation, not chronology.
Collections let durable ideas accumulate around recurring human and business problems.
Collection
Making a hard decision
Evidence, uncertainty, counter-cases, reversibility, and next proof.
Start hereCollection
Building without lock-in
Portability, integration, ownership, handoff, and provider substitution.
Start hereCollection
Proving what matters
Claims, evidence state, freshness, reliability, recovery, and limitations.
Start here