JTBD-PK-02 · Package developer
Depend on another package without importing its source
validated end to end. An automated test or a checked-in example proves the whole job. This is the only status that counts as evidence.
What the catalogue records
declared capabilities only. packages/delivery reaches packages/contracts through delivery-obligations@1, inside the caller's transaction. An undeclared reach, a wrong declared provider, a missing or mis-versioned dependency and a cycle are all startup failures naming the edge
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 Package developer
- Create and compose a custom local domain package — validated end to end
- Validate a package before booting it — partially supported
- Remove a package without losing its data — partially supported
- Scaffold a new package from a template — not supported
- Install a package from a registry or marketplace — not supported
- Run an untrusted package safely — not supported