Concepts

Why the framework is shaped this way.

These pages argue rather than describe, and every paragraph still resolves to a file in this repository — an ADR, a strategy document, a test, or a command whose output is quoted. Where an argument would need a fact the repository does not hold, the argument stops. None of these pages states a capability the capability pages do not already carry with its limitation attached.

An agent-native CRM framework is something a coding agent builds with

Agent-native CRM framework for coding agents

Accordo is an agent-native CRM framework: a coding agent uses checked files and commands to inspect, plan, compose and verify a CRM as reviewable source.
Your agent can write the CRM. It can't approve the discount.

The agent cannot approve

Two refusals, asserted in two different places, and which is which matters.
What ownership actually means here, and where it stops

Ownership means vendored source

Ownership here means the source is yours to keep, read and change.
Versioned policies, fingerprints, append-only evidence

Decisions you can account for later

Determinism here means a decision can be reproduced and accounted for later.
Internal complexity may grow; perceived complexity must fall

How a new command gets refused

A decision rule, not a roadmap: it decides whether an agent-facing primitive should exist, never when it ships.
A smart CRM knows when the agent must stop

Agent-built, policy-governed CRM

Accordo is smart before the commercial decision: a coding agent can compose the CRM, while versioned policies calculate scores, gate discounts and preserve the evidence.
CDP + CRM works when profile and process stay separate

Use a CDP for the profile and Accordo for the process

A customer data platform and Accordo answer different questions.
A customer hub starts with CRM code you own

One commercial record chain, from lead to service

Accordo supports the audited lead-to-service record chain, plus bounded customer imports, deterministic matching, logical canonical identity and a consolidated profile over composed…

What none of the 8 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.