# Container Isolation Execution runs in isolated containers to contain faults and reduce cross-tenant risk. * **Per-run isolation:** Agent jobs execute in ephemeral containers with no shared memory or disk. * **Minimal egress:** Network access is restricted to allow-listed RPCs and APIs; no open internet. * **No secret sprawl:** There are **no private keys** off-chain; session keys are on-chain permissions. Any operational tokens are short-lived and scoped. * **Hardened runtime:** Read-only filesystems where possible, resource quotas, rate limiting, and strict observability. * **Deterministic deployment:** Reproducible builds and checksums to ensure the code that runs is the code that was reviewed. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sail.money/security/infra-safeguards/editor.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.