Time as a Navigable Dimension, Not a Linear Log

What this means for you

Most collaborative systems treat time as a single line that gets overwritten as people work. TNP treats time the way the web treats pages: every alternative coexists, every version has an address, and any reader can travel between them without losing the others.

The pitch

TNP is the protocol that lets a team fork a document, an experiment, a simulation, or a game state, work in parallel without conflict, and decide later whether to merge, keep both, or seal one as the record of what was actually decided. Time becomes something you navigate, not something you lose.

Who it’s for

Anyone whose work has a “we should have kept the other version” problem: collaborative writing, ML experiments, branching narratives, digital twins, regulated decisions.

Proof points

• Stakeholder Introduction Document names the protocol category in plain English: “a new way of thinking about collaboration over time”
• Five primitives the entire surface reduces to: fork, navigate, merge, seal, compare
• Designed alongside four sister protocols on the TimeChain platform (fork-node, vest-node, mesh-node, aegis-node) so the temporal layer has a native home, not a bolt-on
• Reference implementation is a Rust crate under aphelion-craft with a written gRPC streaming surface

mindmap
  root((TNP))
    Fork
      cheap branches
      private by default
    Navigate
      cursor across timelines
      no server round-trips for history
    Merge
      domain-specific strategies
      staged approval gates
    Seal
      signed, append-only
      legal-grade evidence bundles
    Compare
      diff two timelines
      promote one to canonical