Demo · sample dataTalk to us

Live demo · no sign-in

Follow one story from Jira to a signed-off release.

Run the stage agents, read the PR checks, see the orchestrator agent call GO, CONDITIONAL GO or NO-GO, roll it up into a release verdict and download the report. Then change the inputs and watch the call change.

Everything on this page is sample data for an invented shop. It runs in your browser: nothing is saved, and nothing is sent to Jira, GitHub or our servers. The verdicts use the same rules as the product.

01

The Jira story

In the product this is imported from Jira Cloud with a read-only token, or pasted in.

KAN-101StoryFix version: Shop 2026.12Ready for release

Save cards at checkout

As a returning shopper, I want to save a card at checkout so that I can pay in one tap next time.

Acceptance criteria

  1. 1A shopper can tick "Save this card" when paying.
  2. 2Saved cards show brand and last four digits only.
  3. 3A shopper can remove a saved card from their account.
  4. 4Card numbers are never stored by the shop, only the payment provider token.
  5. 5Paying with a saved card asks for the CVC again.
  6. 6Checkout still works for guests who do not save a card.
02

Four stage agents check it

Each agent returns a status and findings. Every finding cites the evidence it relied on.

Requirements, test architect, API tests and PR risk.
  • Requirements agent

    Waiting

    Press Run to start this agent.

  • Test architect agent

    Waiting

    Press Run to start this agent.

  • API test agent

    Waiting

    Press Run to start this agent.

  • PR risk agent

    Waiting

    Press Run to start this agent.

03

The pull request and its CI checks

In the product the orchestrator reads GitHub checks from a pull request link with a read-only token.

PR #128 · feature/kan-101-saved-cards

Save cards at checkout (KAN-101)

9 files · +412 −37

  • frontend / lint and typecheck1m 12ssuccess
  • backend / unit tests320 passedsuccess
  • backend / migrations48ssuccess
  • Agent evals (DeepEval)Known cases passsuccess
04

The orchestrator agent makes the call

Blockers beat conditions, conditions beat GO. Change the inputs and watch the call change.

Run the stage agents in step 2 to fill this in.
05

Roll every story up into one release verdict

The release is the Jira fix version Shop 2026.12. It is GO only when every story is GO, so one weak story is never averaged away.

Run the stage agents in step 2 to fill this in.
06

Download the report

The same report builder the product uses, as PDF, Markdown or JSON, for the change board or the audit trail.

Run the stage agents in step 2 to fill this in.

Want this on your next release?

Bring your own Jira stories, OpenAPI document and pull requests. We will run them through the agents with you.