Security and Trust
Phase C A1a: split security/ + ai/ out of architecture/ (23 articles, 46 EN+ES files); category frontmatter fixed; redirects.yaml 301s; new _index.md landings
@@ -0,0 +1,25 @@ --- schema: foundry-doc-v1 title: "Security and Trust" slug: security-index category: security type: topic content_type: topic quality: complete short_description: "How the platform is protected and how its records are verified: identity and permissions, cryptographic verification, isolation boundaries, how data is handled and kept private, and the supply-chain controls designed to keep code honest." status: active bcsc_class: public-disclosure-safe last_edited: 2026-07-03 editor: pointsav-engineering paired_with: _index.es.md --- The **security** category collects how the platform is protected and how its records are verified. It covers identity and permissions, cryptographic verification, isolation boundaries, how data is handled and kept private, and the supply-chain controls designed to keep code honest from contributor to production. This is the platform's answer to the diligence reader's question — *can this be trusted?* — and the front door for engineers looking up a specific security mechanism: capability-based access control, machine-based authentication, attestation, cryptographic ledgers, and the trust-establishment bootstrap a device passes through before it joins a deployment. ## See also - [Architecture](/architecture/) — how the platform is put together - [Governance and Standards](/governance/) — what was decided and why it is compliant - [Where It Runs](/infrastructure/) — the deployed storage and ledger infrastructure these mechanisms protect