Anu Script Manager 7.0: Beyond Orchestration—The Age of Autonomous Workflow Intelligence
We don't believe in "Ask ASM to deploy the stack." Ambiguity is the enemy of automation. Scripts are code. Code is precise. We won't paper over that with a chat bot. Anu Script Manager 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. Anu Script Manager 7
How we rebuilt ASM from a script runner into a cognitive automation fabric. We won't paper over that with a chat bot
The internal database schema changed. The plugin API is deprecated (replaced by the contract system). And the scheduler state is not backward-compatible.
You can now run scripts from untrusted tenants on the same ASM cluster. The identity plane prevents cross-tenant leakage. Even if a script is malicious, it cannot exfiltrate data it never had permission to see. Part 5: The Observability Shift – Traces, Not Logs Logs are dead. Long live traces.
So, we stopped adding features to 6.x. Instead, we asked a dangerous question: What if the script manager remembered?