Host lifecycle

Compose connection, plan review, apply, receipt-bound cleanup, and disconnect actions into a host-owned domain row and product lifecycle.

This integration level keeps DomainKit’s controllers and dialogs while your application owns the outer lifecycle row and decides when each action is available.

import { Cleanup, Connection, Provisioning } from "@domainkit/react";

export function DomainActions({ domain, records, receiptId }) {
  const controller = Connection.useController(domain);
  if (controller.state._tag !== "Connected") {
    return <Connection.Status state={controller.state} />;
  }

  return (
    <Connection.Root status="Connected">
      <Cleanup.Flow connection={controller.state} receiptId={receiptId} />
      <Connection.DisconnectDialog
        connection={controller.state}
        controller={controller}
      />
      <Provisioning.Flow
        connection={controller.state}
        records={records}
        showRecords={false}
      />
    </Connection.Root>
  );
}

Installation

npm install @domainkit/react domainkit effect @effect/atom-react react react-dom

pnpm add @domainkit/react domainkit effect @effect/atom-react react react-dom

yarn add @domainkit/react domainkit effect @effect/atom-react react react-dom

bun add @domainkit/react domainkit effect @effect/atom-react react react-dom

Lifecycle ownership

Provisioning and cleanup are separate reviewed operations:

1. Provisioning.Flow requests an exact create / noop / conflict plan.
2. The user authorizes that plan’s digest before the host applies it.
3. The host persists the returned receipt, including partial results.
4. Cleanup.Flow plans deletion from that receipt and requests separate authorization.

Do not treat disconnecting a provider as cleanup. Your product decides whether cleanup is required, whether a receipt remains valid, and whether a user may remove records.

Product readiness

A completed provider write is not proof that public DNS has propagated. Use Verification and combine its provider/public-DNS observations with your own product readiness policy.

Accessibility

Keep destructive cleanup and disconnect actions distinguishable in text, not color alone. Preserve the confirmation dialogs, loading states, and failure outcomes supplied by the semantic parts.

API reference

Provisioning.Flow

Cleanup.Flow

Connection.DisconnectDialog

Read Plans, authorization, and receipts for the lifecycle invariants behind these controls.