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

Answer

What do I actually own, and how do I install it?

You own the source, and today that means copying it: there is a project bootstrap that runs from a checkout of the repository and no published package: the repository's bootstrap command scaffolds a project that boots, inspects and passes the project doctor, while the reserved `npm create` name still reaches an empty placeholder and installs nothing. Either way the framework is vendored into the project, so upgrading means merging, not bumping a version (L-08). What you are left with is a Node application with zero third-party runtime dependencies — Node 22 and a checkout, no build step, no bundler (C-17) — though that property belongs to the framework, not to whatever you add on top of it. A domain package you author attaches and detaches with the kernel's fingerprint unchanged and reaches another package only through a declared capability (C-13), but there is no scaffold, registry, marketplace or sandboxing, package code runs with the host process's authority, and detaching leaves its data behind. There is nothing to sign up for: no hosted CRM, no free tier, no account (L-07).

What the ledger says, word for word

Each entry below is copied from site/claims.json, where it is bound to the evidence that holds it — a test file, a document, or a named repository fact — and to the limitation that travels with it. The answer above summarises these; these are the claim.

C-17

Zero third-party runtime dependencies. Node 22 and a checkout — no build step, no bundler, no framework underneath your framework.

LimitDevelopment dependencies and the eventual PostgreSQL adapter are separate questions. Having no runtime dependencies is a property of the framework, not of whatever you add on top of it.

tests/api.test.jsARCHITECTURE.mdAGENTS.mdpackage.json has no dependencies fieldSQLite via node:sqlitethe HTTP server, test runner and database adapter are all Node built-ins

C-13

A customer-authored domain package attaches and detaches with the kernel's fingerprint unchanged, and reaches another package only through a capability it declares.

LimitNo scaffold, no registry, no marketplace, and no sandboxing — package code runs with the host process's authority. Detaching leaves its data behind; there is no uninstall.

JTBD-PK-01, JTBD-PK-02tests/package-contract.test.jstests/custom-package-e2e.test.jstests/contracts-registry-review.test.jsdocs/PACKAGE_AUTHORING.md

L-08 · 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.

tests/project-bootstrap.test.jsdocs/PROJECT_STATUS.mddocs/plans/project-bootstrap-installability.mdthe project bootstrap writes a project from an empty directory, dry-run unless --applytests/project-bootstrap.test.js bootstraps into a temporary directory and then runs app inspect, project doctor and the generated project's own checks against the resultsite/brand.json records the registry status and the source status as two separate fields, and scripts/distribution-check.js fails if either disagrees with the treethe published 0.0.1 tarball is an empty name reservation and this repository publishes nothing

L-07 · This is a framework, not a product you sign up for.

There is no hosted CRM, no free tier and no account. The output is an application in your repository that you run.

PRODUCT.mddocs/strategy/CATEGORY.md

Where this stops

Nothing on this page implies the framework is deployable. There is no authentication, tenancy or RBAC, so it is local-development-only whatever any single answer says. Every claim and every limitation is on one page, and the questions this project refuses to answer are published beside them.