Open source. Not deployable to production. This page states what the tests prove and what is missing — nothing else.

Glossary

The vocabulary, defined before it is argued.

Each page below opens with a definition a reader — or a model — can quote whole, then states how the term works in this repository and where that stops. A definition here never claims a capability the ledger does not carry: where a term names something this framework does not do, the page says so in the same breath, with the limitation id beside it.

  • What is a CRM framework?

    CRM framework, defined

    A CRM framework is source code a development team composes into its own CRM application: the framework supplies the runtime contracts — records, services, workflows, policies — and the…

  • What is an agent-built CRM?

    Agent-built CRM, defined

    An agent-built CRM is a CRM application whose source a coding agent composes against a framework's contracts, leaving reviewable code the operator owns rather than configuration inside a…

  • What is a customer hub?

    Customer hub, defined

    A customer hub is a system in which the records of one customer's commercial life — lead, deal, quote, order, contract, delivery, service — connect through explicit identifiers, so…

  • What is CPQ? Configure, price, quote, defined

    CPQ, defined

    CPQ stands for configure, price, quote: software that assembles a quote from a product catalog, prices it under consistent server-side rules, and gates discounts through approval before…

  • What is a versioned policy?

    Versioned policy, defined

    A versioned policy is a business rule stored as an immutable, identified definition — a name, a version and a fingerprint of its source and configuration — so that every decision records…

  • What is a deterministic workflow?

    Deterministic workflow, defined

    A deterministic workflow is a multi-step business process whose transitions are explicit code with defined outcomes: the same inputs under the same policy version produce the same result,…

  • What is a human approval boundary?

    Human approval boundary, defined

    A human approval boundary is a point in an automated process where the system refuses to let software — including an AI agent — record the final decision, and stops until a named human…

  • CDP vs CRM: profile systems and process systems

    CDP vs CRM, the split

    A customer data platform (CDP) assembles one profile per person or account from records and events ingested across many systems — identity resolution, audiences, destination sync.

  • What is a JTBD matrix, and how does it evaluate a CRM?

    JTBD matrix, defined

    A JTBD (jobs-to-be-done) matrix is an evaluation instrument that lists the jobs a buyer hires software to do and records, per job, whether the system can complete it and on what evidence.

  • What is quote-to-cash, and where does this one stop?

    Quote-to-cash, defined

    Quote-to-cash (Q2C) is the commercial process that runs from configuring and pricing a quote, through discount approval, signature and order, to contract activation, fulfilment, invoicing…

What none of the 10 pages above means

These pages describe this repository at this commit. None of them implies the framework is deployable, and none of them is a roadmap: nothing that is not merged appears on this site, in any tense.

  • 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.
  • SQLite only. Persistence is Node's built-in SQLite adapter. PostgreSQL is on the Production Spine track and is not implemented.
  • No scheduler, no reminders, nothing on a timer. Follow-up Tasks and an Activity timeline are one shared model that a person moves by hand: a due date changes no state. There is no recurring work, no delayed workflow, no queue — so nothing fires on a renewal notice period either.
  • No email, calendar or marketing integrations. An in-memory notification provider contract exists. No adapter sends anything to anyone.
  • The build benchmark has not been run. The protocol is designed and published; no Successful Agent Build Rate exists yet. Any number you see quoted for this project is not ours.
  • Ownership today means copying source, not installing a dependency. There is a project bootstrap and there is no published package, and the two are different facts. The repository's bootstrap command scaffolds a project that boots, reports `valid` from `app inspect` and exits 0 from `project doctor`, offline and with no install — run from a checkout of this repository. The package published under the reserved npm name is still an empty 0.0.1 placeholder, so the `npm create` route installs nothing until a human publishes it. Either way the framework is vendored into the project rather than depended on by version: you own the result outright, and upgrading means merging, not bumping.

Every claim and every limitation is on one page, and the questions this project refuses to answer are published beside them.