wrkstrm-research ceremony mode

Give the award, then demand the receipt.

These demos turn the provisional SwiftUI-like framework awards into test assignments. Each winner gets a visible job, the thing we like, the thing we distrust, and the exact proof it has to earn next.

Many worlds. One workstream.
6 awards 11 SwiftUI-like lanes status provisional until build receipts land tests build, load, motion, SwiftUI fidelity

award demos

What each competitor gets to prove.

The ceremony is intentionally blunt: reward the best current shape, then write the next benchmark in public. Great systems get praise and pressure at the same time.

Provisional best all-around web lane Ignite
renderer Static HTML path Direct web candidate mode Static frontend with Swift npm No npm manifest observed

why it gets the trophy

Fast build and fast load path with Swift-authored static output.

It is the cleanest current path for a public marketing site: direct web output, Swift source, and no npm manifest observed in the repository scan.

Prove next
Install in campus, render the wrkstrm page, record build time, static asset weight, Lighthouse-style load timing, and animation ceiling.
Bad thing
Static output can look polished while hiding weak interaction depth; it has to prove rich motion, not only fast pages.
test lane
  • fast build
  • fast load
  • direct web
  • swift first
fast-build fast-load direct-web swift-first award
Best dynamic browser motion lab ElementaryUI
renderer WASM DOM path WASM web candidate mode Dynamic frontend with Swift npm npm present in browser runtime

why it gets the trophy

Swift-authored browser runtime that can test state, DOM updates, and animated interaction.

It has the strongest dynamic-browser ambition in the current catalog and is already marked build-now for the homepage pressure test.

Prove next
Run a real campus demo with frame timing, interaction latency, reduced-motion fallback, and browser bundle size.
Bad thing
The BrowserRuntime npm surface is real pressure; JavaScript cannot quietly become the product boundary.
test lane
  • animation
  • dynamic ui
  • wasm
  • npm pressure
animation dynamic-ui wasm npm-pressure award
Best SwiftUI compatibility research SwiftOpenUI
renderer Native compatibility path Reference specimen mode Dynamic frontend with Swift npm npm present in web build

why it gets the trophy

Compatibility harness for SwiftUI-shaped declarations across renderer backends.

It is the sharpest catalog entry for asking what a portable SwiftUI API actually has to preserve.

Prove next
Separate demo-harness convenience from production runtime, then measure screenshot receipts against native SwiftUI expectations.
Bad thing
Its web package uses Vite, Node, and Puppeteer; useful harnesses are not automatically production paths.
test lane
  • swiftui fidelity
  • compatibility
  • screenshots
  • npm pressure
swiftui-fidelity compatibility screenshots npm-pressure award
Best native cross-platform reference SwiftCrossUI
renderer Native shell path Reference specimen mode Native Swift reference npm No npm manifest observed

why it gets the trophy

Native declarative UI reference for testing component grammar before web output exists.

It gives wrkstrm a Swift-first way to test whether the component model is portable beyond browser concerns.

Prove next
Build a native fixture that mirrors the public page state model and records compile time, launch time, and platform gaps.
Bad thing
Reference-only paths can improve architecture without ever shipping the web surface investors see.
test lane
  • native reference
  • cross platform
  • swift first
  • build time
native-reference cross-platform swift-first build-time award
Best server-side Swift archaeology SwiftWebUI
renderer Server runtime path Server-rendered web candidate mode Dynamic server frontend with Swift npm No npm manifest observed

why it gets the trophy

Server-hosted SwiftUI-like views over browser sessions.

It keeps the server-side Swift campus honest about older runtime ideas that may still teach session, diffing, and render-loop constraints.

Prove next
Compile a minimal server fixture and test cold start, request latency, and state update semantics.
Bad thing
Older architecture is useful evidence, not a default path; it must earn every modern claim.
test lane
  • server side swift
  • runtime
  • latency
  • architecture
server-side-swift runtime latency architecture award
Best minimum grammar reference SwiftTUI
renderer Terminal shell path Not directly web-shippable mode Terminal Swift reference npm No npm manifest observed

why it gets the trophy

Terminal renderer that forces the smallest useful SwiftUI-like component grammar.

It can pressure-test state, layout, and fallback semantics without hiding behind visual polish.

Prove next
Render the same homepage arc as a low-fidelity terminal fixture and compare state shape to the web candidates.
Bad thing
Terminal elegance does not prove browser animation, but it can expose bloated abstractions quickly.
test lane
  • fallback
  • terminal
  • state model
  • small grammar
fallback terminal state-model small-grammar award