Host integration

Host integration

Prerequisites

Use installed public packages and a trusted local project. Host integration requires real scoped persistence, verified identity and current resource authorization. Use synthetic inputs for local checks.

Public import

Install the package; the subpath below is an import target, not a separate package. Registry installation requires a published EAOS release; before publication use the owning workspace’s checksum-verified build artifact.

bun add @alneas/eaos-plugin-approval

import { createPlugin } from '@alneas/eaos-plugin-approval'

export function bindHostPlugin(...args: Parameters<typeof createPlugin>) {
  return createPlugin(...args)
}

Server integration requires a verified principal resolver, live authorization and the plugin’s durable host ports. React views use the separate /react export with its declared UI peers and application providers; importing the server entry requires no CSS.

Step-by-Step Implementation

This module forwards the actual host ports without inventing identity or persistence:

import { createPlugin } from '@alneas/eaos-plugin-approval'

export function bindHostPlugin(
  options: Parameters<typeof createPlugin>[0],
  resolvePrincipal: Parameters<typeof createPlugin>[1],
) {
  return createPlugin(options, resolvePrincipal)
}

Use the package root API with host-owned options and a verified principal resolver. authorize must check current lifecycle activation, tenant membership and the requested resource on every operation. No tenant ID or role from a request body grants access.

Supply the canonical platform-records Data Contract from @alneas/eaos-core/contracts/platform-records to Lifecycle. Its original version, migration identity, SQL and payload namespaces are unchanged. Installation creates storage independently of feature activation. Services use durable tenant-scoped record stores and CAS; configure approval templates or base field schemas in the host.

@alneas/eaos-plugin-approval/runtime exports createExtension({ tenantIds, bindings }) for the Platform loader. bindings contains { options, resolvePrincipal }; missing live host adapters fail closed. Pass these in the trusted loader option bindings[packageName], never in JSON settings or HTTP data. Generic deployment inspection does not execute this factory.

Build/test/pack never apply production DDL, deploy infrastructure or enable tenants. Verify local persistence, cross-tenant refusal, revoked authorization and stale revisions using the packaged plugin before host adoption.

Verification

Build and install the actual tarball in an isolated consumer. Verify the declared behavior, foreign-tenant denial, stale revisions and revoked access. Importing or installing a package does not activate tenants or apply production changes.

Troubleshooting / Common Pitfalls

Missing host bindings must fail closed. Do not substitute empty success adapters, infer addon budgets or treat a visible route as permission. Check the owning API reference and current host policy.