---
name: carbon-confidence-init
description: "Initialize confidence engineering in a repository by creating the .confidence system map, risk register, claim ledger, eval folders, incident records, trace folders, and release report."
user-invocable: false
---

# Initialize Confidence Engineering

Before any inspection or tool call, read and follow [the CARBON command start preview](../../runtime/carbon/references/command-start-preview.md). Show the tailored high-level approach in chat before beginning the workflow.

Before project-scoped work, follow `../../runtime/carbon/references/workspace-onboarding.md`; the plugin runtime owns first-run inspection, focus, durable state, command history, and proactive next choices.

1. Resolve the installed CARBON plugin root as two directories above this `SKILL.md`, then run `bin/carbon-confidence-init` from the project root. It is idempotent and does not overwrite existing evidence.
2. Inspect the repository structure, README, package metadata, deployment config, AI/model call sites, prompts, retrieval, tools, and existing tests.
3. Replace the starter text in `.confidence/system-map.md` with the concrete system boundary and important dependencies you can verify.
4. Seed `.confidence/risks.yaml` with the highest-impact plausible risks. Do not fill it with generic boilerplate.
5. Seed `.confidence/claims.yaml` with falsifiable claims derived from the product's purpose and current change.
6. Run `bin/carbon-confidence-status` from the resolved plugin root and report what was initialized, what you learned, and what remains unknown.

If `$ARGUMENTS` names a feature or goal, make that the initial decision scope. Do not attempt to map the whole company when a feature boundary is enough.

Read [the evidence model](../../references/evidence-model.md) and [the output contract](../../references/output-contract.md) before filling the artifacts.

## Required HTML result

Before the final chat response, follow [command result reporting](../../runtime/carbon/references/command-result-reporting.md). Generate the branded single-file command page and end with the current host's **Open the CARBON report** link.
