update

docs/architecture.md

@@ -317,7 +317,6 @@ flowchart TB
 | **JSON Serialization** | ✅ (JSON.jl) | ✅ (native) | ✅ (json) | ✅ (json) |
 | **arrowtable Support** | ✅ | ✅ | ✅ | ❌ |
 | **jsontable Support** | ✅ | ✅ | ✅ | ❌ |
-| **table Support** | ❌ | ❌ | ✅ | ❌ |
 | **Direct Transport** | ✅ | ✅ | ✅ | ✅ |
 | **Link Transport** | ✅ | ✅ | ✅ | ⚠️ (Limited) |
 | **Handler Functions** | ✅ | ✅ | ✅ | ✅ |
@@ -363,18 +362,17 @@ MicroPython has significant constraints:
 
 ## Cross-Platform Compatibility Notes
 
-### 1. Python Payload Type Naming
+### 1. Payload Type Consistency
 
-The Python implementation uses `"table"` as a single payload type for both Arrow and JSON table serialization, while Julia and JavaScript use separate types (`"arrowtable"` and `"jsontable"`):
+All platforms use the same payload type values for tabular data:
 
 | Platform | Table Types |
 |----------|-------------|
 | Julia | `"arrowtable"`, `"jsontable"` |
 | JavaScript | `"arrowtable"`, `"jsontable"` |
-| Python | `"table"` (single type) |
+| Python | `"arrowtable"`, `"jsontable"` |
 | MicroPython | Not supported |
 
-**Impact:** When exchanging data between Python and Julia/JavaScript, the payload type will differ. Python code should use `"table"` while Julia/JavaScript code should use `"arrowtable"` or `"jsontable"`.
 
 ### 2. Direct Transport Encoding Field