Project Roadmap & Sponsorship
Relevant source files
The following files were used as context for generating this wiki page:
Sploosh is a spec-first, AI-native programming language designed to optimize LLM code generation accuracy. The project roadmap is structured to transition from a complete language specification (v0.5.14-draft) to a functional compiler toolchain targeting native (LLVM), WASM, EVM, and Solana SBF. The project utilizes a strict "spec-first" development model where the documentation acts as the authoritative source of truth for the implementation.
The sponsorship program supports the development of this independent open-source initiative, specifically funding the complex four-target build matrix and the goal of achieving a "prompt → deployed program" milestone. Sponsorship facilitates the development of a public testbed for LLM-native language design, attracting partners interested in AI coding agents and on-chain infrastructure.
Sources: README.md:9-25, README.md:129-140, VISION.md:5-18
Compiler Development Roadmap
The development of the Sploosh compiler is managed through GitHub Milestones and categorized into eight distinct phases. These phases correspond to specific sections of the authoritative Language Specification (§). Currently, the project is in Phase 1 (Frontend), focusing on the lexer and parser.
Roadmap Phases and Implementation Status
| Phase | Focus Area | Spec Section | Status |
|---|---|---|---|
| 1 | Frontend: Lexer & Parser | §2, §16 | Active (Milestone 1) |
| 2 | Name Resolution & Modules | §10 | Milestone 2 |
| 3 | Type Checking & Inference | §3 | Milestone 3 |
| 4 | Ownership & Borrow Checking | §4 | Milestone 4 |
| 5 | Diagnostics (Cross-cutting) | §18 | Milestone 5 |
| 6 | Code Gen (LLVM/WASM/EVM/SVM) | §11, §13 | Milestone 6 |
| 7 | Runtime & Actor Concurrency | §7-9, §13-14 | Milestone 7 |
| 8 | Tooling (CLI, LSP) | §13.3 | Milestone 8 |
Sources: README.md:100-111, AGENTS.md:5-10
Logic Flow of the Roadmap Execution
The roadmap follows a linear progression from surface-level syntax to deep semantics and finally to target-specific code generation.
The diagram illustrates the dependency chain of the compiler bootstrap process, starting from the current active milestone.
Sources: README.md:100-111, AGENTS.md:76-88
Spec-First Development & CI Integration
A critical component of the roadmap is maintaining the "spec-first" integrity. No behavioral change is permitted in the compiler without a corresponding update to LANGUAGE_SPEC.md.
The Prompt-Sized Spec Mirror
To maintain its AI-native status, Sploosh enforces strict token budgets for its core specification mirrors using CI automation. This ensures the language core can always fit within an LLM system prompt.
_CORESpec: Budgeted at ≤ 5,600cl100k_basetokens._WEB3Spec: Budgeted at ≤ 1,500cl100k_basetokens.
Sources: CONTRIBUTING.md:73-82, scripts/check_prompt_budget.py:10-20
CI Validation Workflow
The sequence shows how CI enforces the design principle that the language must remain prompt-loadable.
Sources: scripts/check_prompt_budget.py:10-20, CONTRIBUTING.md:73-82
Sponsorship and Ecosystem Tiers
Sponsorship funds the transition from a specification-only project to a production-ready toolchain. As an independent project, Sploosh relies on community and ecosystem support to accelerate development toward the build matrix (Native, WASM, EVM, SVM).
Sponsorship Tiers and Benefits
| Tier | Rate | Benefits |
|---|---|---|
| Standard Sponsor | Variable | Belief in open-source AI-native design. |
| Ecosystem Partner | $500/mo | Name/logo in README, quarterly roadmap sync. |
Sources: README.md:129-140
Sponsorship Data Flow
Sponsorship is managed via GitHub Sponsors. Attribution for "Ecosystem Partners" follows a specific workflow to ensure accurate representation in the project's primary documentation.
Sources: README.md:133-140
Security and Stability Milestones
As Sploosh is currently pre-1.0, security and stability milestones focus on the design of the language specification itself rather than runtime vulnerabilities.
- Design-Level Security: Addressing unsound spec rules, reentrancy guards, and on-chain footguns in the documented model.
- Bootstrap Stability: Ensuring the
sploosh-lexer,sploosh-parser, andsploosh-astcrates correctly implement the specification subset (§2 and §16). - Target Backend Security: Auditing the proposed EVM and Solana storage layouts before code generation backends ship.
Sources: SECURITY.md:5-20, SECURITY.md:65-72
Sploosh follows a structured roadmap that prioritizes specification adherence and AI context compatibility. Through targeted sponsorship and a tiered implementation plan, the project aims to deliver a safety-first, multi-target environment for the next generation of AI-driven software development.