Verify the solution against defined acceptance

What the catalogue records

Quality Gates, crm package validate, the test suites and the clean-clone run are real and enforced, and DX10 now closes the last hop from a plan to its proof: accordo solution verify <plan.json> --evidence <evidence.json> --json reports, per requirement, whether it is proven, partial, blocked, unevidenced, stale or unverified, from authorities that ran in the same invocation. A requirement id is derived from the plan, the evidence document has no status field, and file exists can never satisfy a behavioural requirement — tests/implementation-evidence.test.js, tests/solution-verify.test.js. Still partial, and deliberately so: it grades the acceptance a plan wrote down and cannot catch one it omitted, manual requirements stay unverified, no checked-in plan verifies today, and there is still no automated goal-to-acceptance runner (AX3)

Evidence

Proved by these tests, which run on every push:

What this status does not mean

A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework ships no authentication, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.

Other jobs in Agent experience

• Discover installed packages, capabilities and policies — validated end to end
• Extend the CRM for a goal without patching the kernel — validated end to end
• Turn a business objective into a reviewable solution plan — partially supported
• Build the solution as checked-in, customer-owned source — partially supported
• Report unavailable capabilities honestly — partially supported
• Analyse a funnel and identify a drop from a goal — not supported
• Propose an optimization campaign from an insight — not supported
• Deploy, observe and fix a solution in production — not supported

All 10 jobs in Agent experience · the whole catalogue