interaqt 0.3.0 → 0.4.0

package/agent/.claude/agents/code-generation-handler.md

@@ -279,6 +279,8 @@ This task has its own dedicated sub-agent that handles the progressive implement
 
 **🛑 STOP GATE: DO NOT proceed to Task 3.1.4.4 until ALL computations in `docs/computation-implementation-plan.json` are marked as complete with passing tests.**
 
+** CRETICA:L use the specialized sub-agent `computation-generation-handler` until ALL computations in `docs/computation-implementation-plan.json` are marked as complete with passing tests.**
+
 **✅ END Task 3.1.4.3: Update `docs/STATUS.json`:**
 ```json
 {

package/agent/.claude/agents/computation-generation-handler.md

@@ -59,6 +59,7 @@ color: blue
        - You should modify the PARENT entity's computation, not the current entity
        - Example: For `_parent:[User]`, modify the `User` entity's computation that creates Posts
        - This typically occurs when a child entity needs to be created by a parent's Transform computation
+       - **📍 Finding the parent entity**: You can find the parent entity name in the current item's `lifecycle.creation.parent` field
        - **How to create child entities**: Use the relation's source/target property name in the parent's Transform return value
        - Example: If `OrderItemRelation` has `sourceProperty: 'items'`, then in Order's Transform:
          ```typescript
@@ -79,9 +80,7 @@ color: blue
    - **🔴 SPECIAL CASE 2: `_owner` notation**
      - If the computation decision is `_owner`, this means:
        - The property's value is fully controlled by its owner entity/relation's computation
-       - You should modify the OWNER entity/relation's creation or derivation logic, not add a separate property computation
-       - For `controlType: "creation-only"`: Add the property assignment logic in the entity/relation's creation Transform or StateMachine
-       - For `controlType: "derived-with-parent"`: The property is part of the parent's derivation computation
+       - You should modify the OWNER entity/relation's creation or derivation logic, not add a separate property computation. Add the property assignment logic in the entity/relation's creation Transform
        - Example: For a `createdAt` property with `_owner`, add timestamp assignment in the entity's Transform that creates it
    - Add computation code using assignment pattern at end of file:
      ```typescript

package/agent/.claude/agents/implement-design-handler.md

@@ -37,20 +37,11 @@ You are a honest software expert with the following capabilities:
 }
 ```
 
-**🔴 CRITICAL FOUNDATION:**
-**📖 MUST READ FIRST: `requirements/detailed-requirements.json`**
-- **Read the COMPLETE detailed requirements document thoroughly before starting data analysis**
-- **This document is the ROOT SOURCE for all data analysis**
-- **ALL data entities, properties, and relationships mentioned in the detailed requirements MUST be analyzed**
-- **No data element from the requirements should be overlooked**
-
 
 **Process:**
-1. **FIRST**: Thoroughly read `requirements/detailed-requirements.json` to understand ALL data requirements
-2. **EXTRACT**: Identify every entity, property, and relationship mentioned in the requirements
-3. **ANALYZE**: Follow the systematic approach in `data-analysis.md` for each identified data element
-4. **DOCUMENT**: Use the Analysis Documentation Template from `data-analysis.md` to create your `docs/data-design.json`
-5. **VERIFY**: Cross-check that ALL data from the detailed requirements has been included in your analysis
+1. **ANALYZE**: Follow the systematic approach in `agentspace/knowledge/generator/data-analysis.md` for each identified data element
+2. **DOCUMENT**: Use the Analysis Documentation Template from `agentspace/knowledge/generator/data-analysis.md` to create your `docs/data-design.json`
+3. **VERIFY**: Cross-check that ALL data from the detailed requirements has been included in your analysis
 
 **✅ END Task 2.1: Update `docs/STATUS.json`:**
 ```json
@@ -150,7 +141,7 @@ You are a honest software expert with the following capabilities:
    - `docs/interaction-design.md` (from Task 2.2)
 3. **ANALYZE**: For EVERY entity and EVERY property, follow the step-by-step analysis process
 4. **DOCUMENT**: Create `docs/computation-analysis.json` documenting your analysis for each entity/property
-5. **REFERENCE**: Use `computation-implementation.md` as a reference for syntax and examples
+5. **REFERENCE**: Use `./agentspace/knowledge/generator/computation-implementation.md` as a reference for syntax and examples
 
 **Key Steps from computation-analysis.md:**
 - [ ] Create analysis document at `docs/computation-analysis.json`

package/agent/.claude/agents/requirements-analysis-handler.md

@@ -72,6 +72,11 @@ Constraints expressed on roles, interactions, and data in requirements.
 
 ### Analyze User Input
 
+**🌐 Language Processing:**
+- Translate user input to English if provided in other languages
+- Use English consistently throughout all subsequent analysis and outputs
+- Preserve original meaning and context during translation
+
 User input may contain:
 - Vague or incomplete goals
 - Specific requirements mixed with goals
@@ -169,6 +174,39 @@ git commit -m "feat: Task 1.1 - Complete goal analysis and refinement"
 
 We focus on data-centric requirements. Human software usage delegates unsuitable tasks (storage, computation) to support better decision-making. Since decisions require information, we start with **READ requirements** as the root.
 
+### ⚠️ CRITICAL: Reactive Framework Principles
+
+**DO NOT create "automatic system" requirements.** Our framework is reactive - avoid designing autonomous system behaviors.
+
+**Transform "non-data-reactive" requirements into:**
+
+1. **Reactive Data Requirements**: 
+   - ❌ WRONG: "System automatically counts total books"
+   - ✅ CORRECT: "There is a `totalBookCount` data that represents the statistical result of total books"
+
+2. **Interaction Constraint Conditions**:
+   - ❌ WRONG: "System automatically detects uniqueness"  
+   - ✅ CORRECT: "Can only create unique XXX" (as constraint condition)
+
+3. **Data Constraints on Write Operations**:
+   - ❌ WRONG: "System automatically creates uniform record when employee is created"
+   - ✅ CORRECT: "When creating employee, automatically create uniform record" (as data constraint)
+
+4. **Data Replacement Operations**:
+   - ❌ WRONG: "Replace old data with new data"
+   - ✅ CORRECT: "Create new data + Delete old data" (as two separate operations)
+
+**For unavoidable side-effect requirements** (e.g., "automatically send notification"):
+- Design the requirement but explicitly mark as **"Currently Not Supported"**
+- Document: "This requirement involves automatic side-effects which are not supported by the current reactive framework"
+
+**Examples of Proper Transformation:**
+- "Auto-calculate late fees" → "Late fee amount is computed based on overdue days and daily rate"
+- "Auto-send reminders" → "Reminder needed status is computed based on due date" + "Send reminder interaction"
+- "Auto-validate ISBN" → "Can only create books with valid ISBN format" (constraint)
+- "Auto-update inventory" → "Available count is computed based on total copies minus borrowed copies"
+- "Replace employee profile" → "Create new employee profile" + "Delete old employee profile" (two interactions)
+
 ### Step 1: Create Read Requirements from Goals
 
 Read requirements express:
@@ -255,6 +293,20 @@ Create `requirements/requirements-analysis.json`:
         },
         "business_constraints": ["[Business rule 1]"],
         "data_constraints": ["[Data constraint 1]"]
+      },
+      {
+        "id": "R103",
+        "type": "delete",
+        "title": "[Requirement name]",
+        "parent": "R001",
+        "role": "[Role]",
+        "data": {
+          "type": "entity|relation",
+          "description": "[Data to delete]"
+        },
+        "deletion_type": "hard",
+        "deletion_rules": ["[Rule 1: e.g., Cannot delete if has active references]", "[Rule 2]"],
+        "business_constraints": ["[Business rule 1]"]
       }
     ],
     "from_R101": [
@@ -334,6 +386,11 @@ For each entity property:
 - **Computation Method**: For aggregated or computed values
 - **Data Dependencies**: For computed values, list dependencies
 
+**Hard Deletion Property**:
+- If delete requirements in Task 1.2 specify `"deletion_type": "hard"`
+- Add **HardDeletionProperty** to the entity/relation
+- Document deletion rules from requirements as property metadata
+
 ### Step 3: Relation Identification and Analysis
 
 **Relations are the ONLY way to connect entities** - they replace traditional foreign key patterns.
@@ -426,9 +483,17 @@ Create `requirements/data-concepts.json`:
             "description": "Total copies minus borrowed copies",
             "dependencies": ["BookCopy", "BorrowRecord"]
           }
+        },
+        {
+          "name": "_hardDeletion",
+          "type": "HardDeletionProperty",
+          "required": false,
+          "computed": false,
+          "deletion_rules": ["Cannot delete if has active borrow records", "Only administrators can delete"],
+          "source_requirement": "R103"
         }
       ],
-      "referenced_in": ["R001", "R101", "R201"],
+      "referenced_in": ["R001", "R101", "R103", "R201"],
       "note": "No authorId or publisherId - use BookAuthorRelation and BookPublisherRelation instead"
     },
     {
@@ -481,9 +546,17 @@ Create `requirements/data-concepts.json`:
           "name": "dueDate",
           "type": "date",
           "required": true
+        },
+        {
+          "name": "_hardDeletion",
+          "type": "HardDeletionProperty",
+          "required": false,
+          "computed": false,
+          "deletion_rules": ["Auto-delete when book is returned"],
+          "source_requirement": "R103"
         }
       ],
-      "lifecycle": "Created on borrow, updated on return",
+      "lifecycle": "Created on borrow, updated on return, deleted on return or book deletion",
       "referenced_in": ["R102", "R103"]
     },
     {
@@ -541,6 +614,7 @@ git commit -m "feat: Task 1.3 - Complete data concept extraction"
 - Interactions fulfill requirements
 - All data in interactions must reference concepts from Task 1.3
 - **CRITICAL**: Inherit all data constraints from requirements
+- **Interaction IDs must be semantic names** (e.g., "BorrowBook", "ViewAvailableBooks") not generic codes (e.g., "I001", "I002")
 
 ### Interaction Specification Format
 
@@ -569,8 +643,7 @@ Create `requirements/interactions-design.json`:
   },
   "interactions": [
     {
-      "id": "I001",
-      "name": "BorrowBook",
+      "id": "BorrowBook",
       "fulfills_requirements": ["R101"],
       "type": "create",
       "specification": {
@@ -611,8 +684,7 @@ Create `requirements/interactions-design.json`:
       ]
     },
     {
-      "id": "I002",
-      "name": "ViewAvailableBooks",
+      "id": "ViewAvailableBooks",
       "fulfills_requirements": ["R001"],
       "type": "read",
       "specification": {
@@ -650,20 +722,20 @@ Create `requirements/interactions-design.json`:
   ],
   "interaction_matrix": {
     "by_requirement": {
-      "R001": ["I002"],
-      "R101": ["I001"],
-      "R102": ["I003"],
-      "R201": ["I004"]
+      "R001": ["ViewAvailableBooks"],
+      "R101": ["BorrowBook"],
+      "R102": ["ReturnBook"],
+      "R201": ["ValidateReaderStatus"]
     },
     "by_role": {
-      "Reader": ["I001", "I002"],
-      "Librarian": ["I003", "I004", "I005"],
-      "Administrator": ["I006", "I007"]
+      "Reader": ["BorrowBook", "ViewAvailableBooks"],
+      "Librarian": ["ReturnBook", "ValidateReaderStatus", "ManageBookInventory"],
+      "Administrator": ["CreateBook", "ManageReaderAccounts"]
     },
     "by_data_entity": {
-      "Book": ["I001", "I002", "I003"],
-      "Reader": ["I001", "I004"],
-      "BorrowRecord": ["I001", "I003", "I005"]
+      "Book": ["BorrowBook", "ViewAvailableBooks", "CreateBook"],
+      "Reader": ["BorrowBook", "ValidateReaderStatus"],
+      "BorrowRecord": ["BorrowBook", "ReturnBook", "ManageBookInventory"]
     }
   },
   "coverage_analysis": {