Report unavailable capabilities honestly

What the catalogue records

the JTBD matrix and package metadata make the honest answer available, and two commands now make part of it machine-checked rather than optional: the service scenario publishes each unavailable capability as a stated false it earned by attempting the operation, and accordo solution verify refuses to let an agent declare a requirement met — the evidence document has no status field, a downgrade needs a reason, and a manual requirement can never read as proof. Still partial: nothing enforces that an agent writes an evidence document at all, which is why the Skill states it as a rule

Evidence

This row carries no test path of its own in the structured index. The matrix records the evidence for it in a block shared with neighbouring rows, which jobs.json does not split per row — so read docs/benchmarks/CRM_JTBD_MATRIX.md for it. The status above was set from that evidence, not from its absence.

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
• Verify the solution against defined acceptance — 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