CARBON — Engineering ConfidenceUser Guide
CHAPTER 29 / 60 Pro

/carbon-networking

Run focused CARBON Networking testing and generate a branded networking report.

Fatima · Error UXSecurity & resilience

When to use it

Offline, retry, caching or timeout behavior is uncertain.

Before you start

Control one network condition at a time in an approved environment. Compare request order, stale responses, retry bounds and visible recovery. A stubbed failure is not a measurement of a real mobile network.

Try this in your coding agent.

/carbon-networking Review retry and offline behavior around the checkout API.

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

Offline and retry behavior

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 offline and retry behavior. 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 network stub: disconnect → change quantity twice → reconnect → inspect request order.

Report

A reconnect retries a stale cart update after a newer one. Real mobile-network behavior is outside this illustration.

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

A reconnect retries a stale cart update after a newer one.

Evidence to inspect

Local network stub: disconnect → change quantity twice → reconnect → inspect request order.

Still untested / not established

Real mobile-network behavior is outside this illustration.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For offline and retry behavior, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Local network stub: disconnect → change quantity twice → reconnect → inspect request order. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

Real mobile-network behavior is outside this illustration.

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 offline and retry behavior 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-networking result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-state →/carbon-reliability →

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