1  # RFC-0001 — Lightspeed Core Runtime
 2  
 3  Status: Draft
 4  
 5  ## Summary
 6  
 7  Define Lightspeed as a transport-independent live-session runtime for Gleam.
 8  
 9  ## Motivation
10  
11  A LiveView-style system in Gleam should not begin as a monolithic web framework. Gleam already has web libraries and UI libraries. Lightspeed should provide the missing runtime contract: stateful server sessions, typed events, lifecycle safety, and patch delivery.
12  
13  ## Design
14  
15  The core crate exposes:
16  
17  - component contract
18  - lifecycle typestate
19  - ISA
20  - protocol frame model
21  - patch model
22  - test helpers
23  
24  Transport adapters and render integrations may live in separate packages once the core boundary stabilizes.
25  
26  ## API impact
27  
28  Introduces initial public modules under `lightspeed/*`.
29  
30  ## Protocol impact
31  
32  Introduces protocol name `lightspeed` and protocol version `1`.
33  
34  ## ISA impact
35  
36  Introduces initial instruction vocabulary.
37  
38  ## Security impact
39  
40  Core will define security hooks but concrete enforcement lives in adapters until the WebSocket proof of concept exists.
41  
42  ## Alternatives
43  
44  - Build directly on Lustre server components.
45  - Build a Wisp plugin first.
46  - Build a Phoenix-compatible protocol.
47  
48  ## Unresolved questions
49  
50  - Should core be one package or split into `lightspeed_core`, `lightspeed_server`, and `lightspeed_client`?