CARBON — Engineering ConfidenceUser Guide
CHAPTER 31 / 60 Pro

/carbon-data

Run focused CARBON Data testing and generate a branded data report.

Arjun · Data integritySecurity & resilience

When to use it

A value changes incorrectly across computation or persistence.

Before you start

Trace a synthetic record through UI, API and storage. Compare precision, rounding, validation, transactions and import/export round trips; preserve evidence of both the input and resulting value.

Try this in your coding agent.

/carbon-data Check order totals and currency handling in src/orders using synthetic fixtures.

Replace sample paths with your project. Slash names are shorthand; your host may use a plugin prefix or a skill picker. Invocation help →

ILLUSTRATIVE WALKTHROUGH

Order-total consistency

An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.

  1. 01Read context
  2. 02Investigate
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing order-total consistency. I’ll keep the scope and permissions explicit.

Investigate

Follow the weakest evidence link and record what remains blocked.

Show evidence

Here is the evidence trail to inspect: Fixture: three fractional-price items → compare UI, API and persisted amount.

Report

The displayed total and stored total use different rounding rules. Synthetic fixtures only; no customer records.

CARBON

Example report

Illustration
Follow the cart state
Follow the cart state — TestBucks teaching screen

TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.

  1. Cart input
  2. Totals & state
  3. Checkout evidence

Illustrated outcome

The displayed total and stored total use different rounding rules.

Evidence to inspect

Fixture: three fractional-price items → compare UI, API and persisted amount.

Still untested / not established

Synthetic fixtures only; no customer records.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For order-total consistency, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Fixture: three fractional-price items → compare UI, API and persisted amount. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

Synthetic fixtures only; no customer records.

The next decision

Decide whether the evidence calls for a focused check, a reviewed fix or more context. Do not convert a plausible example into a verified finding.

Adapt the example to your project

  1. Replace order-total consistency with a real feature, path or decision in your project.
  2. State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
  3. Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-data result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-state →/carbon-api →

Content checked against the local command definition: skills/carbon-data/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.