XTend Fabric Runtime
XTend Fabric is the coordination layer for runtime work. It maps RMT scheduling intent into lanes and fibers, makes hydration decisions and exposes telemetry plus diagnostics.
What This Layer Is
Fabric is the bridge between kernel intent and host execution. The kernel describes which work exists; Fabric helps the host decide when that work should run and with which priority.
What this layer knows
Fabric knows Fabric lanes, RMT lane mapping, schedule records, fiber context, hydration policies, backpressure, completion signals, diagnostics and telemetry snapshots.
Fabric can identify whether work is visible, idle, diagnostic or user-blocking. That helps the app control repaints, reflows and unnecessary hydration work.
What it does not know
Fabric does not parse RMT, render UI, own framework components or execute business logic.
Fabric does not decide whether a React, Vue or XTend component is correct for the product. It only evaluates runtime intent, priority, hydration and diagnostic information.
Interfaces
import { createXtendFabric } from '@ccslabs/xtend/fabric';
import { resolveRmtScheduleForFiber } from '@ccslabs/xtend/fabric/rmt-lane-mapping';
const fabric = createXtendFabric();
const schedule = resolveRmtScheduleForFiber({
lane: 'visible',
scheduleRef: 'component.visible.hydrate',
kind: 'component.hydrate'
});The primary public entry points are createXtendFabric, hydration policy helpers, RMT lane mapping, diagnostics and telemetry snapshots.
Communication with other layers
The RMT kernel provides schedule intent, lane names and diagnostics. Fabric normalizes that information and gives host adapters concrete execution and hydration hints.
XTend UI and other framework adapters can use Fabric context to prioritize visible work before idle work, collect diagnostics and make component hydration traceable.