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

CRM job catalogue

Package developer

Custom Package Authoring v1, M13

7 jobs in this area. 2 validated end to end, 2 partially supported, 3 not supported.

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.

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.

technically supported The primitives exist but no test proves the job end to end, so it is not claimed as working.

not supported No implementation and no test. It would have to be built. This is the default status in the catalogue — a row moves out of it only when a test proves it.

JTBD-PK-01 · Create and compose a custom local domain package

validated end to end

a customer-authored package attaches through the identical definePackage contract, works over the generic API, and detaches — with every kernel file fingerprinted before and…

JTBD-PK-02 · Depend on another package without importing its source

validated end to end

declared capabilities only. packages/delivery reaches packages/contracts through delivery-obligations@1, inside the caller's transaction. An undeclared reach, a wrong declared…

JTBD-PK-03 · Validate a package before booting it

partially supported

crm package validate|inspect runs the startup validator, reports collisions and private kernel imports, and exits non-zero. It imports and executes the package's own module body:…

JTBD-PK-04 · Remove a package without losing its data

partially supported

removing the import removes actions, schema block and Admin section; the tables and rows are left untouched. There is no uninstall, no data migration and no cleanup command —…

JTBD-PK-05 · Scaffold a new package from a template

not supported

crm package new deliberately deferred until a third package settles the file shape

JTBD-PK-06 · Install a package from a registry or marketplace

not supported

no registry, publication, remote install, auto-update, signing or hot loading. Packages are checked-in source, by design

JTBD-PK-07 · Run an untrusted package safely

not supported

and not planned at this layer. Repository source is trusted: a package's module body, actions and policies run in-process with full authority, and the consumer name passed when…

What a status here does not mean

These statuses describe this repository at this commit. None of them implies the framework is deployable: there is no authentication, tenancy or RBAC, so it is local-development-only whatever any row says. Every claim and every limitation is on one page.

All 149 catalogued jobs · /jobs.json · the claims ledger