@vfarcic/dot-ai 0.28.0 → 0.29.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vfarcic/dot-ai",
3
- "version": "0.28.0",
3
+ "version": "0.29.0",
4
4
  "description": "Universal Kubernetes application deployment agent with CLI and MCP interfaces",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -15,22 +15,13 @@ Analyze the user's intent and determine the best solution(s). This could be:
15
15
  - A combination of resources that can actually integrate and work together to create a complete solution
16
16
  - Multiple alternative approaches ranked by effectiveness
17
17
 
18
- ## MANDATORY Validation Process
18
+ ## Validation Requirements
19
19
 
20
- **STEP 1: Extract Intent Requirements**
21
- Parse the user intent and identify ALL requirements (e.g., "stateful application" + "persistent storage" + "accessible through Ingress").
20
+ **Capability Verification**: For each resource in your solution, examine its schema fields to verify it can fulfill the user's requirements. Do not assume capabilities that aren't explicitly present in the schema fields.
22
21
 
23
- **STEP 2: Schema Analysis for Each Resource**
24
- For each resource in your solution, examine its schema fields to verify it can fulfill the requirements:
25
- - **Direct field matching**: Look for schema fields whose names directly relate to the requirements
26
- - **Integration capability**: Check if the resource has fields to integrate with other needed resources
27
- - **Reject false matches**: Do not assume capabilities that aren't explicitly present in the schema fields
22
+ **Complete Solutions**: Include ALL resource types needed for the solution to work. If your analysis mentions integration with other resources, include those resources in your resources array.
28
23
 
29
- **STEP 3: Solution Completeness Check**
30
- Verify your solution addresses ALL requirements from Step 1. Incomplete solutions must score lower.
31
-
32
- **STEP 4: Combination Validation**
33
- For multi-resource solutions, verify integration compatibility by checking that resources have schema fields to reference each other.
24
+ **Integration Validation**: For multi-resource solutions, verify that resources have schema fields to reference each other.
34
25
 
35
26
  ## Scoring Guidelines
36
27