Our direction is to make communication–AI hardware easier to program. The first step is a useful simulator and a guided development workflow; the next is a more complete Agent-assisted path from intent to an application for Venus.
Available in the release branch
1.0
You develop. Echo assists.
Develop applications for Venus with a usable Gem5 simulator, approximate cycle-level performance evaluation and an initial Agent-assisted development framework.
Get started with 1.0 ↗Planned direction
2.0
Your intent. An application for Venus.
Our goal is for an Agent to turn your application intent into an implementation deployable on Venus, including generation, iteration and validation. This is a future platform goal; no release date is announced here.
What changes between releases
| ACE-Echo 1.0 | ACE-Echo 2.0 direction | |
|---|---|---|
| Starting point | A developer-defined task, DAG and reference | A user-defined application intent |
| Development | Venus C/BAS with initial Agent assistance | Agent-led generation and iterative improvement |
| Evaluation | Gem5 output checks and approximate timing | Validation integrated into the generation loop |
| Result | An implementation the developer reviews and evaluates | An application intended for deployment on Venus |
The 2.0 column describes planned behavior. Its release date and final supported application scope have not been announced here.
Software versions and hardware generations
ACE-Echo 1.0 / 2.0 name platform releases. Venus 1.0 / 2.0 name hardware backends. A Venus2 backend in the source tree does not mean the ACE-Echo 2.0 Agent workflow has shipped. The 1.0 website’s reported regression targets Venus1.
Previous plans
Explore the platform’s early development in the v0.1 release record. The roadmap above describes the current direction.