Server-rendered web candidate

SwiftWebUI

Server-hosted SwiftUI-like views over a browser session.

Many worlds. One workstream.

renderer Server runtime maturity Investigate maintainer External upstream campus Campus maintainer candidate mode Dynamic server frontend with Swift npm No npm manifest observed setup Syntax specimen only import SwiftWebUI

Shipping question

Can an older SwiftUI-style server runtime still compile and host the homepage loop?

This specimen is generated by the wrkstrm homepage model. It does not prove the upstream framework is installed in the campus until a setup receipt lands here.

npm evidence: 2026-05-18 recursive GitHub tarball scan found Package.swift and no npm manifest or lockfile paths.

Package: https://github.com/SwiftWebUI/SwiftWebUI

current provisional award

Where this competitor is strongest.

Best server-side Swift archaeology

SwiftWebUI

Server-hosted SwiftUI-like views over browser sessions.

Why: 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.
Sharp edge: Older architecture is useful evidence, not a default path; it must earn every modern claim.

server-side-swift runtime latency architecture award

Homepage arc

candidate

Generate possible worlds

Agents and digikomas produce apps, documents, diagrams, releases, and decisions.

parallel

Compare timelines

Shipped, stalled, counterfactual, and next-best branches stay visible together.

proved

Select the executable path

Schemas, Swift packages, DocC, receipts, commits, and releases back the branch.

Adapter sketch

import SwiftWebUI
struct WrkstrmHome: View {
  var body: some View {
    VStack {
      Text("wrkstrm")
      Button("Enter the workstream") {}
    }
  }
}