docs: align terminology (sensing/control layer) and update agent guidelines
This commit is contained in:
+7
-1
@@ -166,4 +166,10 @@ The Unified Interface Module to be implemented in future research and developmen
|
||||
### 🛡️ 4. Idempotency Assurance Schema
|
||||
- **Idempotency Classification of Physical Control Commands**: The interface module must classify control commands by their idempotency guarantees. It must explicitly distinguish between commands where idempotency is naturally guaranteed (e.g., information queries, state settings) and non-idempotent physical control commands where side effects accumulate and re-execution may lead to critical safety incidents (e.g., pesticide spraying, irrigation, valve actuation).
|
||||
- **Duplicate Dispatch Suppression Mechanism**: To prevent the same control intent from being dispatched under a new job ID during asynchronous retry loops, a deduplication schema based on a Control Intent Key must be embedded in the interface layer. Upon retry, the system must reuse the idempotency key bound to the original control intent rather than issuing a new job ID, thereby systemically controlling the possibility of duplicate execution of the same control.
|
||||
- **Pre-flight Verification at the Interface Layer**: Before a duplicate control reaches the physical device, the interface module must perform a pre-flight check that pre-blocks re-execution requests for already-executed control intents, or approves them only after cross-checking against device-side state, providing a safety net against physical double actuation.
|
||||
- **Pre-flight Verification at the Interface Layer**: Before a duplicate control reaches the physical device, the interface module must perform a pre-flight check that pre-blocks re-execution requests for already-executed control intents, or approves them only after cross-checking against device-side state, providing a safety net against physical double actuation.
|
||||
|
||||
### ✍️ 5. Terminology & Alignment Guidelines
|
||||
- **Academic Precision**: When writing or editing papers and design documents, avoid colloquial descriptions (e.g., 'value-delivering layer', 'action-triggering layer') and strictly use formal academic terminology: **'Sensing Layer'** and **'Control Layer'**.
|
||||
- **Refined Sensing Layer Definition**: The Sensing Layer must be defined not merely as a unidirectional data upload channel, but as a specific operation of "specifying sensor values such as temperature and humidity and transmitting them to the edge or cloud," describing the data flow accurately.
|
||||
- **Actionable Control Layer Definition**: The Control Layer must be defined as an active layer that issues control commands to the physical layer (e.g., "pesticide spraying") and verifies/validates the execution results.
|
||||
- **Cross-Section Terminology Alignment**: Ensure that these terms are used consistently across all sections of the document (Introduction, Background, Design, Experiments, etc.) to assist reader comprehension and prevent cognitive confusion.
|
||||
Reference in New Issue
Block a user