Pre-launch. Not deployable to production. This page states what the tests prove and what is missing — nothing else.

JTBD-DS-09 · Delivery & Service

Collect customer acceptance on deliverables

partially supported. Part of the job works and is proved; the rest is named rather than implied. Read what is excluded before planning around it.

What the catalogue records

M14b2: Deliverables gated on server-authoritative execution state, and an immutable Acceptance Request that freezes its exact scope with a SHA-256 fingerprint the evidence binds to. A pending request freezes its milestone; a settled scope cannot be re-asked, and the fingerprint covers the body of work alone so retyping the customer label buys no second answer; a rejection preserves completed execution and forces a governed replan over genuinely new work. Partial, and narrowly so: this records what a user actor asserted a customer said. It is not an authenticated customer action, not a legal signature, not a verified identity and not authorization to bill — real customer actors are gated by the Production Spine

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 is local-development-only: there is no authentication, tenancy or RBAC, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.

Other jobs in Delivery & Service

All 12 jobs in Delivery & Service · the whole catalogue