The project carries the context.
AceLM is being designed to preserve specifications, plans, decisions, and verification records alongside the code they describe.
Continue the work with its history.
A new session or a different clone should not require rebuilding the project's history from scattered conversations. AceLM is intended to read versioned project records, reconstruct lifecycle state, and make the next steps and unresolved decisions visible.
Standalone installation
Install AceLM independently of your repositories and open projects with alm. Fast local indexing is planned to keep navigation and lifecycle queries responsive.
Records that travel with Git
Shared specifications, plans, decisions, and verification summaries are intended to travel through committed project records. Another clone can pick up the lifecycle information that has been shared.
Live work that survives connection loss
Persistent sessions are planned to keep agents, shells, and tests running on their execution host when a terminal connection drops. Reconnect to that host to return to the live work.
Verification tied to the work
Planned verification records link check results to the requirements and code revision they evaluated, making gaps and outdated evidence easier to identify.
Explore Planned Capabilities
Inspect the nine core capabilities planned for the AceLM terminal workspace.
View planned capabilities