FOLLOW THE WORK
Come back when something changes.
New field notes, meaningful project changes, and corrections. Follow through RSS, or return to this page. Updates appear when there is something useful to share.
Open the RSS feedOne feed. No account required.
RSS brings updates from websites into a feed reader. In your reader, choose the option to add a feed and paste this address:
https://appwizzud.com/feed.xml
You can also open the feed above and copy its address. Your browser may show XML; the feed reader turns it into a list of updates. App Wizzud does not collect your email address.
An accounting design takes shape. A long sprint ends.
The accounting project now has a profile covering its recent architecture work and the browser prototype that exists today. The timekeeping correction sprint is complete after roughly a month and a half, with the feature enabled and some verification deliberately deferred.
The existing finish-line field note has a dated conclusion about custom test tools, repeated handoffs, and deciding which checks a release actually needs. Its earlier account remains intact.
Explore the accounting project, read the current timekeeping status, or read the sprint follow-up.
A clearer way into the work.
App Wizzud now offers clearer starting points for practical software, experiments, and fiction, with field notes alongside the work. Slow Proof’s profile has been corrected to point to free fiction already published at readslowproof.com, including Terms of Entry and Miquelon Issue One.
The software profiles distinguish internal use from availability to other people, and the experiment pages describe what has been tried and what remains open. The earlier Slow Proof description treated publication as still in development; the current profile reflects its public reading site. This is a description update, not a new publication announcement.
The production app’s earlier “IN USE” label is now “LOCAL WORKING PROJECT.” The available evidence shows installation with working records; recurring operational use and customer readiness are not established by that observation.
Explore the projects, read about Slow Proof, or go straight to the fiction.
Already in the feed.
The feed starts with these field notes. Their dates below are their original publication dates. Their original accounts remain distinguishable from dated follow-ups; current project pages provide later status where available.
What did this actually establish?
A narrow model result and a review process that kept expanding raise a practical question: when does more checking stop helping?
Why the finish line kept moving.
A working timekeeping app led to harder questions about corrections, backups, recovery, and owning the result.
What a passing checklist missed.
Four practical defects showed what a passing set of automated checks had left unasked.