What PAPI does

The loop PAPI runs, and what it remembers

PAPI works inside the AI tool you already build in. You run the cycle by typing commands in your chat; PAPI keeps the plan, the memory, and the map so the project stays coherent. Every step below is a real surface you can see.

Connect PAPI

The cycle you run in chat

Five commands, in order. Type them where you already work.

  1. Orientationpapiorient

    Instant Orient

    Pick up exactly where you left off, in any tool.

    See it
    papi orientStorefront · Cycle 12
    ➤storefrontpapi orient
    Storefront — Cycle 12 — Orient

Cycle 12 in flight. Next: Review — 1 build awaiting your verdict.

⚠ task-316 needs your verdict (checkout and customer portal)
⚠ 1 decision waiting on you

Health: 🟢 GREEN (73/100)
Velocity: 17 pts/cycle avg · scope accuracy within 3 pts
Strategy review: on track — next due Cycle 15

Board: 4 in cycle — 1 building, 1 in review, 1 shipped, 1 queued

Next action: Review task-316. Then task-317 (Refund handling) is mid-build.
  2. Planningpapiplan

    Adaptive Planning

    Picks the next task, in the right order — and gets sharper each cycle.

    See it
    papi planStorefront · Cycle 12
    ➤storefrontpapi plan
    Cycle 12 planned — 4 tasks, 15 pts (sized from last cycle's delivered 14).

  1. task-315  Email receipts on payment        S · 2pts
     Why: unblocks refunds, smallest surface. Do first.
  2. task-316  Checkout and customer portal     M · 3pts
     Why: the revenue path. Highest priority this cycle.
  3. task-317  Refund handling                  M · 3pts
     Why: depends on task-316's portal session.
  4. task-318  Rate limit the public API        S · 2pts
     Why: no dependency, safe to trail.

Handoffs written for all 4. Order set by priority and dependencies.
  3. Briefingpapibuild

    Build Handoffs

    Briefs your AI can run cold.

    See it
    Build Handofftask-317 · Cycle 12
    Why nowCustomers who pay by card need refunds to settle to the original card, and the current flow has no idempotency on retries, so a dropped webhook can double-refund.
    SCOPE (DO THIS)
    • Settle refunds to the original payment method.
    • Support partial refunds against a single charge.
    • Make webhook retries idempotent with a stored idempotency key.
    SCOPE BOUNDARY (DO NOT DO THIS)
    • Do not touch the checkout capture path.
    • Do not add a new payment provider.
    ACCEPTANCE CRITERIA

    [ ] Refunds settle to the original card [ ] Partial refunds supported [ ] Webhook retries are idempotent [ ] A dropped-then-retried webhook never double-refunds

    PRE-MORTEM
    • Most likely blocker: the provider sends the same webhook twice on retry with the same event id; key on the event id, not the charge id.
    EFFORT

    M

    ▸Show 1 additional section
    FILES LIKELY TOUCHED
    • refunds.ts
    • webhooks.ts
    • portal.tsx
  4. Qualitypapireview

    Quality Gate

    Every build is audited and reviewed before anything ships.

    See it
    Build Reviewtask-316 · Cycle 12
  5. Shippingpapirelease

    Release

    Ship the cycle, and carry the lessons forward.

    See it
    papi releaseStorefront · Cycle 12
    ➤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.

What lives across the project

The surfaces that persist beyond any single cycle.

Visibility

The Live Hub

Watch your project think.

See it
The Live HubPayments · Cycle 12
PlanBuildReviewRelease12Cycle
What just happened
  • task-317 started. Refund handling, brief in hand.just now
  • task-316 needs your verdict. Estimate held, scope accurate.8 min ago
  • Caught 2 issues nobody asked it to look for.9 min ago
Memory

Decision Memory

Your AI remembers what it built, and why.

See it
Active DecisionAD-7 · high confidence
AD-7

Refund idempotency keyed on webhook event id

Started Cycle 12Never referencedRisk score 8
RevisitHIGH
New decisionClick to see the full trail →

Key refund idempotency on the provider webhook event id, not the charge id. A single charge can have several legitimate partial refunds, so charge-id keying blocked valid refunds; event-id keying…

What this replacedAD-3 — Refund idempotency keyed on charge id
Direction

Strategy Reviews

Zoom out every few cycles; the direction stays true.

See it
Strategy ReviewCycles 8 to 12
Strategy Review · Cycles 8-12 · 5 cycles analysed

Payments is stable; the next constraint is trust at checkout

PAPI analysed 5 cycles (Cycles 8-12) — 3 recommendations, 0 decision changes, one direction shift.

Cycle healthHealthy
Velocitytracked
Reworkclean
Throughputsteady
2 carrying into the next planDefer or reject any that shouldn’t — the rest carry automatically
2 Carrying1 In plan

Carrying into the next plan

defer or reject what shouldn’t
direction
Prioritise checkout trust cues next cycle over new payment methods.
Carrying
Decision
Revisit whether the portal should be server-rendered for speed.
Carrying

Settled

all carried into the plan
New taskSurface card errors to the customer instead of failing silently.task-319In the plan

Direction

shifted this review
Was
Ship the payments MVP: checkout, receipts, refunds.
Now
Shift from feature coverage to checkout trust: visible security cues, clearer errors, and a faster portal.

The full read

the analysis behind the calls
1Full analysis

Five cycles delivered checkout, receipts, and refunds with velocity holding near estimate. The quality gate caught two payments regressions before they shipped. The binding constraint is no longer feature coverage; it is buyer trust at the checkout step.

Roadmap

Automated Roadmap

See where the project is heading, kept current as you ship.

See it
Project RoadmapStorefront · Cycle 12
Where it's goingThe road ahead

You're in Payments. Follow the horizons, stages, and phases still to come.

2horizons ahead
41%mapped done
3horizons total
Portfolio

Multiple Projects

Every project you run, in one place.

See it
Your Projects3 active
StorefrontCycle 12
Building2 hours ago
Mobile appCycle 5
In reviewyesterday
Marketing siteCycle 3
Planning3 days ago

One connection turns all of it on.

Point your AI tool at PAPI once. The cycle, the memory, and the map follow it into every project.

Connect PAPI