ONE Mono Repository

Workspace layout

crates/
  syon-parser/     # pest-based parser and emitter, AST in both directions
  syon-cli/        # `syon` binary — parses a .syon file and prints the AST as JSON
  syon-python/     # PyO3 bindings exposing syon-parser to Python
  sheni_types/     # Sheni (layer 2), the type layer over the parsed AST
  shelishi_schema/ # Shelishi (layer 3), user-declared types from a runtime schema
  luach_types/     # calendar-agnostic day count, week, and the calendar contract
  hodesh_calendar/ # the calendars themselves — Gregorian, and hodesh
  shlita_types/    # IEC 61131-3 elementary types and standard functions
syon-go/           # independent, dependency-free Go implementation
spec/              # language specification

A crate's directory, its package, and its library all carry the same name. cargo build -p sheni_types, sheni_types = { path = "../sheni_types" } and use sheni_types::… are then the same word, so there is nothing to look up. Two crates used to have three names between them — package sheni in directory sheni_types with library sheni_types — and every one of the three was wrong somewhere.

The syon-* crates keep Cargo's own convention, where a hyphenated package has an underscored library: syon-parser builds syon_parser. syon-python is the one deliberate exception, whose library is syon because PyO3 requires the cdylib to be named for the module Python imports.

Quick start

task build-parser
task run-cli-binary -- examples/glossary/entries/syon.syon

Examples

Example	Shows
examples/glossary/	A glossary entry and its schema — the language itself
examples/planner/	A task tracker using the type layer, including the soft types. Read through Sheni by crates/sheni_types/tests/planner_example.rs, so it cannot drift from the crate.

Spec

See spec/README.md for the full language specification.

Architecture decisions

See design/architecture/ for the ADR log — why pest was chosen for the Rust parser, why Go got an independent implementation instead of FFI bindings, and other architecturally significant calls.

Each layer numbers its own decisions and the prefix says which layer: syon for the parser and the language, sheni for the type layer above it, shelishi for the schema layer above that, hodesh for the calendar crates and shlita for the IEC 61131-3 control crates, both of which sit alongside rather than on top of the SYON stack.

This is the beginning of the README. Read the rest at the original. Read the full README ↗