Release
Ship the cycle, and carry the lessons forward.
papireleasetyped in your AI tool
The problem
Shipping is a manual scramble of tags, notes, and merges, and the lessons from the cycle evaporate before the next one starts.
How it works
Type release. PAPI tags the version, writes the notes, merges the cycle, and closes it. The cycle metrics roll into the next plan, so the following cycle is sized from what this one actually delivered.
➤storefrontpapi release
Cycle 12 released — v0.12.0
✓ 4 tasks shipped, all reviews accepted
✓ Tagged v0.12.0, notes written, cycle branch merged
✓ Cycle closed
Carried into Cycle 13:
• Delivered 14 pts. Next plan sizes from this, not the estimate.
• 2 issues found mid-build, queued for triage.
• Decision 7 (refund idempotency) held up, confidence raised.
Next: run plan to open Cycle 13.Put this on your own project.
Connect PAPI to the AI tool you already build in. This surface, and every other, come with it.