Overview

The Synchronic Web is a shared state layer for open-world, partially-trusted networks. It combines cryptographic data structures, programmable semantics, and distributed synchronization so participants can reason about state across time and space.

Contents

Each section builds on the previous one:

1. Usage: how users interact with journals and services.
2. Operation: how operators deploy, run, and maintain the system.
3. Development: how developers extend runtime behavior and class logic.
4. Research: research directions motivated by the current architecture.

If you are new to the stack, read this page, then move through the sections in order. If you already operate or build on the stack, you can jump directly to the section aligned with your role.

Purpose

The core value proposition is verifiable shared state in adversarial or partially-trusted environments. Traditional APIs can serve data quickly, but they often lack strong guarantees about temporal ordering, provenance, and cross-node consistency. The Synchronic Web addresses that by treating state as a cryptographically linked structure with programmable rules for mutation and synchronization.

Dynamic Object Structures

The stack uses a minimal language and object protocol to encapsulate both data and behavior over time. Rather than hard-coding every interface in Rust, the runtime allows controlled Lisp-level composition of classes (standard, tree, chain, ledger) and query/step handlers. This makes higher-level behavior evolvable without replacing the runtime substrate. In practice, this means teams can iterate on application semantics at the Lisp layer while retaining a stable underlying execution and persistence runtime.

Dynamic Peer Topologies

The distributed model is usage-driven: peer relationships can be introduced and updated at runtime. Nodes can synchronize proofs and selectively resolve remote state while preserving cryptographic verifiability. This gives a practical notion of state across space, not just within one process or one database. This topology flexibility is useful in real systems where trust boundaries and communication patterns change over time.

Resources

This section links to the primary repositories and live endpoints that developers and operators use most often.

Software Repositories

All official resources are found in the following public repositories:

1. sync-web: documentation hub and project entry point.
2. sync-journal: Rust runtime, HTTP interface, evaluator extensions, persistence.
3. sync-records: Lisp class logic (control, standard, tree, chain, ledger, interface).
4. sync-services: compose deployments and web services (interface, gateway, explorer, workbench, file-system).
5. sync-analysis: load testing and network/simulation assets.

All repositories are open source and include licensing metadata in-repo (LICENSE files where applicable), with Sandia National Laboratories authorship and stewardship.

Live Nodes

• The Beagle: flagship general-purpose synchronic web node accessible from the open web

Use the operation and usage documentation before depending on live infrastructure for production workflows.