Docs
Documentation hub
The first path through Cale docs
Cale spans language design, a compiler pipeline, a standalone debugger, and a release path. This hub gives readers a project map before they dive into the sidebar.
Understand the current project state, build assumptions, and first steps.
LanguageSee how the C lane and Cale lane coexist around the C ABI.
Compiler PipelineFollow C source through SIR, FIR, BCIR, and Sol.
Lacail DebuggerA standalone debugger direction: stop like LLDB, explain more with Cale artifacts.
C ABI / InteropHow Cale stays compatible with OS, kernel, runtime, and existing C boundaries.
Releases / RoadmapSource builds today, GitHub Releases based binaries later.
Blog
Latest posts
Popular topics
What to read first
- C lane
- Compatibility path for C source and ABI boundaries
- SIR/FIR/BCIR/Sol
- The lowering pipeline that keeps source meaning recoverable
- UB facts
- Evidence records for dangerous execution meaning
- Semantic trace
- Links between source spans, IR values, and lower-level locations
- Debug artifact contract
- File-oriented boundary consumed by Lacail
Index
AI-friendly index
Cale provides llms.txt and a Markdown-friendly docs index so AI assistants and crawlers can understand the public documentation structure.