docs: Feature/paypertask

src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md

@@ -11,11 +11,13 @@
 application with Intel TDX technology using both traditional deployment and the
 iApp Generator.
 
-:::danger ⚠️ EXPERIMENTAL FEATURE
+::: info **Experimental Feature**
 
-**TDX support is currently experimental and should NOT be used in production.**
-This feature is provided for testing and development purposes only. Expect
-instabilities, limited compatibility, and potential outages.
+TDX support is currently in experimental phase:
+
+- Stability and confidentiality features are still being tested and refined.
+- Features may evolve based on user feedback, please share your experience on
+  [Discord](https://discord.com/invite/pbt9m98wnU).
 
 :::
 
@@ -24,21 +26,6 @@
 **[Intel TDX Technology](/protocol/tee/intel-tdx)** guide for comprehensive
 explanations of TDX technology and its benefits.
 
-::: info
-
-**Request access to the experimental feature**
-
-- The TDX-powered workerpool is currently in a development environment and not
-  intended for production use.
-- Expect occasional instability or incomplete features. Service is subject to
-  change or discontinuation
-- Development environment only - do not share sensitive data or secrets.
-- Please share any bug reports, suggestions for improvement, or general feedback
-  on your experience.
-- To request early access, please [contact us](https://discord.gg/9h25DQFSCU)
-
-:::
-
 ## Prerequisites
 
 - [Docker](https://docs.docker.com/install/) 17.05 or higher on the daemon and

src/protocol/pay-per-task.md

@@ -1,34 +1,42 @@
----
-title: Pay Per Task Model
-description:
-  Pricing model and task categories for iExec protocol, including computing and
-  deal time limits.
----
+# Task size: pay-per-task
 
-# Pay per task model
+Pay-per-task categories, time limits, and claim rules.
 
-We are introducing a new method for pricing and we have defined several task
-categories that describe the execution boundaries. We'll setup a test
-infrastructure so that application developers can evaluate the category of their
-submissions. Conversely, worker pools will be able to benchmark their
-infrastructures against the reference machine.
+## Pay-per-task model
 
-In the future, we'll redefine the categories, and provide more advanced tools
-for helping developers to maximize the usage of the infrastructure
+We base the pay-per-task model on task size categories. Each category defines
+two limits:
+
+- Maximum Computing Time (C): per-task execution time on the worker. If the task
+  exceeds C, the worker stops the task and marks it as failed.
+- Maximum Deal Time (D): overall time window for a task in the deal. If the task
+  isn’t completed within D, the requester can claim the task. On claim, the
+  requester can recover the RLC engaged for this task.
 
 **Categories Description:**
 
 | **Category** | **Maximum Computing Time (C)** | **Maximum Deal Time (D)** |
 | ------------ | ------------------------------ | ------------------------- |
 | 0 – XS       | 5 min                          | 50 min                    |
-| 1 – S        | 20 min                         | 200 min (3h20m)           |
+| 1 – S        | 20 min                         | 200 min                   |
 | 2 – M        | 1 hour                         | 10h                       |
-| 3 – L        | 3 hour                         | 30h (1d6h)                |
-| 4 – XL       | 10 hour                        | 100h (4d4h)               |
-
-- Each worker will allocate **C** minutes to compute the application. If the
-  computation is not completed within this **Maximum Computing Time**, the
-  running application will be stopped.
-- From a buyer perspective, a requester will be able to claim a task of a deal
-  after **D** minutes if the task is not completed within the **Maximum Deal
-  Time**.
+| 3 – L        | 3 hours                        | 30h                       |
+| 4 – XL       | 10 hours                       | 100h                      |
+
+- Worker allocates up to C per task. Beyond C, the worker stops the task.
+- Requesters can claim the task after D if the task isn’t completed.
+
+## How to pick a category: quick guide
+
+Use this decision table to choose a safe category for your workload.
+
+| **Typical workload**                  | **Suggested category** |
+| ------------------------------------- | ---------------------- |
+| Short scripts / small data processing | Cat 0–1                |
+| Medium data processing / 10-15min     | Cat 2                  |
+| Heavy ML inference / long simulations | Cat 3–4                |
+
+Use the iExec SDK to **set the category** in app, request, or workerpool
+orders.  
+For commands and examples, see the
+[iExec SDK Github repository](https://github.com/iExecBlockchainComputing/iexec-sdk/blob/master/docs/README.md).