make tee section lighter

Author: aimen-djari

src/get-started/protocol/tee/intel-sgx.md

@@ -13,48 +13,13 @@ the iExec platform, SGX is the **production-ready, widely-supported TEE
 technology** that powers secure, privacy-preserving applications in the
 decentralized cloud.
 
-## Why SGX Matters for iExec
-
-iExec has chosen SGX as its primary TEE technology because it provides the
-perfect balance of **security, stability, and accessibility** for decentralized
-computing:
-
-### 🔒 **Decentralized Security**
-
-- **Hardware-Level Protection**: SGX provides hardware-level security guarantees
-  regardless of who owns the worker hardware
-- **Trust in Untrusted Environments**: Users can trust computation results even
-  from unknown workers in the network
-- **Proof of Contribution**: SGX enables verifiable proof that computations were
-  executed correctly
-
-### 💰 **Data Monetization Platform**
-
-- **Protected Data Processing**: Data owners can safely monetize their data
-  without losing control
-- **Secure Computation**: Sensitive data remains encrypted during processing
-- **Access Control**: Fine-grained control over who can access and process data
-
-### 🌐 **Global Computing Network**
-
-- **Wide Worker Support**: SGX is supported by the majority of iExec workers
-- **Reliable Execution**: Production-ready technology with proven stability
-- **Cost-Effective**: Standard pricing due to wide availability
-
 ## What is Intel SGX?
 
-[Intel® SGX](https://software.intel.com/en-us/sgx) is a technology that enables
-**Trusted Computing** and **Confidential Computing**. At its core, it relies on
-the creation of a special zone in the memory called an "enclave". This enclave
-can be considered as a vault, to which only the CPU can have access. Neither
-privileged access-levels such as root, nor the operating system itself is
-capable of inspecting the content of this region. The code, as well as the data
-inside the protected zone, is totally unreadable and unalterable from the
-outside. This guarantees non-disclosure of data as well as tamper-proof
-execution of the code.
-
-An application's code can be separated into "trusted" and "untrusted" parts
-where sensitive data is manipulated inside the protected area.
+[Intel® SGX](https://software.intel.com/en-us/sgx) creates a special secure
+zone in memory called an "enclave" - think of it as a vault that only the CPU
+can access. Neither the operating system nor any other software can see what's
+happening inside this protected area. Your code and data are completely private
+and secure.
 
 ## SGX: The "Application-Level" Security
 
@@ -66,54 +31,16 @@ applications.
 
 - **Scope**: Protects specific parts of your application
 - **Memory**: Limited secure memory (like a small safe)
-- **Code Changes**: Requires significant modifications to your application
+- **Code Changes**: Requires modifications to your application
 - **Use Case**: Perfect for focused, lightweight applications
 
 **Analogy**: SGX is like installing a small, specialized safe inside your office
 for specific valuable items.
 
-### Visual Representation
-
-```mermaid
-graph TB
-    OS[Operating System<br/>Can see everything]
-    App[Regular Application<br/>Visible & Vulnerable]
-    Enclave[🔒 SGX Enclave<br/>Protected]
-    Data[Sensitive Code & Data<br/>Encrypted]
-
-    OS --> App
-    App --> Enclave
-    Enclave --> Data
-
-    style Enclave fill:#ffffff,stroke:#0000ff,stroke-width:2px,color:#000000
-    style Data fill:#ffffff,stroke:#00ff00,stroke-width:2px,color:#000000
-```
-
-## SGX Technology Details
-
-### How SGX Works
-
-1. **Enclave Creation**: SGX creates a secure memory region (enclave) that only
-   the CPU can access
-2. **Code Isolation**: Sensitive code runs inside the enclave, isolated from the
-   rest of the system
-3. **Memory Encryption**: All data in the enclave is automatically encrypted
-4. **Integrity Protection**: The enclave can prove it's running the correct,
-   unmodified code
-
-### SGX Limitations
-
-With native Intel® SGX technology, the OS is not a part of the Trusted
-Computing Base (TCB), hence system calls and kernel services are not available
-from an Intel® SGX enclave. This can be limiting as the application will not be
-able to use File System and sockets directly from the code running inside the
-enclave.
-
-## SGX with iExec and Scone
+## SGX with iExec
 
 iExec has built a comprehensive SGX infrastructure that makes it easy for
-developers to create secure, privacy-preserving applications without deep SGX
-expertise.
+developers to create secure, privacy-preserving applications.
 
 ### iExec's SGX Infrastructure
 
@@ -126,88 +53,3 @@ iExec provides a complete SGX ecosystem that includes:
   execution
 - **🔗 Blockchain Integration**: Decentralized coordination and payment
 - **📦 Scone Framework**: High-level development framework for SGX applications
-
-### Why iExec Uses Scone
-
-To build Confidential Computing (TEE) applications with SGX, iExec uses the
-high-level **Scone framework** instead of requiring developers to manipulate the
-Intel® SGX SDK directly.
-
-#### Scone Framework Benefits
-
-At a high-level, Scone protects the confidentiality and integrity of the data
-and the code without needing to modify or recompile the application. The
-[Scone](https://scontain.com/) framework resolves the limitations of native SGX
-and reduces the burden of porting the application to Intel® SGX.
-
-#### How Scone Works
-
-More precisely, Scone provides a C standard library interface to container
-processes. System calls are executed outside of the enclave, but they are
-shielded by transparently encrypting/decrypting application data. Files stored
-outside of the enclave are therefore encrypted, and network communication is
-protected by Transport Layer Security (TLS).
-
-For a deeper understanding, you can have a look to the official
-[Scone documentation](https://sconedocs.github.io/).
-
-### iExec SGX Workflow
-
-```mermaid
-graph TD
-    Dev[Developer]
-    Build[Build with Scone]
-    Deploy[Deploy to iExec]
-    Worker[SGX Worker Selected]
-    Enclave[SGX Enclave Created]
-    Execute[Secure Execution]
-    Proof[Proof of Contribution]
-    Result[Results]
-
-    Dev --> Build
-    Build --> Deploy
-    Deploy --> Worker
-    Worker --> Enclave
-    Enclave --> Execute
-    Execute --> Proof
-    Proof --> Result
-
-    style Enclave fill:#ffffff,stroke:#0000ff,stroke-width:2px,color:#000000
-    style Execute fill:#ffffff,stroke:#0000ff,stroke-width:2px,color:#000000
-```
-
-## SGX Use Cases on iExec
-
-### Best For
-
-- ✅ **Production Applications**: SGX is production-ready and stable on iExec
-- ✅ **Lightweight Applications**: Perfect for focused, high-assurance modules
-- ✅ **Crypto Operations**: Wallets, cryptographic key operations
-- ✅ **Small AI Models**: Lightweight machine learning applications
-- ✅ **Maximum Compatibility**: Widely supported by iExec workers
-
-## When to Use SGX
-
-**SGX is ideal for**:
-
-- ✅ Building production applications
-- ✅ Need proven, stable technology
-- ✅ Working with lightweight applications
-- ✅ Require maximum worker availability
-- ✅ Need focused security for specific application parts
-
-## What's Next?
-
-**Learn about the next generation**:
-
-- **[Intel TDX Technology](/get-started/protocol/tee/intel-tdx)** -
-  Next-generation VM-level TEE technology
-- **[SGX vs TDX Comparison](/get-started/protocol/tee/sgx-vs-tdx)** - Detailed
-  comparison of both technologies
-
-**Ready to build with SGX?** Check out the practical guides:
-
-- **[Build & Deploy](/guides/build-iapp/build-&-deploy)** - Create your first
-  SGX application
-- **[Advanced SGX Development](/guides/build-iapp/advanced/create-your-first-sgx-app)** -
-  Deep dive into SGX development

src/get-started/protocol/tee/intel-tdx.md

@@ -13,48 +13,11 @@ virtual machine-level protection. On the iExec platform, TDX is an
 **experimental technology** that offers advanced capabilities for
 memory-intensive workloads and legacy application migration.
 
-## Why TDX Matters for iExec
-
-iExec is exploring TDX as the next evolution of TEE technology to address the
-limitations of SGX and enable new use cases:
-
-### 🔬 **Research and Innovation**
-
-- **Future-Proofing**: iExec is preparing for the next generation of TEE
-  technology
-- **Advanced Capabilities**: TDX enables new use cases that SGX cannot support
-- **Technology Leadership**: Staying ahead of the curve in confidential
-  computing
-
-### 💾 **Memory-Intensive Workloads**
-
-- **Large AI Models**: Support for complex AI workloads that exceed SGX memory
-  limits
-- **Big Data Processing**: Handle large-scale data analytics in secure
-  environments
-- **Database Applications**: Secure processing of large databases
-
-### 🔄 **Legacy Application Migration**
-
-- **Lift-and-Shift**: Enable existing applications to run securely with minimal
-  changes
-- **Enterprise Adoption**: Make it easier for enterprises to adopt confidential
-  computing
-- **Reduced Development Overhead**: Lower barrier to entry for TEE adoption
-
-### 🚀 **Experimental Platform**
-
-- **Limited Availability**: Currently available on experimental worker pools
-- **Research Environment**: Perfect for testing future capabilities
-- **Developer Feedback**: iExec uses TDX to gather developer feedback and
-  improve the platform
-
 ## What is Intel TDX?
 
 **TDX (Trust Domain Extensions)** is Intel's newer confidential computing
-technology, different from the default SGX implementation. TDX provides VM-level
-protection, allowing entire virtual machines to run in secure, isolated
-environments.
+technology that provides VM-level protection, allowing entire virtual machines
+to run in secure, isolated environments.
 
 ### Key TDX Benefits
 
@@ -82,43 +45,6 @@ machines.
 **Analogy**: TDX is like moving your entire office into a secure building where
 everything is protected.
 
-### Visual Representation
-
-```mermaid
-graph TB
-    Hypervisor[Hypervisor<br/>Cannot see inside TDX]
-    TrustDomain[🔒 TDX Trust Domain<br/>Entire VM Protected]
-    App[Your Complete Application<br/>All Protected]
-    Data[OS, Libraries, Data<br/>All Encrypted]
-
-    Hypervisor --> TrustDomain
-    TrustDomain --> App
-    App --> Data
-
-    style TrustDomain fill:#ffffff,stroke:#0000ff,stroke-width:2px,color:#000000
-    style Data fill:#ffffff,stroke:#00ff00,stroke-width:2px,color:#000000
-```
-
-## TDX Technology Details
-
-### How TDX Works
-
-1. **Trust Domain Creation**: TDX creates secure virtual machines called "trust
-   domains"
-2. **VM-Level Isolation**: Entire virtual machines run in isolated, secure
-   environments
-3. **Large Memory Support**: Significantly larger secure memory space compared
-   to SGX
-4. **Legacy Compatibility**: Existing applications can run with minimal
-   modifications
-
-### TDX Advantages
-
-- **Larger Memory**: Multi-GB+ secure memory space vs limited SGX memory
-- **Easier Migration**: "Lift and shift" approach for existing applications
-- **Better Performance**: Optimized for complex, memory-intensive workloads
-- **VM-Level Security**: Protects entire virtual machines, not just applications
-
 ## TDX with iExec
 
 iExec is actively exploring TDX technology to expand the platform's capabilities
@@ -133,79 +59,3 @@ iExec provides experimental TDX support through:
 - **🔐 Secret Management Service**: SMS support for TDX applications
 - **📋 Task Verification**: Proof of contribution for TDX executions
 - **🔗 Blockchain Integration**: Decentralized coordination and payment
-
-### iExec TDX Workflow
-
-```mermaid
-graph TD
-    Dev[Developer]
-    Build[Build TDX App]
-    Deploy[Deploy to iExec]
-    Worker[TDX Worker Selected]
-    TrustDomain[TDX Trust Domain Created]
-    Execute[Secure Execution]
-    Proof[Proof of Contribution]
-    Result[Results]
-
-    Dev --> Build
-    Build --> Deploy
-    Deploy --> Worker
-    Worker --> TrustDomain
-    TrustDomain --> Execute
-    Execute --> Proof
-    Proof --> Result
-
-    style TrustDomain fill:#ffffff,stroke:#0000ff,stroke-width:2px,color:#000000
-    style Execute fill:#ffffff,stroke:#0000ff,stroke-width:2px,color:#000000
-```
-
-## TDX Use Cases on iExec
-
-### Best For
-
-- 🔬 **Research and Development**: Testing future capabilities on iExec
-- 🧪 **Experimental Features**: Exploring new TEE possibilities
-- 💾 **Memory-Intensive Applications**: AI workloads, large databases
-- 🔄 **Legacy Applications**: Existing applications that need TEE protection
-- 🚀 **Complex Workloads**: Applications requiring large memory and processing
-  power
-
-## Current Limitations
-
-:::danger Production Warnings
-
-- **🚫 NOT for production use**
-- **🚫 Limited worker availability**
-- **🚫 Unstable execution environment**
-- **🚫 Breaking changes** without notice
-
-:::
-
-## When to Use TDX
-
-**TDX is ideal for**:
-
-- 💾 Working with memory-intensive applications
-- 🔄 Running existing applications with minimal changes
-- 🚀 Running complex workloads with VM-level protection
-
-## What's Next?
-
-**Learn about the foundation**:
-
-- **[Intel SGX Technology](/get-started/protocol/tee/intel-sgx)** -
-  First-generation application-level TEE technology
-- **[SGX vs TDX Comparison](/get-started/protocol/tee/sgx-vs-tdx)** - Detailed
-  comparison of both technologies
-
-**Ready to experiment with TDX?** Check out the practical guides:
-
-- **[Build Intel TDX App (Experimental)](/guides/build-iapp/advanced/create-your-first-tdx-app)** -
-  Build TDX applications with traditional deployment and iApp Generator
-- **[Create Your First TDX App](/guides/build-iapp/advanced/create-your-first-tdx-app)** -
-  Build TDX applications
-
-**For production applications, use SGX**:
-
-- **[Build & Deploy](/guides/build-iapp/build-&-deploy)** - Create
-  production-ready SGX applications