Stable browser/session identity used to bind multi-module behavior into one Ember story.
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>Canonical event / handoff schema
Canonical site or tenant URL where the event originated.
Current page where the module interaction happened.
One of prompt, proof, capture, scheduler, or signal_handoff.
Canonical event or signal label emitted by the module.
Short operator-facing description of what just happened.
The meaningful customer-side context needed by Ignite.
0-1 confidence score for the importance or urgency of the event.
The operator move Ignite should consider next.
Why the event matters to the operator/business.
Call, quote, booking, consultation, contact, or other declared intent.
Attached tenant/account identity for attached-customer runtime proving grounds.
Readable company label for the attached sandbox or real customer context.
Canonical site record identifier carried from the customer install context.
Live lf_accounts row id used when the runtime is database-backed.
Live lf_sites row id used when the runtime is database-backed.
Only present for handoff records; explains why the site event crossed the threshold into Ignite action.
Product-lane identity for product-specific conversion signals such as revenue_leak_finder.
yes/no marker proving whether known prospect/company/domain context was attached.
Known company or business name attached to the event when present.
Known domain or website attached to the event when present.
Known vertical/trade/industry context attached to the event when present.
Known market/metro/city context attached to the event when present.
Known acquisition source context attached to the event when present.
Known campaign context attached to the event when present.
Known intake/import batch context attached to the event when present.
Known traffic route or UTM route context attached to the event when present.