Author Gimble workflows

Write a program whose purpose, decisions, and evidence are visible in its source. Aim for the clarity of a page of pseudocode. Research, bake-offs, critique, retries, worktrees, and delivery are tactics written inline with ordinary Go and Gimble's primitives.

Use Godoc for the current API. For an existing command, use Use Gimble; for building and installing the application, use Build and release.

Define the outcome and its proof

State what the workflow should accomplish, its scope, and what someone must observe to know it worked. Give agents outcomes and useful verified facts; leave their approach open unless a particular method is a requirement. A plan can change as facts emerge. The original goal remains authoritative.

Separate three things in the design: