Journals/Field notes
Twenty-four hours at NTNU
A 2023 student weekend, a public recording, and a written account of live proofs versus slides. The architecture point is smaller than the boast: a weekend is a service only if the channel already exists.
Thiru · 23 September 2026 · 9 min read
A proof of the Real Time Web is not a slide. It is one live service: a source that still moves, an owner, a that is open, and something that reacts while people are still in the room. That is the test this page is about.
The recording is titled Brain x Nornir Hackathon at NTNU 2023. It is a student room, not a product launch. This site treats the video as the primary source for what happened that weekend. The written summary that travels with it is a separate thing, and it is treated as an account, not as independently verified history.
That written account says more than a hundred AI master’s students at NTNU built services across healthcare, logistics, IoT, and games. Many of them built more than one. After twenty-four hours they presented live on stage, with the services still running. This page does not invent a student count, a timetable, or a list of winning teams beyond that sentence. If you want the room, watch the recording.
What the comparison actually is
The same written account adds a contrast. A few months earlier, it says, the same students ran a hackathon on Microsoft’s IoT platform. They could not finish working services. The presentations became PowerPoint. At the NTNU weekend, the account says, they finished and showed the work live.
That is a compelling story. It is also a self-reported story. Nothing in the public corpus this site uses (the architecture notes, the published pages, an independent write-up) confirms the Microsoft weekend, the student count, or the claim that every team finished. There is no NTNU-published comparison cited here, and no journalist account. The one primary object you can inspect is the recording above.
So this page will not say it was the first time in hackathon history that every student finished. It will not say a vendor lost and a network won. It will say what the architecture actually claims, which is smaller and more useful: if a live channel already exists, twenty-four hours can be a service. If the weekend is spent standing up the stack, twenty-four hours is a slide.
Earlier IoT weekend
Integration as the work
Same student group, a few months before. The account says the presentations became slides. The services were not live.
NTNU, 24 hours
A live channel already there
Same student group. The account says they finished proofs and showed them on stage while they were still running.
Why a weekend only works with a channel
Most IoT weekends are integration weekends. Students spend the first day on identity, a device registry, a cloud project, a dashboard, and the glue between them. The object they wanted to build waits. By the time the stack is almost standing, the clock is gone. A slide is what you can still finish.
The Real Time Web model assumes the opposite order. The already has a . The ghost already has an owner. A can allocate more ghosts and link them into a channel. The weekend is not “invent the network.” The weekend is “name a job and keep it live.”
That is why NTNU-style proofs, as this site describes them for teammates, assume an existing channel platform. Without one, you mock the model. You do not claim you reverse-engineered a toolchain from a brochure. You also do not treat a chatbot wrapper, a stored inbox, or a multi-tenant registry as a Real Time Web proof. Those can look busy. They are not a live relationship.
Same architecture. Different rooms.
The account names four industrial rooms: healthcare, logistics, IoT, and games. That list is useful because it is ordinary. The architecture is not a vertical. A live reading a clinician can act on, a moving source a warehouse can follow, a sensor that stays a sensor, a game that stays open while people are still in it: those are the same four layers with different owners on them.
splits infrastructure, network and security, domain and application, and resource ownership so a change in one layer does not have to redefine the whole relationship. A student team can own the application they wrote for the weekend. The person or device that generates the resource can still own the data. Those do not have to be the same party.
Two different people do not open each other’s data because they share a weekend, a campus, or an implementation. Read access is a . It can be withdrawn. Ownership is a transfer, and a transfer has to be confirmed. The consume rule in the draft notes is still the same: data is consumed when the ghosts at the ends are owned by the same user, or the receiver has approved read access. Same user usually means one person, two of their endpoints. Not two strangers who sat at the same table.
Healthcare
A live reading a clinician or a device can act on.
Logistics
A moving source, not a batch report after the truck has left.
IoT
A sensor that stays a sensor. The service supplies the job.
Games
A present that stays open while people are still in it.
What “finished” has to mean
Finished, on this site, is a ninety-second clip: a named service is live, a source changes, something reacts without a batch job. Optionally a second consumer arrives through a morph, then goes dark when the morph is withdrawn. The first service still works. That is the demo moment. A deck that describes the same idea is not the same moment.
The written account says the NTNU students reached that kind of finish, and that many of them reached it more than once in a day. Watch the recording before you treat that as more than an account. If the stage shows live services, that is the interesting fact. If some teams are still on slides, that is also a fact. This page will not paper over either.
The architecture point survives either way. Real Time Web is not a replacement for the Internet and not a new World Wide Web. WWW connects documents. This work is for live, stateful relationships on top of and alongside the existing Internet. A weekend is a good place to see whether that sentence is operational or only rhetorical.
How far this page goes
The written account names a toolchain used at that event. A toolchain can configure and secure a service. It is not the architecture, and it is not the only way to run one.
A student weekend is one place the idea was tested in a room. The recording is public. The comparison to an earlier IoT weekend remains the account of the people who ran this one.
This page follows the published recording of the 2023 NTNU hackathon and the written account that travels with it. Claims about student numbers, completion rates, and an earlier Microsoft IoT weekend are attributed to that account. They are not independently verified in the corpus this site uses. Watch the video for the room itself.