Crucible / Product Lane / Ignite

Ignite control surface

Shell-inheritance proof for the Ignite product lane: product-state clarity, growth-engine posture, gated activation, and no-send safety inside the canonical Crucible frame.

Updated May 11, 2026 6:48 PM · Schema logicforge-layer-578-schema.sql · Ignite accent is content-scoped only

Inheritance verdictIgnite shell liveL578 · neutral shell + product accent

Ignite fuelActive

growth-engine lane projected through Crucible

shell only; runtime untouched

Demo postureHeld

customer-facing Ignite surfaces remain gated

no funnel reactivation

Execution modeNo-send

operator proof only inside Crucible

outbound unchanged

Route stateLive

single product control surface reactivated

other Ignite routes blocked

Critical bottleneck

Ignite activation remains gated

This page proves shell inheritance only. It does not reactivate Ignite app, demo, funnel, outbound execution, workers, customer access, or billing behavior.

View gate details →

Required outcome

Clear Ignite review gate

The product lane can now be inspected inside the shared shell while all deeper Ignite routes remain intentionally blocked.

Audit gate details →

Ignite system flowFuel → Context → Demo → Funnel → Review → Activation → Send

Fuelprospect spine

ContextCrucible-owned

Demogated

Funnelgated

Reviewoperator only

Activationblocked

Send0 sent

Product proof

What this surface proves

Canonical shell inheritanceHealthy

Neutral nav/topbar invariantPreserved

Product accent boundaryContent only

Ignite behavior mutationNone

Safety postureMuted by design

Shell inheritanceHealthy

Send postureNo-send

WorkersUnchanged

SchemaNo-op