Practical field notes
Articles
Practical ways to connect requirements, people and agents around a clear next step.
10 articles
Keep requirements connected to the build
What TopDo does when a requirement moves under work that is already underway.
Give an agent a bounded piece of work
Scope the key, claim the node, hold the five-minute lease, complete with token and version.
Model a release with real dependencies
A dependency is a claim about the work, and only the ones you wrote are enforced.
A knowledge page that stays close to work
A page is a node with no state, and its links are edges you can delete by editing a sentence.
Customer feedback arrives as a signed push, not a sync
GreatFeedback events are pushed, HMAC-verified, and recorded once as work under a parent you choose.
Design fields your dashboard can trust
Five field kinds, three operations, two filters: design types so a total is right or null.
Retry an agent write without doing the work twice
Idempotency in TopDo is opt-in, keyed on four fields, and it expires after 48 hours.
A template amplifies the structure you gave it
A template is a node with a flag; run_process copies the tree. Structure is what repeats.
Schedule recurring work with the right clock
Recurrence is elapsed days from completion, and it reopens the same node instead of making a new one.
One home per node, and a graph for everything else
One parent decides where a node lives; typed edges decide what it affects. A copy breaks both.