# Confidence Engine

Read these project instructions before making changes:

- @.claude/project-context.md
- @.claude/architecture-guardrails.md
- @.claude/ux-guidelines.md
- @.claude/working-rules.md

## Current working principle

The Confidence Engine helps a person move from uncertainty towards justified
confidence by asking one simple, useful question at a time.

The graph preserves the state of the reasoning. The conversation is the primary
user experience.

## Before changing anything

1. Inspect the current branch and working tree.
2. Read the relevant implementation and tests.
3. Identify whether the request concerns:
   - reasoning behaviour;
   - API/data contracts;
   - or presentation only.
4. Respect the boundaries in the imported instructions.
5. Make the smallest change that satisfies the task.

Do not assume an architectural redesign is wanted.

## Live experiment harness rule

When running reasoning experiments, use the canonical harness at
`tests/graph/live-update-experiment-helper.cjs`. Never create a new harness,
enumerate `/api/tags`, probe localhost, or discover/substitute models during
normal reasoning experiments.

## Standard validation

For UI-only work, normally run:

```bash
npm test -- --run tests/ui/scenario-form.test.jsx
npm run lint
npm run build
```

Run additional focused tests only when relevant files are affected.

Do not run Ollama, Playwright, the full test suite, or evaluator suites unless the
task explicitly requires them.