<a id="packages"></a>

# Packages

Choose a package to see how to set it up, try an example, and use it in your project.

<a id="foundation-and-tools"></a>

## Foundation and tools

*   [@dads-framework/dev](https://dadsframework.dev/docs/package-dev#try-it) Local development slots and conservative Git worktree lifecycle.
*   [@dads-framework/plugin](https://dadsframework.dev/docs/package-plugin#try-it) The build-time plugin contract: `definePlugin` declares what a plugin contributes and depends on, `composeApp` orders and checks a plugin list and returns what the host wires, and every effect a plugin starts is disposed with its scope.
*   [@dads-framework/toolbox](https://dadsframework.dev/docs/package-toolbox#try-it) Explains Dads ownership and runs deterministic agent workflows.
*   [create-dads](https://dadsframework.dev/docs/package-create-dads#try-it) Guides new and existing applications through deterministic Dads initialization.

<a id="contracts-and-access"></a>

## Contracts and access

*   [@dads-framework/access](https://dadsframework.dev/docs/package-access#try-it) The TypeScript authoring kit for relationship-based authorization: `access()`, entity handles, combinators, and the emitter that writes committed `generated/*.zed` fragments. SpiceDB schema is generated from these definitions.
*   [@dads-framework/contract](https://dadsframework.dev/docs/package-contract#try-it) HTTP-kit wire vocabulary every surface shares: the request-id header name,

<a id="server"></a>

## Server

*   [@dads-framework/audit](https://dadsframework.dev/docs/package-audit#try-it) Assembles row-level audit, request retention, and client diagnostics with the HTTP, jobs, and Postgres packages. Applications configure the tables, exclusions, and scope dimensions captured by the audit trigger.
*   [@dads-framework/audit-actor](https://dadsframework.dev/docs/package-audit-actor#try-it) Who is acting, in one dependency-free place: the `AuditActor` vocabulary, the exact JSON the Postgres `dads.audit_actor` setting carries, and the `AsyncLocalStorage` context that carries it. It lives apart from `@dads-framework/audit` because the postgres kit (attributed pool), the http kit (request scope), and the job-queue kit (system actor per job) all need the actor and none of them may depend on the audit kit to get it. **Read the rest when:** establishing an actor context at a new seam, or asking how an actor reaches the database.
*   [@dads-framework/authorization](https://dadsframework.dev/docs/package-authorization#try-it) SpiceDB checks and snapshots, Postgres outbox and catalog.
*   [@dads-framework/authorization-migration](https://dadsframework.dev/docs/package-authorization-migration#try-it) The authorization schema journal: ordered `NNNN_slug` schema snapshots with the relationship steps that keep access intact, applied once each, plus the patch-form authorization changes and their scaffolding.
*   [@dads-framework/cross-domain-references](https://dadsframework.dev/docs/package-cross-domain-references#try-it) Builds reconciliation queries and reports dangling references using the database client supplied by the application.
*   [@dads-framework/csv](https://dadsframework.dev/docs/package-csv#try-it) Encodes rows as CSV using RFC-style field quoting and LF line endings.
*   [@dads-framework/email-delivery](https://dadsframework.dev/docs/package-email-delivery#try-it) Binds the Postgres adapter to the durable email outbox and composes the delivery and sweep jobs over it.
*   [@dads-framework/email-sender](https://dadsframework.dev/docs/package-email-sender#try-it) Send outbound email. Callers hold one `EmailSender` and call `send()`; the
*   [@dads-framework/email-templates](https://dadsframework.dev/docs/package-email-templates#try-it) Turns a declarative email template into the HTML and plain-text pair a message
*   [@dads-framework/errors](https://dadsframework.dev/docs/package-errors#try-it) `DomainError` (discriminated `kind` + stable SCREAMING\_SNAKE `code`) with
*   [@dads-framework/event-bus](https://dadsframework.dev/docs/package-event-bus#try-it) The `EventBus` seam for asynchronous cross-domain communication: domains
*   [@dads-framework/feature-flags](https://dadsframework.dev/docs/package-feature-flags#try-it) Defines feature flags, per-tenant audiences, revision-checked changes, and effective access. Its HTTP and PostgreSQL bindings expose and persist flag state.
*   [@dads-framework/http](https://dadsframework.dev/docs/package-http#try-it) Defines HTTP routes and assembles liveness and readiness probes over application-provided checks.
*   [@dads-framework/identity](https://dadsframework.dev/docs/package-identity#try-it) Owns vendor-neutral account, session, and email delivery contracts.
*   [@dads-framework/identity-better-auth](https://dadsframework.dev/docs/package-identity-better-auth#try-it) Binds identity HTTP requests to Better Auth, PostgreSQL sessions, and account invitations.
*   [@dads-framework/job-queue](https://dadsframework.dev/docs/package-job-queue#try-it) `JobQueue`: register typed definitions, start recurring schedules, enqueue
*   [@dads-framework/migrations](https://dadsframework.dev/docs/package-migrations#try-it) The Postgres migration runner: discovers `*.migration.ts` files in the folders a `MigrationWorkspace` names, applies pending ones in dependency order under an advisory lock, and journals and checksums what ran. Also ships the `dads-migrate` bins and the compatibility rehearsal.
*   [@dads-framework/object-storage](https://dadsframework.dev/docs/package-object-storage#try-it) Put, get, delete, and sign download or single-PUT upload URLs for object bytes. The composition
*   [@dads-framework/pdf](https://dadsframework.dev/docs/package-pdf#try-it) `PdfRenderer` turns a declarative pdfmake definition into bytes. No Chrome.
*   [@dads-framework/postgres](https://dadsframework.dev/docs/package-postgres#try-it) Owns the Postgres pool and the Drizzle instance (`createPostgresConnection`),
*   [@dads-framework/postgres-access](https://dadsframework.dev/docs/package-postgres-access#try-it) Postgres backend for the composed access model and transactional relationship facts. Status: Trusted experimental.
*   [@dads-framework/runtime](https://dadsframework.dev/docs/package-runtime#try-it) Provides the clock, request work accounting, and diagnostic sinks used across server kits.
*   [@dads-framework/telemetry](https://dadsframework.dev/docs/package-telemetry#try-it) Opt-in OpenTelemetry trace export for Node HTTP and Postgres.
*   [@dads-framework/tenants](https://dadsframework.dev/docs/package-tenants#try-it) Tenant lifecycle, membership authorization, and verified-account invitations.

<a id="client"></a>

## Client

*   [@dads-framework/client-feature-flags](https://dadsframework.dev/docs/package-client-feature-flags#try-it) Context-keyed feature state in the browser and the React hooks that read it.
*   [@dads-framework/client-request-transport](https://dadsframework.dev/docs/package-client-request-transport#try-it) The one HTTP chokepoint for `web`. Every call the app makes to the
*   [@dads-framework/client-telemetry](https://dadsframework.dev/docs/package-client-telemetry#try-it) Where a client reports a fault that never became a request: a render that
*   [@dads-framework/client-xlsx](https://dadsframework.dev/docs/package-client-xlsx#try-it) The one .xlsx seam for the web app. Features describe a workbook as a

<a id="web"></a>

## Web

*   [@dads-framework/copy](https://dadsframework.dev/docs/package-copy#try-it) The machinery every word a product says goes through, and no product's words.
*   [@dads-framework/design-tokens](https://dadsframework.dev/docs/package-design-tokens#try-it) Default palette and semantic roles in the DTCG design token format.
*   [@dads-framework/styles](https://dadsframework.dev/docs/package-styles#try-it) Default web theme, exposed as CSS and Tailwind utilities.
*   [@dads-framework/ui](https://dadsframework.dev/docs/package-ui#try-it) Composable React controls, display primitives, tables, page layouts, and navigation.

<a id="testing"></a>

## Testing

*   [@dads-framework/path-aliases](https://dadsframework.dev/docs/package-path-aliases#try-it) Resolves the TypeScript path aliases declared across one tsconfig extends chain to files, over a file system port two providers implement.
*   [@dads-framework/testing](https://dadsframework.dev/docs/package-testing#try-it) Bootstraps, plans, runs, and explains declared verification tasks through a native JSON boundary. Its Nx adapter imports recipes and adapts live targets.
*   [@dads-framework/testing-vitest](https://dadsframework.dev/docs/package-testing-vitest#try-it) Binds the Dads alias resolver to Vite and Vitest as a pre-resolution plugin, without an Nx runtime dependency.

<a id="native-testing-runtimes"></a>

## Native testing runtimes

*   [@dads-framework/testing-native-darwin-arm64](https://dadsframework.dev/docs/package-testing-native-darwin-arm64#try-it) Distributes the macOS arm64 dad-test executable.
*   [@dads-framework/testing-native-darwin-x64](https://dadsframework.dev/docs/package-testing-native-darwin-x64#try-it) Distributes the macOS x64 dad-test executable.
*   [@dads-framework/testing-native-linux-arm64-gnu](https://dadsframework.dev/docs/package-testing-native-linux-arm64-gnu#try-it) Distributes the Linux arm64 glibc dad-test executable.
*   [@dads-framework/testing-native-linux-x64-gnu](https://dadsframework.dev/docs/package-testing-native-linux-x64-gnu#try-it) Distributes the Linux x64 glibc dad-test executable.
*   [@dads-framework/testing-native-win32-x64](https://dadsframework.dev/docs/package-testing-native-win32-x64#try-it) Distributes the Windows x64 dad-test executable.

Canonical page: <https://dadsframework.dev/docs/packages>
