ACE-Echo 1.0 is the development platform for Venus applications. Its current scope is defined by the release source, selected hardware backend and recorded validation cases.
- 01DefineInputs, outputs and reference
- 02DevelopVenus C tasks + BAS DAG
- 03SimulateGem5 on a selected backend
- 04EvaluateOutput agreement + timing
Current capabilities
| Capability | Included in the 1.0 workflow |
|---|---|
| Application authoring | Venus C tasks and BAS descriptions of task dependencies |
| Compilation | Bundled DSL frontend connected to a separately installed Venus-custom LLVM toolchain |
| Simulation | Gem5 task, DAG and application-contract execution |
| Performance exploration | Cycle-level modelling and approximate timing on the selected backend |
| Output checking | Explicit comparison against a supplied reference; input and output identities recorded per run |
| Agent assistance | Forge requests and repository skills used by an external AI coding host |
| Reproducibility | Per-run commands, logs, configuration identities and generated artifacts |
Application coverage
The published Venus1 regression covers nrPBCH, nrPDCCH, ltePBCHDag1_hw, ltePBCHDag2_hw, ltePCFICH, ltePDCCHDag1_hw, ltePDCCHDag2_hw and ltePDSCH. The validation report explains timing agreement and remaining output-correctness limits.
The bundled two-task vector smoke is the starting point for installation checks. Broader 5G/LTE workflows and communication–AI research belong to the project ecosystem; they do not imply that every operator, input combination or end-to-end application is qualified by this release.
Scope boundaries
The release does not provide an automatic BAS-to-RTL exporter, a general CPU/GPU execution fallback, a visual DAG editor, or automatic ASIC power/resource reports.
The L1 application-contract engine models a Scheduler execution plan; it does not execute the complete scalar Scheduler firmware. RTL runs need separately supplied hardware sources and tools. Full intent-to-deployable-application generation belongs to the 2.0 roadmap.
For exact command scope, see the pinned platform README and coverage contract.