loomwell Get started
Menu
← Back to Loomwell

PUBLIC FORMAT SAMPLE

Useful context.
In every example.

Explore the request, agent decision, human correction, and outcome together. Three fictional workflows show exactly how the sample is structured.

All examples are syntheticNo signup required

Take the format with you.

3 fictional records, a file manifest, and an acceptance-criteria worksheet.

Download sample ZIP

JSONL + manifest · Public format demonstration

FICTIONAL / EXCHANGE / 001

When the right size is gone.

Synthetic

  1. Customer request

    Can I exchange the shirt for a medium?

  2. Tool result

    inventory.lookup: medium=0, large=2

  3. Agent decision

    I will send a medium replacement.

  4. Human correction

    Medium is unavailable. Ask before substituting large.

  5. Corrected response

    Medium is unavailable. Would large work instead?

The policy behind the correction

Obtain explicit customer consent before substituting a size.

Corrected outcome

Customer consent requested. No exchange created.

Inspect starting and final state

Starting state

{
  "inventory": {
    "medium": 0,
    "large": 2
  }
}

Final state

{
  "exchange_created": false,
  "awaiting_consent": true
}

FICTIONAL / RETURN / 002

When a return needs a review.

Synthetic

  1. Customer request

    I want to return an item delivered 35 days ago.

  2. Agent decision

    I can approve that return now.

  3. Human correction

    The 30-day window has passed. Escalate instead of approving.

  4. Corrected response

    This is outside the standard window. I have requested a review.

The policy behind the correction

Returns beyond 30 days require human review. Do not promise approval.

Corrected outcome

Human review requested. Return not approved.

Inspect starting and final state

Starting state

{
  "days_since_delivery": 35,
  "return_window_days": 30
}

Final state

{
  "return_approved": false,
  "review_requested": true
}

FICTIONAL / REFUND / 003

When a refund is already done.

Synthetic

  1. Customer request

    Can you refund the returned item?

  2. Tool result

    refund.lookup: existing refund completed

  3. Agent decision

    I will create another refund.

  4. Human correction

    Do not create a duplicate. Report the existing refund status.

  5. Corrected response

    A refund has already been completed; no additional refund was created.

The policy behind the correction

Check for existing refunds and never duplicate a completed refund.

Corrected outcome

Existing refund reported. No additional refund created.

Inspect starting and final state

Starting state

{
  "existing_refund": "completed",
  "refund_count": 1
}

Final state

{
  "refund_count": 1,
  "additional_refund_created": false
}

Fictional examples, for inspecting the format. An outcome of “success” means the corrected fictional workflow followed its policy. It does not mean a transaction completed or a model passed a test. These public examples are not a held-out benchmark or a licensed customer release.

MAKE THE NEXT STEP SPECIFIC

What examples would
help your agent?

Start with your email. Add a workflow or a question if you like; we can discuss the missing cases together.

Discuss a dataset pilot Have workflows to contribute?