V50, plain LiveView: 100 at familiarity 5, with no relays
V49 reached 100 at familiarity 5, but its LiveComponent panels relay every cross-panel change through the page: send(self(), …), then handle_info, then send_update. V48 has no relays (each feature is a value in the page’s assigns, and one handle_event runs the whole chain), but it scored familiarity 4. V50 asks whether that point was the design or the vocabulary.
What cost V48 the point
A Phoenix developer reading V48 learns three things beyond phx.gen.live: feature modules that return {state, outputs}, one private wire/3 clause per output port, and Steps’ sourcing vocabulary. V49 also has the first two, in the form of {state, outputs} modules and one handle_info clause per port, and I rated it a 5. So the point was the third: feed, call and async over named instances ({:add_line, &AddLine.run/2}) looked up in an @instances map.
What V50 changes
The named instances go. The configured store-work instances are plain assigns, and a clause says what it calls:
defp wire(s, :wishlist, {:taken, product}),
do:
s
|> Steps.feed(:cart, &Cart.receive/2, &AddLine.run(s.assigns.add_line, &1), product, &wire/3)
|> put_flash(:info, "Added to cart")
The payment, which the requirements make asynchronous, uses LiveView’s own task, and settling the order is a plain call:
defp wire(s, :checkout, {:ready_to_pay, payment}) do
charge = s.assigns.charge
start_async(s, :payment, fn -> Charge.call(charge, payment) end)
end
defp wire(s, :checkout, {:done, reference}) do
SettleOrder.run(s.assigns.settle, reference)
push_navigate(s, to: ~p"/cart/success")
end
Steps is now run/4 and feed/6, plus the stream, patch and timer landing points. feed stays because it keeps a clause from holding one abstraction’s answer to hand to another (Spray’s “handling the data”, §1.6.3): it runs a feature’s input on what a function answers. Store work therefore stays synchronous, as in V48. Adding a wishlisted product to the cart still happens inside the click’s own handle_event, with no task and no extra render.
The cart page, drawn from its clauses
flowchart LR
payment -->|"done → succeeded"| checkout
payment -->|"done → failed"| checkout
timer_undo -->|"fired → expire"| undo
cart -.->|"rows"| page_stream["page: stream"]
cart -.->|"summary"| page_assign["page: assign"]
cart -.->|"changed"| call_Carts_apply_change["call Carts.apply_change"]
cart -->|"removed → capture"| undo
cart -->|"saved → stash"| saved
cart -.->|"saved"| page_put_flash["page: put_flash"]
cart -->|"line → toggle"| wishlist
cart -.->|"promo_applied"| page_assign["page: assign"]
cart -.->|"promo_applied"| page_put_flash["page: put_flash"]
cart -.->|"promo_rejected"| page_assign["page: assign"]
cart -.->|"promo_rejected"| page_put_flash["page: put_flash"]
cart -->|"checkout_started → start"| checkout
cart -->|"checkout_requested → pay"| checkout
undo -.->|"captured"| page_assign["page: assign"]
undo -.->|"captured"| timer_undo["timer undo"]
undo -.->|"restored"| timer_undo["timer undo"]
undo -.->|"restored"| page_assign["page: assign"]
undo -->|"restored → receive"| cart
undo -.->|"restored"| page_put_flash["page: put_flash"]
undo -.->|"expired"| page_assign["page: assign"]
undo -->|"expired → confirm_removal"| cart
saved -.->|"rows"| page_stream["page: stream"]
saved -.->|"count"| page_assign["page: assign"]
saved -->|"moved → receive"| cart
saved -.->|"moved"| page_put_flash["page: put_flash"]
wishlist -.->|"rows"| page_stream["page: stream"]
wishlist -.->|"count"| page_assign["page: assign"]
wishlist -.->|"ids"| page_assign["page: assign"]
wishlist -.->|"added"| page_put_flash["page: put_flash"]
wishlist -.->|"dropped"| page_put_flash["page: put_flash"]
wishlist -->|"taken via AddLine.run → receive"| cart
wishlist -.->|"taken"| page_put_flash["page: put_flash"]
ui -.->|"tab"| page_assign["page: assign"]
checkout -.->|"step"| page_assign["page: assign"]
checkout -.->|"step"| page_patch["page: patch"]
checkout -.->|"form"| page_assign["page: assign"]
checkout -.->|"address"| page_assign["page: assign"]
checkout -.->|"blocked"| page_put_flash["page: put_flash"]
checkout -.->|"ready_to_pay"| payment["task Charge.call"]
checkout -.->|"done"| call_SettleOrder_run["call SettleOrder.run"]
checkout -.->|"done"| page_push_navigate["page: push_navigate"]
What it scores
| V48 | V49 | V50 | |
|---|---|---|---|
| Full checklist, by hand | 100 | 100 (99.5) | 100 |
ala_lint default / --strict / --super-strict | 100 / 100 / 100 | 100 / 100 / 100 | 100 / 100 / 100 |
Rules met under --strict (of 10 checked) | 10 | 10 | 10 |
| LiveView relays between components | none | 1 per cross-panel update | none |
| Tests | 119 | 87 | 118 |
| Mean / median time per test | 5.8 / 1.2 ms | 8.2 / 1.0 ms | 5.2 / 1.2 ms |
| Distinct functions | 296 | 312 | 295 |
| Familiarity | 4 | 5 | 5 |
The walk finds nothing new. Reading a configured instance from assigns and passing it as a call’s first argument is configuration, the same reading V49 and V38-max had.
What it gives up
- Loud instance names. In V45 and V48 a misnamed instance raised “no configured instance :charge” where it was named. In V50 a wrong assign key is a
nilthat fails inside the call. - Clauses that never read assigns. V45 removed those reads, and V50 brings them back for configured instances.
Later: the clone check (2026-10-19)
A clone check joined the linter on 2026-10-19 (R7, reported at the default tier and scored from --strict; a copy inside one module is reported and never scored). It found five pieces of logic written twice across modules. The checkout’s and the portal’s step handling (advance and goto) is now the Transitions paradigm, and the cart’s and order’s row is Lines.row. Two are accepted with their reasons in the code: set_stock in the cart and the order shares only the shape every input has, and the two pages’ wire/3 clauses are each page wiring its own flow. Later the same day V51B’s defect fixes were ported here (the portal’s “Item restored”, held removals kept out of settlement, distinct flash ids, and holds marked in the database so a closed page can’t lose a removal), and save for later was fixed in all three Elixir variants: a saved line is now marked in the database, so it stays in the Saved tab across a reload and is never charged, deducted or recorded at checkout. Now: 100 at every tier, 146 tests.
The step machine went into each variant’s own Transitions module, and the three did it differently: V50’s is a struct answering {:moved, to, machine} or :stayed, V51’s a struct answering {:moved, machine} or {:stayed, machine}, and V51B’s two plain functions answering the next state. The names and APIs are left as they are for now, so a reader comparing the variants meets the same idea three ways.
Later: a change feed (2026-10-21)
Until now each page subscribed through the Subscribed hook to Foundation.Broadcast’s topic and wrote a handle_info clause per kind of message, and SaveProduct broadcast on its own. A new kind of outside change meant a clause on every page that cared. Now outside change is one part, GoodDealWeb.Paradigms.ChangeFeed: the checklist’s “live subscription port”, in the layer Spray keeps for paradigm interfaces (§2.2). A page lists a configured feed among its parts, attaches it in mount/3, and wires its port like any other output:
feed: ChangeFeed.new(Catalog.changes_topic(), [:stock]) # among the page's parts
|> ChangeFeed.attach(:feed, @features.feed, &run/3) # in mount/3
defp wire(s, :feed, {:stock, change}), do: run(s, :cart, &Cart.set_stock(&1, change))
attach subscribes once connected and adds one handle_info hook (attach_hook/4) that runs each fact through the page’s run, so the fact leaves on the feed’s port and a wire/3 clause routes it. The wiring check and the trace see feed as they see any part. On the portal the same fact runs both OrderLines and PortalCatalog. The publish side is another instance on the same topic, called by SettleOrder’s announce after a purchase and by the product pages’ saved clause. A fact is a kind and a product id with at most one value, and only ChangeFeed knows its shape on the topic.
The move found a gap. A staff stock edit at /products was broadcast as product_updated, which carts and the portal ignored, so an open cart never showed it. The product pages now publish the stock fact too, and a test that failed without that line covers it. Foundation.Broadcast, the Subscribed hook and SaveProduct’s broadcasting are gone. Now: 100 at every tier, 153 tests (eight added, four of them on ChangeFeed itself, and one removed with Broadcast).
Isn’t this just LiveView? No. LiveView keeps a process per open page and pushes rendered diffs from that process to its browser, which solves page to browser. ChangeFeed solves world to page: it gets a change made somewhere else into the parts inside that process, as identity-keyed facts over Phoenix.PubSub, wired like any other part. LiveView then does what it always does: the part’s new state re-renders and the diff goes to the browser. How close can a LiveView app come to ideal ALA? has the longer answer.
What it shows
The familiarity point V48 lost was vocabulary, not design. With the same features, the same clauses and the same synchronous store work, a page using only LiveView’s API and a two-function runner scores 100 with no relays. As before, familiarity is my judgement on my own scale. V48, V49 and V50 together are a good set to show Phoenix developers to calibrate it.
The wiring as it ran
Added 2026-10-16. The trace first built for V51B is now part of V50, and it needed no change to any page. Steps.run/4 is the one function every output passes through, so it records the hop into the part it runs and, for each output, whether the page’s wire/3 clause ran another part or kept it; the page is read off the wire function it was handed. The suite turns the trace on, writes docs/diagrams/running/ from the hops, and fails if a declared output never routed.
Its first run found four: the cart’s checkout: :blocked and wishlist: :dropped, the portal’s undo: :expired and flow: :blocked. All four were wired and the source-parsed check was satisfied; none had a test. Four tests later, 123 tests and every output routed. Scored with a layer map, now kept in the variant as lint.exs, V50 is 100 at every tier.
The code is in ala_variants_elixir/v50-plain-liveview.