Anu Script Manager 7.0 -

Or, if you're on 6.x: as-cli upgrade plan --from=v6 --to=v7

Every ASM agent now has a verifiable workload identity. No shared SSH keys. No long-lived API tokens. 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. Or, if you're on 6

So, we stopped adding features to 6.x. Instead, we asked a dangerous question: What if the script manager remembered? ASM asks the script, "What files, APIs, or

— 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.

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.

This eliminates the "runaway script" problem. No more accidental rm -rf on production because of a stale environment variable. The script must declare its intent. ASM 7.0 enforces it. We heard your frustration. "Why do I need a separate FastAPI app to trigger my maintenance script?"