Skip to content

More

Open source

What we intend to open, and in what order. The parts that let anyone check the record without trusting Syderial lead the list.

A stranger should be able to check the record without our help. The parts we intend to open earliest make that possible. None is published yet, and this page lists them in the order we intend to release them.

A precise written description of the canonical form, hashing, chain links and Ed25519 signatures behind every receipt, detailed enough for an independent implementation. It comes with a reference verifier that checks a chain end to end.

A versioned schema for an entry, its lines, its evidence and its two clocks. Importers, exporters and verifiers can then work against the definition Syderial uses.

A small library with the five label axes and the dominance rule. It answers whether a line may reach a reader, using the rule the record uses.

Machine-checkable specifications of the record’s core rules. The record admits only supported lines, corrections never rewrite an entry, labels only get stricter, and every consequential step leaves a receipt.

The configuration fragments and capture hooks for coding harnesses, and examples for connecting MCP clients, so you can read the integration code you run.

The context compiler, the extraction and entailment pipeline and the service that runs the doors stay proprietary. We’re opening the parts you need to check the record and keeping closed the parts that produce it.

We’ll announce each release on syderial.ai, X and GitHub. To review a part before it opens, get in touch.