Osprey specifications

Choose a subject. Platform applications and development tools have their own contracts; they are not part of the core language specification.

Core language and compiler

• Language — Syntax, types, expressions, effects and module semantics.
• Compiler — Target lowering, generated ABIs and debug artifacts.

Supporting systems

• Runtime libraries — Built-in library contracts and execution services.
• Platform integration — WASI/browser hosts, iOS and Android applications.
• Developer tooling — Language server, editor, documentation and test tools.
• Packages and automation — Package registry, evidence and GitHub automation.
• Application frameworks — Reactive mobile applications, the proof workbench and its lessons, the Osprey Agent, host protocols, and the local coding model.

Contract and delivery

These documents define required behavior. A specification is not evidence that a feature has shipped. Each contract records its limits; feature status and the linked delivery plans distinguish implemented behavior from unfinished work.