Agent tools

What a coding agent can actually run in this checkout.

Each page names the command, quotes what it printed in this repository, and states what its report does not prove. Nothing here installs from npm. The project bootstrap scaffolds a working project from a checkout of this repository; the two names on the registry are still empty reservations, so ownership means copying source and upgrading means merging (site/brand.json, L-08). The MCP server is stdio and local only, and it inherits the authority of the process that starts it.

How a coding agent finds out what your CRM project actually contains

See what exists

One command that reads checked-in source and prints a deterministic JSON document describing what an application has composed: packages, the resolved capability graph, records and their…
Making an AI agent write a plan a second reader can check

Decide what to build

A file contract, a validator and a binder — not a planner and not a runtime.
Finding what is stale in a checkout before you pay for a full test run

Find what's broken

A read-only source-consistency check that answers what is structurally inconsistent or stale before you edit — a composition that no longer resolves, a plan bound to an application that…
Starting a new domain package without inheriting somebody else's domain

Create the right starting point

Two files, an identity, five empty declarations and a README — a package that passes validate, inspect and the conformance harness with no manual edit, and that models nothing.
Proving a package still fits the framework — and what that does not prove

Check it follows the rules

A generic conformance harness that composes a package into a throwaway copy of the project, boots the application twice, attaches and detaches it, and reports what the framework's own…
The review a change has to survive before anyone calls it done

Prove it works

Repository policy rather than a command: ten requirements for every feature PR, fifteen adversarial review categories a milestone is attacked with before it merges, a four-value job status…
Deleting a safety rule on purpose to see whether a test notices

Try to break it yourself

A falsification kit, not a mutation-testing tool.
Giving your coding agent the instructions, over MCP or as skills

Plug it into your agent

Two shipped harnesses with byte-identical skill files, two stdio MCP servers — one of them also hosted read-only over HTTP — and a stated contract for what a harness must provide: a shell,…

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. 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 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.