field-customization host boundaries

Motivation

The generic MIT field-customization plugin provides reusable operations while the host retains identity, current activation, persistence and resource authorization.

Architectural Diagram

flowchart LR
  Principal[Verified principal] --> Admission[Live activation and resource check]
  Admission --> Service[Plugin service]
  Service --> Store[Host durable store and audit]

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-field-customization

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

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.

Trade-offs & Decisions

Package installation never activates a tenant. Request bodies cannot grant identity or roles. Real-store tests exercise persistence, tenant isolation, stale revisions and revocation. Business templates and production provider configuration remain host-owned.

Continue with the user guide, host integration and API reference.