Install one reviewed revision.

01 · Build the handoff

Pin the source and toolchain.

Use Node 22.18.0 and pnpm 10.28.0 in a clean checkout of the exact approved commit. The packaging command builds twice, checks that the archives are byte-identical, exercises the packaged dependency tree and writes a source archive, manifest and checksums under .local/releases/<full-commit>/.

pnpm install --frozen-lockfile
pnpm collectors:pack

# Confirm manifest.json says deployment_status: "pending".
# Verify every artifact against SHA256SUMS before copying it.

02 · Keep the set together

Install all matching tarballs.

Install the revision-specific @illun/agent-rules, @illun/collector-core and @illun/collector-next archives in the host app. Keep direct core or rules dependencies when the app imports them itself. Do not mix versions or treat a backend deployment as a collector update.

A source handoff is still marked pending until the receiving app records the exact revision, package versions, rules version and evidence expiry after deployment.

03 · Wire Next.js

Configure the real deployment boundary.

In Next.js 16 use proxy.ts; in Next.js 14–15 use middleware.ts. Put the project id, write key and ingest endpoint in the deployment environment. Choose a trusted-proxy mode only after reviewing the actual proxy chain, and never commit the write key.

import { agentProxy } from "@illun/collector-next";

export default agentProxy({
  project: process.env.ILLUN_PROJECT!,
  writeKey: process.env.ILLUN_WRITE_KEY!,
  endpoint: process.env.ILLUN_ENDPOINT!,
  // Add trustedProxy only for the reviewed deployment chain.
});

Next statically analyses the matcher, so the reviewed matcher literal must be copied from the installed adapter README rather than imported. It excludes Next internals, static assets and React Server Component payloads before the runtime collector runs.

04 · Verify the runtime

Deployment and contact are separate facts.

Verify a known real agent request, the sanitised event, the dashboard rollup and the collector configuration report. An explicit deployment contact can report configuration without a request; it is not a count and does not prove successful collection. Human and excluded requests must emit no event and no collector contact.

Record the deployed revision and rules expiry, then keep the reviewed range refresh, rebuild and redeployment process active. Installed bundled evidence does not update when source or the backend changes.

Availability

This is an operator guide, not a signup.

The procedure above documents the controlled handoff used for owned sites. There is no public package release, self-service project creation or customer service offer. See the technical privacy boundary and legal-document status for the other current limits.