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, and a stated contract for what a harness must provide — which is a shell, an exit code, a JSON parser and file…
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, 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 task engine, no reminders. One follow-up Task is created inside lead qualification. 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.