Machine-native programming for AI agents.

Active lineage · pre-release engineering

Sley 2 - the canonical Sley

The canonical site is sleylang.org. Sley 2 is developed in a private Greyforge Labs repository; this site is its public record. Current workspace/source version: 2.0.0-alpha.0 - a workspace pre-release, not a released product, GitHub release, package, or GA. The license declaration is LicenseRef-Proprietary; the source is private and not open source.

Machine-native for AI agents. The canonical raw program representation is intentionally not required to be comfortable human source. Agents work through projections, inspection, policy roots, capability tokens, objectives, constraints, receipts, and acceptance - not by authoring canonical bytes.

• Active: Sley 2 (private repository, Greyforge Labs) - SSMC1 canonical form · SCB1 canonical encoding · SMP1 designated interface · 2.0.0-alpha.0 · LicenseRef-Proprietary
• Legacy: GreyforgeLabs/sley-legacy - Sley 1.2.0 frozen · human-readable canonical source · self-hosted 1.x compiler · Apache-2.0
• Transition: Sley 1.2.0 → Machine-native break Chronicle · source note

Current phase

Active pre-release engineering - not research, not GA

M0 is complete. M1 core (SCB1, identifiers, independent oracle, epochs, immutable store, deterministic roots, root/object packs) is complete. M2 is advancing - deterministic type, CFG, effects, restricted contracts, fingerprints, lowering, VM, adapters, and policy now have bounded implementations for the supported subset. Full-GA semantics, complete operation analysis, and release hardening remain incomplete. The exact work-package DAG is maintained in the private repository; the technical brief tracks its milestone state.

Follow Sley

Updates from the machine-native lineage

@SleyLanguage - Sley updates · @GreyforgeLabs - lab updates · Sley 2 technical brief - public record

Typed semantic state

Programs are SSMC1 typed state, not canonical human source. Canonical form and canonical SCB1 encoding are the source of truth.

Deterministic identity

Immutable objects and deterministic state roots give every verified state a stable, content-addressed identity; roots are order-independent.

Proposal before mutation

Machines construct proposal-only mutation candidates - never direct mutation. Every candidate is digest-trailed SLEYCAN1 with exact discriminants.

Validation before commit

A fourteen-phase restricted validator owns every outcome before the durable atomic transaction commits. Unsupported semantics fail closed.

Explicit policy & capability

Protected policy roots and BLAKE3-authenticated capability tokens bind root / effect / scope / adapter / budget with deterministic authority.

Native versioned state

Atomic named branch refs over verified receipts: immutable origin records, CAS advancement, bounded deterministic ancestry. Merge, force-reset, and clone exchange remain gaps.

Bounded deterministic execution

Restricted O0 lowering and VM for the validated Boolean/terminator subset executes with exact fuel, value, and observation digests. Other opcodes remain fail-closed.

Human inspection & evidence

Readable projections, diagnostics, QueryId-typed queries, evidence capsules, receipts, and deterministic error behavior - machines mutate verified state with deterministic evidence.

State → Proposal → Validation → Transaction → Verified State

How a machine changes a Sley 2 program

1. Verified state root - begin from a deterministic StateRoot over immutable canonical bytes.
2. Derive bounded context - derive freshly rebuilt snapshots and typed queries; candidates match only an already-fresh explicit modeled-request rebuild.
3. Proposal-only candidate - build an immutable digest-trailed SLEYCAN1 candidate from 179 bound descriptors; no semantic validation yet.
4. Deterministic validation - fourteen-phase validator owns every outcome; unsupported semantic operations and insufficient capability fail closed.
5. Atomic transaction - commit-time revalidation, durable object + receipt ordering, and one fixed-head compare-and-swap promotion.
6. Advance a branch - named ref CAS from direct parent, deterministic ancestry, coordinated maintenance.
7. Retain receipts & evidence - canonical receipts, observation digests, query responses, and evidence capsules for acceptance.

Sley 2 is a privately developed pre-release implementation, not an installed language release. No stable end-user CLI/API is claimed beyond thin machine wrappers that delegate all judgment to the kernel.

Boundaries

What Sley 2 is intentionally not - yet

• 52 opcode signatures, generics, adapters, VM adapter opcodes, live host/policy transitions, sessions, providers, and deployment remain explicit gaps
• 19 root-backed query classes, truncation/continuation, master ContextCapsule, SMP1 protocol framing, and JSON bridge are deferred (SMP1 is designated, not claimed implemented)
• Complete semantic-operation analysis, production fingerprint hardening, and full S20-530 crash-matrix implementation remain gaps
• Merge, force-reset, symbolic refs, tags, branch deletion, and clone-equivalent pack exchange are not supported
• Sley 2 is a privately developed pre-release, not an installed language release - no GA, tag, package, or production claim

Full-GA blockers remain: six unmodeled entity bodies, unsupported opcode families, trunk truncated query coverage, master capsule, live provider/shell/network authority, and complete S20-530 recovery implementation. This page and the technical brief track exact status.

Sley 1.x Legacy - preserved

Looking for human-readable Sley 1.2?

Sley 1.2 completes the human-readable structural line - self-hosted compiler, 99 report schemas, 187 contract fixtures, 72 corpus cases, 264 integration checks. It remains frozen and available under Apache-2.0.