6. Security and Auditability

maicrotrader treats auditability as infrastructure, not a feature.

Self-custody architecture: Users retain full custody of their funds at all times. No private keys are held by the platform. Vault contracts are non-custodial by design.

On-chain policy hashes: Every STA's configuration policy is hashed and recorded on-chain at deployment. Any change to the policy generates a new hash and a new on-chain record. There is no mechanism to silently alter a deployed vault's behavior.

Immutable decision log: Every agent action is recorded in a structured event log: signal_emitted, risk_check_passed, risk_check_blocked, order_submitted, order_filled, rebalance_triggered. This log is the basis for the attribution feed visible in the dashboard and cannot be retroactively modified.

Risk Agent veto by architecture: The Risk Agent's authority is not a soft check. No trade can reach the Execution Agent without passing a Risk Agent validation against the vault's deployed policy parameters. This is enforced at the system level, not the UI level.

Smart contract audits: The vault contract infrastructure is subject to independent security audit prior to the Strategy Builder launch. Audit reports will be published publicly.

Seasoning-gated vault network: Strategies must demonstrate live performance under real capital before being published to the vault network. The seasoning record is on-chain and verifiable by any depositor before allocating capital.

The combination of non-custodial architecture, on-chain policy records, immutable decision attribution, and mandatory seasoning is what makes "auditable" a structural claim rather than a marketing claim.