Anu Script — Manager 7.0

In ASM 7.0, the SEG recognizes the anomaly pattern, injects a pre-processing shim (a built-in Python function you wrote months ago for a different job), repairs the header on the fly, and logs the intervention. The script succeeds. The on-call engineer never wakes up.

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.

How we rebuilt ASM from a script runner into a cognitive automation fabric. Anu Script Manager 7.0

This is not AI. This is engineered memory . And it's deterministic. Let's talk about the scheduler. We threw out the cron emulation.

Every ASM agent now has a verifiable workload identity. No shared SSH keys. No long-lived API tokens. In ASM 7

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?"

12 minutes Prologue: The Breaking Point of Traditional Automation For five years, Anu Script Manager (ASM) was our scalpel. We used it to schedule Python scripts, orchestrate cloud migrations, and glue together APIs that were never meant to be friends. Version 6.x was reliable. It was fast. But somewhere between managing 500 cron jobs and handling dynamic secret rotation, we hit a wall. You can now run scripts from untrusted tenants

The internal database schema changed. The plugin API is deprecated (replaced by the contract system). And the scheduler state is not backward-compatible.