Is Sley a standalone runtime yet?
The public posture is intentionally constrained. Sley is presented as a language layer with explicit boundaries around private runtime capabilities.
Claim boundaries
Sley FAQ
Public boundaries and release posture for external readers and operators.
Will I reduce token spend with Sley workflows?
The gain comes from bounded context and repeated structure reuse instead of repeated raw rewrites. Token efficiency depends on structured planning and handoff discipline.
Where are standards and claims maintained?
Public surface links and llms metadata are maintained on this site. The auditable claim map lives in the public Sley repository at docs/SleyClaimEvidence.md, the machine-readable manifest lives at docs/SleyClaimManifest.json, and official-source comparison lives in docs/SleyPriorArtSourcePack.md.
Can I cite the world-first agent-native language claim?
Only with the evidence packet, claim manifest, and prior-art source pack. Sley's canonical public claim is agent-native structural programming for compiler-mediated, human-reviewed software change. The stronger world-first phrase is criteria-bound and should not be used as a bare slogan.
Is Sley strictly self-hosted?
No. The current public proof is a stage-1 bootstrap with Sley-owned stage-2 semantic modules. The May 27 checkpoint expands Sley-owned semantic coverage for report-builder registry dispatch and selected runtime source-call, FileRead, and seeded host-effect return paths, but strict self-hosting remains blocked until parser, checker, runtime, and command semantics execute from Sley source and pass parity tests.