@fabricorg/experience-runtime

The supported experience composition runtime, split by trust:

• /server verifies admitted releases and issues scope-bound render plans.
• /client consumes plans through fragment events and named bindings.
• /offline captures eligible events for governed replay.
• the root export contains serializable contracts only.

Client checks detect accidents. They are not authorization. Server plan resolution, ProjectionHost, and PlatformHost remain authoritative.

Offline capture stores no credentials or identity claims and requires an encrypted-at-rest adapter in production. A capture expires no later than its scoped plan, so applications that support a longer offline window must issue an explicitly bounded offline-capable plan. Replay always returns through the gateway and current Host authority rules.

Replacement runtimes can run experienceServerChecks and replacement clients can run experienceClientChecks without importing Fabric internals.