Find the code.
Understand the decision.

A refund question needs more than a file name. This interactive example brings together the implementation, a saved decision, and the next session’s handoff. Choose a question, then inspect a source.

ShepAIrd / searchSample workspace

Where does our refund logic live?

Explore the context 3 example sources
Source previewL24–30

The refund entry point

src/billing/refund.ts

  1. export function refund(order: Order) {
  2. if (order.legacy) {
  3. return refundLegacyOrder(order);
  4. }
  5. const fee = calculateFee(order);
  6. return issueRefund(order, fee);
  7. }
Source references keep the evidence close.
Inspect the original context before you act.

Showing source: The refund entry point, L24–30.

Illustrative data · Choose a question, then select a result to inspect its source. Not a live search.

What you’re looking at

Code shows where legacy orders take a different refund path. Saved knowledge explains the original no-fee policy. The handoff records what was checked and which tests come next.

The questions and source files are synthetic. Selection happens locally; this is not a live search, a production interface, or a customer result. Your trial uses supported sources and access rules agreed for your deployment.

Now try a question from your own work.

Choose something that currently sends you through code, notes, and a previous conversation. Use it to define what a useful result must include.

Plan your trial Check source coverage