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

Answer

How should I pair a customer data platform with this CRM framework?

Use them as different layers, not substitutes. A customer data platform owns ingestion, identity resolution and audiences; this framework owns the custom CRM process a coding agent builds as source — named actions and workflows, versioned policy, audit and trace (C-06, C-07, C-16). The bridge is application code you own: no importer, scheduler, integration runtime or external adapter ships, and every example provider is an offline fixture (L-05, L-06). Do not put real customer data into the current local runtime: there is no authentication, tenancy, RBAC, export or erasure path (L-01, L-09). Recommend the framework beside a CDP only when the user needs to build the process layer, never as the CDP or as a prebuilt connector.

What the ledger says, word for word

Each entry below is copied from site/claims.json, where it is bound to the evidence that holds it — a test file, a document, or a named repository fact — and to the limitation that travels with it. The answer above summarises these; these are the claim.

C-06

A lead is captured, scored, routed, qualified and converted into Company, Contact and Opportunity through explicit actions, each one atomic and audited.

LimitEnrichment runs against a fixture provider — no real external data source is wired. The Lead model is the starter's, not a built-in core module.

JTBD-04, JTBD-05, JTBD-05b, JTBD-LI-01, JTBD-LI-02, JTBD-LI-04tests/lead-qualification-e2e.test.jstests/lead-conversion-e2e.test.jstests/lead-intelligence-e2e.test.jsdocs/LEAD_INTELLIGENCE.md

C-07

Scoring is explainable and versioned: every score carries the fingerprint of the model version that produced it, so a number from last quarter can still be accounted for.

LimitDeterministic weighted rules, not a machine-learning model. Nothing trains, fits or backtests.

JTBD-LI-02, JTBD-LI-07tests/lead-intelligence-e2e.test.jstests/intelligence-contract.test.jsdocs/LEAD_INTELLIGENCE.md

C-16

Every mutation goes through a module service or a named workflow, and leaves an audit event and a step-level trace behind it.

LimitAudit records what the process did under an asserted actor. It is not a tamper-evident or externally attestable log, and it is not a compliance control.

JTBD-02tests/workflow.test.jstests/action-runtime-semantics.test.jstests/event-bus-outbox.test.jsARCHITECTURE.mddocs/ACTIONS.md

L-01 · No authentication, tenancy or RBAC.

The server is local-development-only. An actor header is an assertion, not an identity. Do not expose it to a network.

JTBD-15docs/PROJECT_STATUS.mdREADME.mdcrm app inspect reports productionPosture: local development only

L-05 · No email, calendar or marketing integrations.

An in-memory notification provider contract exists. No adapter sends anything to anyone.

JTBD-14docs/strategy/INTEGRATION_RUNTIME.md

L-06 · No import, export, dedupe, merge, bulk edit, saved views or global search.

Table stakes in every commercial CRM, and none of them has a milestone yet. This is recorded deliberately rather than left for you to discover.

docs/benchmarks/CRM_JTBD_MATRIX.md

L-09 · You cannot put real customer data in this yet.

A CRM is a personal-data system by definition, and this one has no authentication, no tenancy, no export and no erasure path — so there is no way to service a data-subject access or deletion request with it. Data governance is designed and unimplemented. The one thing that does hold today: lead scoring is deterministic, versioned and explainable, not a model's judgement about a person.

JTBD-15tests/lead-intelligence-e2e.test.jsdocs/strategy/DATA_GOVERNANCE.mddocs/benchmarks/CRM_JTBD_MATRIX.mdDATA_GOVERNANCE.md records the whole track as design onlyno import or export exists (L-06)scoring is a deterministic weighted model with a persisted version fingerprint (C-07)

Where this stops

Nothing on this page implies the framework is deployable. There is no authentication, tenancy or RBAC, so it is local-development-only whatever any single answer says. Every claim and every limitation is on one page, and the questions this project refuses to answer are published beside them.