Ember install

One install script powers the Ember launch modules.

The runtime stays small: one public asset, one module registry, one event/handoff schema, and one Ignite support contract.

One-script install

<script src="/assets/logicforge.js"
    data-client-key="lf-launch-preview"
    data-source-key="ember-install"
    data-site-url="https://example.logicforge.local"
    data-page-path="/"
    data-mount="[data-ember-preview]"
    data-preview-mode="true"
    data-ingest-base="/api/ingest"></script>

Client keylf-launch-preview

Source keyember-install

Mount selector[data-ember-preview]

Asset/assets/logicforge.js

Ingest base/api/ingest

Canonical event / handoff schema

session_id

string · required

Stable browser/session identity used to bind multi-module behavior into one Ember story.

site_url

string · required

Canonical site or tenant URL where the event originated.

page_path

string · required

Current page where the module interaction happened.

module_key

enum · required

One of prompt, proof, capture, scheduler, or signal_handoff.

event_key

string · required

Canonical event or signal label emitted by the module.

headline

string · required

Short operator-facing description of what just happened.

detail

string · required

The meaningful customer-side context needed by Ignite.

confidence

float · required

0-1 confidence score for the importance or urgency of the event.

recommended_next_move

string · required

The operator move Ignite should consider next.

operator_effect

string · required

Why the event matters to the operator/business.

conversion_intent

string · optional

Call, quote, booking, consultation, contact, or other declared intent.

handoff_reason

string · optional

Only present for handoff records; explains why the site event crossed the threshold into Ignite action.