Skip to main content

Flagship 01 / Sley

Software change, made structural.

Sley 1.2.0 preserves the completed human-readable lineage with readable source, intent, authority, and verification visible. Sley 2.x is the active, intentionally incompatible machine-native lineage.

Open Active SleyExplore Sley Legacy 1.2.0Read the lineage break
Sley structural graph flowing through typed language layers
SourceStructureAuthorityVerification

Current project status

Sley 1.2.0 is the completed, frozen human-readable legacy line. Active development continues in the separate, intentionally incompatible machine-native Sley 2.x repository. The 1.x line remains available for historical use, compatibility, study, experimentation, and forks.

Read the architectural transition
examples/project/src/app/main.sleyACTUAL SOURCE
module app.compute

task classify -> Text {
  take score: Int
  return if score >= 90 { "excellent" } else { "steady" }
}

task main -> Text {
  bind score = 40 + 55
  return call classify(score)
}

The Sley 1.x line

Readable syntax. Structural reports. Separate authority.

This example is real Sley 1.x source from the public repository. Its call structure can be queried before any write is authorized. Direct readability remains a defining property of the open 1.x architecture, not a requirement for 2.x.

Why it exists

Text is not the whole program.

Conventional editing asks a system to infer structure from text, change it, and explain the result afterward. Sley makes structure part of the language surface before mutation begins.

Terminal evidence

sley query --json --kind calls examples/project

"schema": "sley.query.report.v0"

"kind": "calls"

"entry_module": "app.main"

"modules": 2, "calls": 1

A bounded change lifecycle
  1. 01Inspect structure
  2. 02Plan transformation
  3. 03Authorize scope
  4. 04Verify evidence
release targets
38 / 38
report schemas
99
contract fixtures
187 / 187
corpus cases
72
integration checks
264 / 264

Sley 1.2.0 release-candidate evidence recorded August 27, 2026.

What systems can inspect

  • Typed structural nodes and relationships
  • Declared intent and transformation boundaries
  • Available capabilities before a write
  • Deterministic reports and verification results

What people retain

  • Readable source and an explicit proposed change
  • Authority over whether the proposal may execute
  • A reviewable boundary between reports and mutation
  • Evidence tied to the exact checkpoint being discussed

Inspect the evidence

Standalone site Language specification Claim evidence Architectural transition
Back to productsExplore Open Source