Pre-launch. Not deployable to production. This page states what the tests prove and what is missing — nothing else.

Answers

Straight answers, and the questions we refuse.

Every answer below is assembled from the claims ledger: the sentences are the ledger's own, and each one carries the limitation that travels with it. The lede on each page summarises; the claim below it is quoted. Below them are 15 questions this project will not answer yet — a benchmark that has not been run, comparisons nobody measured, adoption numbers that do not exist — with the reason in each case.

Answered

Refused, and why

These have no honest answer in the ledger today. When one exists — when a benchmark runs, when the production spine lands — the question moves up the page. Until then this list is the answer.

Is it production-ready yet, and when will authentication, tenancy or PostgreSQL land?

L-01 and L-02 record the absences, but no claim or limitation carries a date, a milestone order or a commitment. 'Production Spine' is named as a track in L-02's text, not as a schedule, so any answer to the 'when' half would be invented.

What is the Successful Agent Build Rate — how often does a coding agent finish a working CRM with this?

L-03 states the benchmark has not been run and that any number quoted is not ours. A page shaped around the number would exist only to host a figure that does not exist. The accepted page 'is-there-a-benchmark-for-agent-built-crms' answers the meta-question honestly; this one cannot be answered at all.

How does this compare to Salesforce, HubSpot, Twenty, Odoo or a low-code CRM platform?

No claim or limitation makes any statement about another product. A comparison needs verified, dated competitor facts, and I have no internet access to establish them; docs/strategy/COMPETITOR_MAP.md exists but is strategy, not ledger evidence, so nothing in claims.json licenses a comparison sentence.

How long does it take an agent to build a CRM with this, and how fast is the framework?

C-22 states outright that wall-clock time varies by machine and is deliberately not claimed. The only timing in the ledger is C-23's 'about two seconds' for the fast falsify set, which is scoped to that command and cannot be generalised into a time-to-first-CRM.

How well does it scale — how many records, what throughput, what response times?

No claim or limitation measures performance or volume, and no load test exists on disk that I could cite. L-02 (SQLite only) constrains the answer but does not supply one.

Is it secure? Has it had a security review or penetration test?

The ledger records the absence of authentication (L-01) and states that audit is not tamper-evident and not a compliance control (C-16), but it makes no positive security claim and cites no review. A page titled 'is it secure' would invite an affirmative sentence that no C-xx supports.

Is it SOC 2 / GDPR / HIPAA compliant, and how do I service a DSAR?

L-09 says data governance is designed and unimplemented and that a data-subject access or deletion request cannot be serviced. There is no compliance programme, certification or control mapping in the ledger, so a compliance-shaped page would imply a process that does not exist. The honest fragment already lives in 'can-i-put-real-customer-data-in-it'.

How do I connect it to DocuSign, Stripe, HubSpot or my email provider?

A how-to page requires steps. C-09 and C-08 state those adapters do not exist and L-05 states no adapter sends anything to anyone, so every step would be fabricated. The negative version — 'what-integrations-exist' — is accepted instead.

How do I import or migrate my existing CRM data into it?

L-06 records that import, export, dedupe, merge and bulk edit do not exist. There is no path to document, and a migration guide is the single most damaging thing to invent for a system that has no export either.

Does it have reporting, dashboards, forecasting or pipeline analytics?

No claim or limitation covers reporting or aggregation. The sentence 'reporting or aggregation over generated modules' is absent appears in site/assets/llms.txt prose, not in claims.json, so under the rule that a public sentence comes only from the ledger there is nothing to answer with. Worth adding as an L-xx if this question recurs.

Which coding agent works best with it — Claude Code or Codex? Which model should I use?

Nothing in the ledger compares harnesses or models, and the benchmark that would measure it has not been run (L-03). Any preference stated would be a guess presented as a measurement.

What does it cost, what licence does it ship under, and is there a free tier?

L-07 establishes there is nothing to sign up for, but licence status is not a ledger entry — README.md says 'MIT today' with a final confirmation gated on an explicit human decision, which is precisely the kind of sentence that must not be frozen into a retrievable page ahead of that decision.

Who uses this in production, how many teams have adopted it, how many stars or downloads?

No adoption, usage or popularity fact exists anywhere in claims.json, and L-08 records that nothing is published, so there are no download numbers to have.

Can I give a coding agent a business goal and have it build the whole CRM unattended?

C-01 is scoped to generated CRUD with workflows and approvals still handwritten, and C-15 states explicitly that nothing executes a plan. An unattended end-to-end build is the exact capability the unrun benchmark (L-03) was designed to measure, so claiming it would be claiming the benchmark result.

Does an LLM decide anything at runtime — is this an 'AI CRM'?

Tempting, and half-answerable: C-03 says commercial policy is deterministic code rather than a model's judgement and C-07 says scoring is deterministic weighted rules rather than machine learning. But no claim or limitation states that nothing calls a model at request time anywhere in the runtime — that sentence lives in PRODUCT.md, llms.txt and OBJECTIONS.md, not in the ledger — so a page under this question would answer wider than its evidence. It becomes proposable the moment a C-xx covers the runtime as a whole.