How it works

# A coding agent gets a method, not a blank repository.

Accordo makes discovery, planning, construction and proof distinct steps so an agent does not confuse generated code with a working business system.

The loop

## See → plan → build → prove.

Each rail answers one question and produces machine-readable evidence.

1. See `npm run crm -- app inspect --json` reports the checked-in composition and its limitations.

2. Plan A checked Solution Plan binds requirements to that composition.

3. Build Packages, actions, workflows and policy remain explicit source.

4. Prove technical health `npm run crm -- project verify --json` composes the project and runs its declared technical authorities; it does not run a business journey.

5. Prove one business journey `npm run crm -- scenario run lead-to-won --json` executes that named scenario and publishes linked evidence; choose the scenario that matches the job.

Implementation truth stays separate. Current proof and limitations come from the generated [claims ledger](evidence.html), not from this product description.

Ownership

## The result is not attached to an Accordo account.

The published scaffolder copies framework source into the project. There is no hosted Accordo runtime to keep contacting; upgrades require merging changes into your owned copy.

---
Canonical: https://accordo.dev/how-it-works.html
Implementation evidence: https://accordo.dev/claims.json
Build provenance: https://accordo.dev/version.json