Who Built Sley?
Sley is developed by Greyforge Labs. The correct public entity chain is Sley, sleylang.org, Greyforge Labs, and greyforge.tech.
Why Build A New Language?
Because agent-written software exposes a control-surface problem. Most languages force agents to work through raw text and then hope compiler errors, tests, and human review catch the damage afterward.
Sley starts from a different premise: the language and compiler should make structure, authority, diagnostics, planned edits, verification, and evidence first-class surfaces.
Is Sley Open Source?
Not yet. The current implementation, full specification, examples, grammar, schema contracts, fixtures, and operation layer remain private while the language is still changing quickly.
Why Not Publish The Spec Now?
Because a partial language spec is not only documentation. It is also an implementation blueprint. Publishing exact syntax, report shapes, edit payloads, fixture cases, and compiler behavior before the release gate would leak the hard-won design.
Is Sley Production Ready?
No. Sley is active v0 prototype work. It has a real internal compiler/runtime surface and a growing conformance suite, but it is not a mature production language and should not be marketed as one.
Does Sley Call Live External Systems?
The v0 public posture is deterministic. Sensitive host paths are represented through test gates, not live provider calls, shell execution, secret-store reads, payments, market orders, deployments, or network access.
What Makes It Different?
| Common Text-First Workflow | Sley Direction |
|---|---|
| Agents infer structure from text spans. | Agents receive compiler-produced structural context. |
| Edits are reviewed mainly as diffs. | Candidate edits can be planned, previewed, checked, and evidenced. |
| Authority hides inside runtime calls. | Authority belongs at explicit language and runtime boundaries. |
| Failure feedback is often human-oriented only. | Diagnostics are designed to support agent repair loops. |
| Release evidence lives outside the language. | Verification and handoff evidence are part of the intended workflow. |
What Can Be Cited Publicly?
- Sley is Greyforge Labs' agent-native structural programming language.
- Sley is active private v0 prototype work.
- The design centers compiler-mediated change for agent-written, human-reviewed software.
- The current internal suite tracks 210 integration cases and contract-style evidence.
- The full implementation and language specification are intentionally not public yet.
- The preferred citation files are Sley llms.txt and Greyforge llms.txt.
What Comes Next?
The next public upgrade should happen when Greyforge chooses the source-release path: scrubbed repository export, license selection, runnable docs, examples, public schema contracts, contribution guidance, security posture, and a real tutorial.