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 connects the records of one customer commercial lifecycle.

  • 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 ships: the framework authenticates nobody. Production Spine v1 (ADR-038) gives the framework verified identity, organizations and memberships, server-authoritative authorization and one tenant per application instance — so tenancy and authorization now exist and are enforced. What does not exist is authentication: no login, password, session or OIDC implementation ships, and a deployment must supply the adapter that verifies the request. Production mode refuses to start without one. In local-development mode an actor header is accepted as an assertion and is not an identity, which is the default developer posture. This is not shared-database multi-tenancy and it is not a readiness claim.
  • Not shared-database tenancy. createAccordoAppAsync can boot one tenant onto dedicated PostgreSQL databases. Shared-database row-level tenancy is not implemented, and this is not a production-readiness claim.
  • Timers exist; a service that runs them for you does not. Durable jobs, a transactional outbox and scheduled asks exist for self-hosted applications that explicitly start a worker. Nothing autostarts; a timer opens an ask, never makes a decision, and no managed worker service or recurrence is included.
  • No email, calendar or marketing integrations. An in-memory notification provider contract exists. MK1 marketing records supplied funnel observations and human-reviewed proposals only; it has no sending, publishing or spending path.
  • 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 means vendored source: there is no framework dependency to bump. The published create-accordo@0.1.0 scaffolds vendored source; it is the August 19 snapshot, not the current repository feature set. Use a current source checkout for the capabilities described here; upgrades require merging source (L-08). The framework is copied into the project, not installed as a framework library dependency. The accordo npm name is an empty reservation; the @accordo scope is claimed and deliberately empty.

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