Skip to content

syncropic/syncropel

Syncropel

Make coordination durable, composable, and trustworthy.

License: Apache-2.0 npm PyPI Docs


Syncropel makes the world's knowledge and actions composable, computable, verifiable, and yours. It is an open protocol for human + AI teams to coordinate, decide, and govern together — built from immutable, signed, content-addressed records that compose into threads, accumulate evidence-based trust, and feed workflows that learn and replay.

Syncropel is not an AI framework, not a vendor SaaS, and not a blockchain. It sits alongside your tools and records what they do, with verifiable provenance and consent-gated sharing.


What's in the protocol

  • Records. Every coordination event becomes a record: who did it, what kind of act (intend, do, know, learn), what content, in what thread. Signed by the actor, content-addressed by its hash, immutable from the moment it lands.
  • Threads. Records group into threads — the unit of coordinated work. Git-like: fork, merge, close.
  • Actors. Humans, AI agents, and automations are all first-class actors with portable identity. The protocol doesn't distinguish them structurally; every record is signed by its actor, and every actor accrues trust independently.
  • Trust. Evidence-based reputation. Trust accumulates from execution history, is computed per-actor-per-domain rather than as a single score, and decays over time so old wins don't bank forever.
  • Patterns. Repeated success is captured automatically. When a thread succeeds the same way often enough, its shape promotes to a reusable pattern — next time something similar appears, the proven solution replays. A single dial decides whether each task leans into replay (predictable, free) or fresh generation (novel, costlier).
  • Workspaces. A workspace is a record too — versioned, forkable, federatable. Specs, dashboards, runbooks, anything you'd put in a separate tool, but as records.
  • Federation. Instances pull from each other selectively; consent-gated; no central registry. Share patterns without sharing data, via a hash hierarchy that lets you publish what works while keeping the specifics private.

For the full specification, see docs.syncropel.com.


Two paths to a working instance

Hosted — fastest. Sign up at syncropel.com/sign-up; a per-customer Syncropel instance comes up at <your-label>.syncropel.app in about a minute. No install, no machine to maintain. Free tier; pricing for scale.

Self-hosted — install spl on a machine you control:

# Linux + macOS + WSL
curl -sSf https://get.syncropic.com/spl | sh

# Windows (PowerShell)
irm https://get.syncropic.com/spl.ps1 | iex

# Then
spl init && spl serve --daemon

Both paths run the same binary, expose the same APIs, and federate with each other.

If you're integrating from code, use one of the SDKs:

npm install @syncropel/sdk      # TypeScript / JavaScript
pip install syncropel           # Python

Full getting-started flow at docs.syncropel.com.


What a thread looks like

fix-checkout-timeout                          5 records · 3 actors

● you      INTEND  "Fix checkout timeout before launch"     14m ago
○ agent    DO      Profiled — connection pool saturated     12m ago
○ agent    DO      Patch applied: pool 10 → 50, deployed    9m ago
○ monitor  KNOW    p99 4.2s → 180ms — 340 users unblocked   6m ago
○ agent    LEARN   "Pool sizing must scale with replicas"   now
                   captured · next similar issue replays

is a person; is an AI agent or automation. Every record is immutable, content-addressed, and signed by its actor. The LEARN at the end captures a reusable pattern — the next time the same shape of issue appears, the solution replays automatically.


Where to go next


The open-protocol commitment

Syncropel is open by design and committed to staying open. The reference implementation is open source under the Apache-2.0 license. The protocol specification is published under CC-BY-SA. We hold patents defensively under a perpetual, irrevocable pledge — never asserted against users of the protocol. We are targeting a non-profit foundation handoff to take stewardship of the protocol.

The formalized text of the charter and patent pledge is in counsel review and will be published here when ready.


Status

Syncropel is in active development. It is used in production by early dogfooders, and hosted signup is live. Breaking changes are possible, and when they happen they ship with documented migrations and a CHANGELOG entry.


License

Apache-2.0. See LICENSE.

The license here covers the documents in this repository. The reference implementation and SDKs ship under their own licenses from their own repositories.

Syncropel is developed by Syncropic, Inc., a Delaware public-benefit corporation.


Brand

  • Syncropic — the company that stewards the protocol
  • Syncropel — the protocol itself
  • Studio — the browser interface for working with Syncropel
  • spl — the command-line interface and local instance binary

About

An open coordination protocol for human + AI teams — immutable records, evidence-based trust, and workflows that learn and replay.

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors