AEGIS Core 3.4.0 — Process-local one-shot execution grants

🔐 Summary

AEGIS Core 3.4.0 introduces an explicit process-local execution disposition for authorization receipts.

The new execution_permitted field separates the historical signed policy decision from permission to dispatch an external tool during the current process execution.

Integrations must execute protected tools only when:

if receipt["execution_permitted"] is True:
    execute_protected_tool()

🔎 Previous behavior

In AEGIS Core 3.3.0, an exact replay returned its historical receipt with:

• policy_decision: allow
• cached: true

An integration dispatching tools solely from policy_decision == "allow" could therefore execute the external action again for every cached replay.

Baseline reproduction with 100 concurrent requests using the same tool_call_id:

• New authorizations: 1
• Cached replays: 99
• Simulated external executions: 100
• Result: FAIL — duplicate external execution

🛠 What changed

• Added execution_permitted to authorization receipts.
• Fresh allowed authorization: execution_permitted: true.
• Exact cached replay: execution_permitted: false.
• Denied or failed authorization: execution_permitted: false.
• Updated documented enforcement patterns and examples.
• Added a 100-request same-ID concurrency regression test.
• Added GitHub Actions CI for Python 3.8, 3.11 and 3.12.
• Removed legacy demonstration scripts containing simulated or unsupported claims.
• Synchronized package, module and documentation versions to 3.4.0.

✅ Verification

Corrected 100-request same-ID contention result:

• Historical allow responses: 100
• New authorizations: 1
• Execution grants: 1
• Cached replays: 99
• Simulated external executions: 1
• Final balance: 0.000000
• Result: PASS

Additional verification:

• Financial-loss adversarial matrix: 12/12 PASS
• L3 settlement security suite: 7/7 PASS
• Micropayment precision suite: 4/4 PASS
• 1,000-way limited-budget contention: 1 allow / 999 deny / PASS
• Integration, enforcement, rollback, idempotency-conflict, binding, key-failure and concurrency tests: PASS
• GitHub Actions: Python 3.8, 3.11 and 3.12 PASS
• Wheel and source distribution: Twine checks PASS
• Isolated wheel installation and same-ID contention test: PASS

📦 Upgrade

pip install --upgrade aegis-core-lortuarte-sdk==3.4.0

After upgrading, external tool dispatch must use execution_permitted, not the historical policy_decision, as its execution condition.

⚠️ Current scope

This release establishes a one-shot execution grant within the documented process-local integration boundary.

It does not claim:

• Exactly-once external side effects
• Crash recovery after external dispatch
• Cross-process or multi-node atomicity
• Automatic reserve / commit / release reconciliation
• Internet-scale production readiness

AEGIS Core SDK v3.0.3 - Clean Release

First clean production release for PyPI.