CARBON — Engineering ConfidenceUser Guide
CHAPTER 25 / 60 Pro

/carbon-reliability

Run focused CARBON Reliability testing and generate a branded reliability report.

Fatima · Error UXSecurity & resilience

When to use it

You care about recovery and consistent behavior when dependencies fail.

Before you start

Define safe retry and idempotency expectations. Use local stubs or disposable fixtures for timeouts and partial failures. Record whether the system recovers without losing or duplicating work.

Try this in your coding agent.

/carbon-reliability Check how checkout handles timeouts and repeated submit attempts in a local test.

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

Checkout recovery

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 checkout recovery. 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: Local stub accepts request, delays response; retry uses a new request identifier.

Report

Retrying after a timeout can create an ambiguous order state. No production charge or order is created.

CARBON

Example report

Illustration
Failure → evidence → recovery
Failure → evidence → recovery — TestBucks teaching screen

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

  1. Failed request
  2. Preserved state
  3. Safe retry

Illustrated outcome

Retrying after a timeout can create an ambiguous order state.

Evidence to inspect

Local stub accepts request, delays response; retry uses a new request identifier.

Still untested / not established

No production charge or order is created.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For checkout recovery, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Local stub accepts request, delays response; retry uses a new request identifier. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

No production charge or order is created.

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 checkout recovery 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-reliability result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/failure →/carbon-networking →

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