LogicForge
Master layer 178 grouped-page UI correction lock live
L180 0.2.180.1800 logicforge-layer-180-schema.sql
Ignite grouped owner page
Ember
Ignite grouped page · Ember

Ember support is now a first-class Ignite grouped page.

Owners can now open one page to understand what the site is signaling and what that changes in the business.

Launch modules
5 canonized

Prompt, Proof, Capture, Scheduler/Contact Rail, and Signal/Handoff now live as a single install package.

Live handoffs
0

Waiting on the first install/session to emit a handoff.

Signals logged
1

Signals and events share one canonical event/handoff schema so later Foundry learning stays clean.

Ember consequence

Ignite is ready for Ember module consequence, but no site handoff is live yet.

This support lane is now real: once the first site session emits signals, Ignite will show module consequence instead of raw runtime proof.

5 canonized

Prompt, Proof, Capture, Scheduler/Contact Rail, and Signal/Handoff now live as a single install package.

0

Waiting on the first install/session to emit a handoff.

1

Signals and events share one canonical event/handoff schema so later Foundry learning stays clean.

Launch modules

What the site runtime can now contribute

Prompt, proof, capture, scheduler/contact rail, and signal/handoff now roll up into one grouped owner page.

Prompt
Live signal seen

Ignite should surface prompt impressions, engagements, objections, and assisted conversions.

Proof
Install-ready

Ignite should show what proof was displayed, what it changed, and whether it helped conversion.

Capture
Install-ready

Ignite should show capture source, CTA variant, conversion quality, and the resulting next move.

Scheduler / Contact Rail
Install-ready

Ignite should surface booking attempts, contact completions, drop-off, and speed-to-follow-up implications.

Signal / Handoff
Install-ready

Ignite should receive handoff reason, confidence, recommended move, and visible business consequence.

Live handoffs

What site behavior is asking the owner to do next

Ember handoffs stop being invisible and start becoming business context.

No live Ember handoff has been recorded yet.
Restore live prospect pressure into the state spine

The support contract is in place; the first installed site session will create the initial handoff packet here.

Recent completions

Business moves still stay visible here

Ember support now lives beside the main business board instead of apart from it.

Booked conversation prepared for Midwest Dental Group
Fallback mutation recorded so the first screen can show immediate consequence without pretending live database execution occurred.

The first screen now reflects a completed move and a new next responsibility. Next: Review the proposal-ready path for Midwest Dental Group.

Booked conversation prepared for Midwest Dental Group
Fallback mutation recorded so the first screen can show immediate consequence without pretending live database execution occurred.

The first screen now reflects a completed move and a new next responsibility. Next: Review the proposal-ready path for Midwest Dental Group.

Booked conversation prepared for Midwest Dental Group
Fallback mutation recorded so the first screen can show immediate consequence without pretending live database execution occurred.

The first screen now reflects a completed move and a new next responsibility. Next: Review the proposal-ready path for Midwest Dental Group.

Level 3 · contextual super-user controls

Advanced inspection stays attached to the page context.

This panel does not replace the owner view. It gives a deeper truth path for the current grouped page without forcing a detached admin detour.

Hide advanced controls
Current grouped page
Ember
Focused direct-entry
None
Dominant move
Restore live prospect pressure into the state spine
Truth posture
Live runtime
Pipeline value
0 live prospect(s)
Ember handoffs
0
Latest receipt
Fallback mutation recorded so the first screen can show immediate consequence without pretending live database execution occurred.