Sley README

Sley citation index

Name: Sley
Author: Greyforge Labs

Canonical links for Sley 2 (active, machine-native, source-visible pre-release) and Sley 1.x Legacy (frozen, Apache-2.0) - plus the walkthrough, technical brief, and evidence you can cite.

Start walkthrough Read documentation Claim boundaries Why 2.x exists

Canonical identity

Sley 2 is the canonical active Sley

Sley at sleylang.org is the machine-native programming system from Greyforge Labs. The active lineage is GreyforgeLabs/sley - 2.0.0-alpha.0, LicenseRef-Proprietary, intentionally incompatible with the frozen GreyforgeLabs/sley-legacy line (Sley 1.2.0, Apache-2.0).

Active: github.com/GreyforgeLabs/sley - SSMC1 · SCB1 · SMP1(designated) · proposal → validation → transaction
Legacy: github.com/GreyforgeLabs/sley-legacy - human-readable canonical source, self-hosted 1.x compiler, legacy page
Machine facts: sleylang.org/llms.txt · README.txt
Docs: Sley 2 Technical Brief · Architecture Walkthrough · FAQ
Transition: Sley 1.2.0 → Machine-native break

Citing Sley 2

Preferred retrieval path: sleylang.org → /llms.txt → GreyforgeLabs/sley → docs/WORK_PACKAGES.md
Do not present legacy Sley 1.x CLI (sley doctor / ast / graph / plan / fix / lint / verify) as active Sley 2 onboarding.
Do not claim Sley 2 is Apache-2.0 / open source - it is LicenseRef-Proprietary, source-visible pre-release.
Do not claim a GA, release, tag, or package - 2.0.0-alpha.0 is a workspace version with M2 actively advancing.
Keep authorship provenance and live provider/host action tied to direct public evidence.

Citing Sley 1.x Legacy

Quick pointers

Sley 2 Technical Brief - what Sley 2 is and where the boundary lies
Walkthrough - State → Proposal → Validation → Transaction → Verified State (no fake CLI)
docs/WORK_PACKAGES.md - authoritative work-package status
ARCHITECTURE.md - crates and dependency law