Embedding

Host apps attach communication to an opaque context. They do not model tickets inside Efelant.

Conversation + Context + Event

Clients

Flutter

EfelantConversation(
  tenantId: tenantId,
  context: EfelantContext(
    type: 'access_request',
    externalId: accessRequestId,
  ),
)

Web components

<efelant-conversation
  tenant-id="…"
  context-type="access_request"
  external-id="AR-123">
</efelant-conversation>

No React package ships from this repo. Stencil custom elements work from HTML, Vue, Angular, and Svelte.

Host integration

Regenerate tokens and SDKs

Package surfaces: SDKs. Token catalog: Styles. The landing-page demo is an in-memory Alice and Bob pair via createMemoryHub(). The Flutter app sets the live host in settings.

From the repository root (Node 20+):

./scripts/packages.sh              # tokens → clients → Stencil → Flutter
./scripts/packages.sh tokens       # Style Dictionary only
./scripts/packages.sh components   # tokens, then web components

Edit packages/tokens/tokens/*.json and packages/web-components/src/. Do not hand-edit generated CSS or Dart.

Same transaction

If the host shares the database, call efelant.publish_status in the same transaction as the business update. If it cannot, use an API client token over REST or gRPC.