From Spec to Time Web: A Six-Phase Adoption Arc

What this means for you

TNP’s evolution.md writes the launch as a six-phase arc that does not skip ahead. Today’s phase is the first one: a documentation-only protocol with no running code. The pitch acknowledges that openly and points at what unlocks the next phase, instead of pretending a product already exists.

The pitch

Establish the protocol as a category of thinking, the way CRDTs were a category before they were a library. Then ship the SDK and the CLI. Then watch collaborative editors, notebooks, and design tools pick it up. Then watch infrastructure adopt it under the hood. Then let the public meet it through the “Time Web” metaphor. Then become the default model for state, the way HTTP became the default for documents.

Who it’s for

The investor or technical peer asking why the README points at research files instead of a download link.

Proof points

• Six phases are explicit in docs/research/evolution.md: documentation, developer tooling, collaborative apps, application infrastructure, Time Web metaphor, mass-market computing primitive
• Phase one is dated honestly: “Nothing runs yet, but the protocol is defined well enough that academics can reason about it, developers can imagine applications”
• Each phase names a concrete unlock for the next: an SDK and CLI move 1 to 2; a multi-timeline editor moves 2 to 3; a public app visualising timelines as spaces moves 4 to 5
• The arc explicitly compares the endpoint to HTTP, WebSockets, and CRDTs as analogous protocol primitives, setting the ambition without overclaiming current state

timeline
  title Six-phase TNP adoption arc
  Phase 1 : Documentation-only protocol : where TNP is today
  Phase 2 : Developer tooling : SDK, CLI, timeline inspector
  Phase 3 : Collaborative apps : editors, notebooks, design tools
  Phase 4 : Application infrastructure : sync, debug, ML, twins
  Phase 5 : Time Web metaphor : public-facing concept lands
  Phase 6 : Default state model : HTTP for temporal navigation