The internal database schema changed. The plugin API is deprecated (replaced by the contract system). And the scheduler state is not backward-compatible.
But we added one proprietary twist: .
Anu Script Manager 7.0 is our statement that automation should be seen, not hidden. docker pull anuscript/manager:7.0-beta
— The Anu Core Team We open-sourced the Stateful Execution Graph prototype. [Link to GitHub.]. Contribute, critique, or just stare at the complexity. All feedback welcome.
In 7.0, .
ASM asks the script, "What files, APIs, or services do you intend to touch?" The script responds (via a new lightweight manifest API). Phase 2 (Execution): If the resources are available and the contract is honest, ASM executes. If not, it queues a remediation script.
ASM 7.0 exports OpenTelemetry traces natively. Every script execution is a trace. Every subprocess call, every HTTP request from inside the script, every file read – all spans.
How we rebuilt ASM from a script runner into a cognitive automation fabric.
ASM 7.0 can detect failure patterns. But we refuse to automatically retry or reroute without explicit human-defined policies. Autonomous systems that act on false positives cause cascading failures. We give you the data. You write the rules. Part 8: The Road Ahead – Scripts as Infrastructure With 7.0, we've changed the ontology. ASM is no longer a "script runner." It's a control plane for ephemeral, intent-driven workloads .
Or, if you're on 6.x: as-cli upgrade plan --from=v6 --to=v7
Traditional script managers treat each execution as an amnesiac event. Run → Log → Exit. In a world of event-driven architectures, fragile microservices, and self-healing infrastructure, amnesia is a liability.