Vertical-neutral capability boundary

Fabric Platform contains governance mechanisms, not a business product. A vertical supplies FabricModule definitions for its actions, policies, state machines, events, views, adapters, and portable semantics. An application composition root validates them with createModuleRegistry() and injects that instance into Platform Host. Imports have no registration side effects and registries are never shared implicitly between applications.

Platform core is UI-agnostic, storage-agnostic, workflow-agnostic, policy-engine-agnostic, identity-provider-agnostic, and vertical-neutral. It contains no vertical business vocabulary or vertical-specific default field policy. Optional roles, slots, action intents, and display renderers belong to @fabricorg/experience-contracts under fabric.experience/v1; core preserves the extension as namespaced JSON without interpreting it.

The Enterprise Composable Framework blueprint shows how company-shared capabilities, vertical packs, and an SDUI experience runtime compose on this boundary without putting industry vocabulary in Platform.

Experience and agent callers use two governed lanes:

1. Reads call ProjectionHost.project() with server-derived actor and tenant scope and one of current, bounded-stale, or offline consistency.
2. Mutations call PlatformHost.submitAction() with server-derived authority and a stable, payload-bound idempotency key.

The repository Boundary Guard checks runtime source and packed npm contents for prohibited domain terms, infrastructure imports, mutable module-scope state, import-time environment reads, dependency budget drift, and expired waivers. Its denylist is deliberately owned outside Platform runtime code so guard vocabulary cannot leak into shipped packages.