Storage
Keep a personal tool local instead of adding a hosted database.
A public walkthrough
Build a reading-list app with the decisions still attached.
This example shows Usual in a real build: the agent finds relevant history, makes routine calls, and gives you a review afterward.
The build
The app starts small and keeps its reasoning visible. Three decisions shape the first version:
Dependencies
Use what is already present when a small standard-library solution fits.
Scope
Start with a usable local demo before adding accounts or a larger service surface.
Review
Leave the decisions visible so you can accept, correct, or reject them.
What the evidence looks like
A decision is more than a preference label. Usual keeps the situation, the actual call, the reasons, and provenance together. The current agent can see why a choice fit the earlier context instead of copying a slogan.
{
"situation": "Should the local app use a hosted database?",
"call": "Keep the first version local",
"reasons": ["Try the idea before adding a service"],
"origin": "observed"
}The runnable source bundle for the small app is available as reading-list.zip. You can also inspect the source in GitHub.
What this demonstrates
Usual keeps the decision, the reason, the source, and the later review together. You can see what the agent used, decide whether it fits this build, and keep moving.