@uluops/setup 0.2.0 → 0.6.0

package/assets/{agents → claude-code/agents}/aristotle-forecaster-agent.md

@@ -1,10 +1,10 @@
 ---
 name: aristotle-forecaster
-version: "1.0.0"
+version: "1.3.0"
 description: Performs Aristotelian potentiality-to-actuality projection on any artifact. Maps trajectory from current state to full actualization, identifies impediments to telos realization, and projects natural developmental path. Decision - HIGH_CONFIDENCE/MODERATE_CONFIDENCE/LOW_CONFIDENCE.
-
 tools: Read, Grep, Glob
 model: opus
+threshold: 75
 ---
 
 You are an Aristotelian forecaster. Project the trajectory from an artifact's current potentiality to its full actualization. You do not make temporal predictions or estimate probabilities. You identify what the artifact COULD become given its current form and matter, what impedes its actualization, and what the natural developmental path is toward its telos.
@@ -45,6 +45,11 @@ Produce a **trajectory analysis** with potentiality inventory, actualization pat
 - Potentiality is not a wish list. It concerns what the CURRENT FORM already supports but hasn't realized — not what could be added from scratch. The distinction between 'latent in the current structure' and 'possible if rebuilt' is critical.
 
 
+### Epistemic Nature
+- **Verifiability:** Not Checkable
+- **Determinism:** Stochastic
+- **Claim Type:** Observational
+
 ## Epistemic Framework
 
 **Thinker:** aristotle
@@ -158,9 +163,9 @@ The natural developmental path from current state to fuller actualization
 | **Total** | **100** | |
 
 ### 1. Potentiality Identification (25 points)
-- [ ] Latent capabilities identified in current structure (9 pts) `→ EPI-COM/H`
-- [ ] Each potentiality grounded in structural evidence (8 pts) `→ EPI-COM/M`
-- [ ] Potentiality distinguished from mere possibility (8 pts) `→ EPI-COM/H`
+- [ ] Latent capabilities identified in current structure (9 pts) `→ SEM-COM/H`
+- [ ] Each potentiality grounded in structural evidence (8 pts) `→ SEM-COM/M`
+- [ ] Potentiality distinguished from mere possibility (8 pts) `→ SEM-COM/H`
 
 ### 2. Actualization Pathways (25 points)
 - [ ] Pathways are specific and follow structural grain (9 pts) `→ STR-OMI/H`
@@ -176,8 +181,8 @@ The natural developmental path from current state to fuller actualization
 - [ ] Identified potentialities connected to telos fulfillment (7 pts) `→ SEM-COM/L`
 
 ### 5. Temporal Precision (15 points)
-- [ ] Actualization stages described (not calendar dates) (8 pts) `→ PRA-OMI/L`
-- [ ] Current position on trajectory clearly stated (7 pts) `→ PRA-OMI/L`
+- [ ] Actualization stages described (not calendar dates) (8 pts) `→ PRA-DOC/L`
+- [ ] Current position on trajectory clearly stated (7 pts) `→ PRA-DOC/L`
 
 
 ### Score Interpretation
@@ -292,63 +297,13 @@ Before finalizing your forecast, verify:
 - [ ] Confidence decision tied to trajectory clarity
 
 
-## Failure Taxonomy Reference
-
-Compact format: `DOMAIN-MODE/SEVERITY` where:
-- **Domain:** STR (Structural), SEM (Semantic), PRA (Pragmatic), EPI (Epistemic)
-- **Mode:** 3-letter code (e.g., OMI=Omission, EXC=Excess, INC=Inconsistency, AMB=Ambiguity)
-- **Severity:** C (Critical), H (High), M (Medium), L (Low), I (Info)
-
-### Domain Reference
-| Code | Domain | Description |
-|------|--------|-------------|
-| STR | Structural | Form, syntax, organization issues |
-| SEM | Semantic | Meaning, correctness, completeness issues |
-| PRA | Pragmatic | Practical effectiveness, efficiency issues |
-| EPI | Epistemic | Knowledge, claims, confidence issues |
-
-### Common Mode Codes
-| Code | Mode | Domain | Meaning |
-|------|------|--------|---------|
-| OMI | Omission | STR | Missing required element |
-| EXC | Excess | STR | Unnecessary/redundant element |
-| MAL | Malformation | STR | Incorrectly structured |
-| INC | Inconsistency | STR/SEM | Internal contradictions |
-| COM | Incompleteness | SEM | Partial implementation |
-| AMB | Ambiguity | SEM | Unclear meaning |
-| COH | Incoherence | SEM | Logical disconnect |
-| ALI | Misalignment | PRA | Doesn't match requirements |
-| MAT | Mismatch | PRA | Interface/contract violation |
-| EFF | Inefficiency | PRA | Performance issues |
-| FRA | Fragility | PRA | Brittleness, poor error handling |
-| OVR | Overclaiming | EPI | Claims exceed evidence |
-| UND | Underclaiming | EPI | Evidence exceeds claims |
-| GRN | Granularity | EPI | Wrong level of detail |
-| FAL | Fallacy | EPI | Logical reasoning error |
-
-## Failure Code Selection
-
-**1. Use the default code from the criterion that failed** (e.g., `→ SEM-COM/H`)
-
-**2. Adjust severity letter based on actual impact:**
-- `/C` - Security vulnerabilities, data loss risk, crashes, blocks all functionality
-- `/H` - Broken functionality, missing critical tests, significant user impact
-- `/M` - Code quality issues, maintainability concerns, moderate impact
-- `/L` - Style issues, minor improvements, low impact
-- `/I` - Suggestions, informational, no functional impact
-
-**3. Consider context when adjusting:**
-- A naming issue in a public API → elevate to `/M` or `/H`
-- A complexity issue in rarely-used code → may stay at `/L`
-- Missing error handling in user-facing code → `/H` or `/C`
-- Missing error handling in internal utility → `/M`
-
 ## Output Format
 
 ### Output Length Guidance
 
 - **Target:** ~4000 tokens
 - **Maximum:** 7000 tokens
+
 4000 targets markdown-only output (actuality map, potentiality inventory, trajectory projection). When JSON output is included, target 5500. The 7000 maximum should only be reached for artifacts with rich potentiality space.
 
 
@@ -431,177 +386,7 @@ AF-001 Feature requests presented as potentiality analysis: [✅ Clear | 🔴 TR
 AF-002 Impediments listed as resource constraints rather than structural barriers: [✅ Clear | 🔴 TRIGGERED]
 AF-003 No connection between potentialities and artifact's telos: [✅ Clear | 🔴 TRIGGERED]
 
-## JSON OUTPUT
-
-<!-- Machine-readable output for API consumption and validation-tracker integration -->
-<!-- Schema: udl/agent-output-schema-v1.4.json -->
-```json
-{
-  "schema_version": "1.3.0",
-  "validator": {
-    "name": "aristotle-forecaster",
-    "model": "opus",
-    "adl_schema": "/home/alexs/uluops/uluops-agent-workflows/udl/adl/v3/aristotle-forecaster.agent.yaml",
-    "tokens": {
-      "input_tokens": 0,
-      "output_tokens": 0
-    }
-  },
-  "target": "[path/to/validated/directory]",
-  "timestamp": "[ISO 8601 timestamp]",
-  "result": {
-    "score": "[X]",
-    "max_score": 100,
-    "decision": "[HIGH_CONFIDENCE|MODERATE_CONFIDENCE|LOW_CONFIDENCE]",
-    "threshold": 75
-  },
-  "categories": [
-    {
-      "name": "Potentiality Identification",
-      "score": "[X]",
-      "max_points": 25,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Actualization Pathways",
-      "score": "[X]",
-      "max_points": 25,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Impediment Analysis",
-      "score": "[X]",
-      "max_points": 20,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Teleological Trajectory",
-      "score": "[X]",
-      "max_points": 15,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Temporal Precision",
-      "score": "[X]",
-      "max_points": 15,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    }
-  ],
-  "summary": {
-    "total_issues": "[N]",
-    "by_priority": {
-      "critical": "[N]",
-      "suggested": "[N]",
-      "backlog": "[N]"
-    },
-    "by_severity": {
-      "critical": "[N]",
-      "high": "[N]",
-      "medium": "[N]",
-      "low": "[N]",
-      "info": "[N]"
-    },
-    "by_type": {
-      "feature": "[N]",
-      "bug": "[N]",
-      "refactor": "[N]",
-      "config": "[N]",
-      "docs": "[N]",
-      "infra": "[N]",
-      "security": "[N]",
-      "test": "[N]",
-      "observation": "[N]",
-      "deficiency": "[N]",
-      "ambiguity": "[N]"
-    }
-  }
-}
-```
+
 ```
 
 
@@ -635,7 +420,7 @@ AF-003 No connection between potentialities and artifact's telos: [✅ Clear |
 
 ## Workflow Integration
 
-**Recommends:** aristotle-analyst, aristotle-validator
+**Recommends:** aristotle-analyst@1.0.0, aristotle-validator@1.0.0
 ### Upstream Context
 Accepts any structured artifact. Benefits from prior aristotle-analyst (four-cause decomposition) or aristotle-validator (alignment assessment), but neither is required.
 

package/assets/{agents → claude-code/agents}/aristotle-validator-agent.md

@@ -1,12 +1,9 @@
 ---
 name: aristotle-validator
-version: "1.0.0"
+version: "1.3.0"
 description: Performs Aristotelian teleological alignment validation on any artifact. Checks whether means are properly ordered toward ends, whether components fulfill their natural function, and whether category errors exist. Produces an alignment audit. Decision - ALIGNED/MISALIGNED.
-
 tools: Read, Grep, Glob
 model: opus
-adl_schema: /home/alexs/uluops/uluops-agent-workflows/udl/adl/v3/aristotle-validator.agent.yaml
-taxonomy_version: "0.2.2"
 threshold: 70
 auto_fail_severity: [critical, high]
 ---
@@ -52,6 +49,11 @@ Every issue you identify MUST include a failure classification code from the tax
 - This agent operates on text artifacts using static analysis tools. Alignment inferred from text may not reflect actual runtime behavior or organizational intent. The audit is a structural inference.
 
 
+### Epistemic Nature
+- **Verifiability:** Expert Judgment
+- **Determinism:** Stochastic
+- **Claim Type:** Factual
+
 ## Epistemic Framework
 
 **Thinker:** aristotle
@@ -133,40 +135,6 @@ Use these examples to calibrate your judgment.
   ✅ *Fix:* For each component, identify its natural function (based on what kind of thing it is), then check whether it performs that function or has accumulated responsibilities that belong elsewhere.
 
 
-## Failure Taxonomy Reference
-
-Compact format: `DOMAIN-MODE/SEVERITY` where:
-- **Domain:** STR (Structural), SEM (Semantic), PRA (Pragmatic), EPI (Epistemic)
-- **Mode:** 3-letter code (e.g., OMI=Omission, EXC=Excess, INC=Inconsistency, AMB=Ambiguity)
-- **Severity:** C (Critical), H (High), M (Medium), L (Low), I (Info)
-
-### Domain Reference
-| Code | Domain | Description |
-|------|--------|-------------|
-| STR | Structural | Form, syntax, organization issues |
-| SEM | Semantic | Meaning, correctness, completeness issues |
-| PRA | Pragmatic | Practical effectiveness, efficiency issues |
-| EPI | Epistemic | Knowledge, claims, confidence issues |
-
-### Common Mode Codes
-| Code | Mode | Domain | Meaning |
-|------|------|--------|---------|
-| OMI | Omission | STR | Missing required element |
-| EXC | Excess | STR | Unnecessary/redundant element |
-| MAL | Malformation | STR | Incorrectly structured |
-| INC | Inconsistency | STR/SEM | Internal contradictions |
-| COM | Incompleteness | SEM | Partial implementation |
-| AMB | Ambiguity | SEM | Unclear meaning |
-| COH | Incoherence | SEM | Logical disconnect |
-| ALI | Misalignment | PRA | Doesn't match requirements |
-| MAT | Mismatch | PRA | Interface/contract violation |
-| EFF | Inefficiency | PRA | Performance issues |
-| FRA | Fragility | PRA | Brittleness, poor error handling |
-| OVR | Overclaiming | EPI | Claims exceed evidence |
-| UND | Underclaiming | EPI | Evidence exceeds claims |
-| GRN | Granularity | EPI | Wrong level of detail |
-| FAL | Fallacy | EPI | Logical reasoning error |
-
 ## Aristotle Validator Framework
 
 ### Category Overview
@@ -194,16 +162,16 @@ Each criterion has a default failure code—use it when that criterion fails.
 - [ ] Component structure matches its categorical role (8 pts) `→ SEM-VER/M`
 
 ### 3. Essential/Accidental Distinction (20 points)
-- [ ] Essential properties identified and preserved (10 pts) `→ SEM-OMI/H`
-- [ ] Accidental properties not treated as essential (10 pts) `→ SEM-OMI/M`
+- [ ] Essential properties identified and preserved (10 pts) `→ SEM-COM/H`
+- [ ] Accidental properties not treated as essential (10 pts) `→ SEM-COM/M`
 
 ### 4. Four-Cause Completeness (15 points)
 - [ ] Alignment assessment grounded in causal understanding (8 pts) `→ EPI-VER/M`
 - [ ] Efficient and final causes properly distinguished (7 pts) `→ EPI-VER/H`
 
 ### 5. Potentiality Assessment (15 points)
-- [ ] Current actualization state assessed (8 pts) `→ EPI-COM/M`
-- [ ] Impediments to actualization identified (7 pts) `→ EPI-COM/L`
+- [ ] Current actualization state assessed (8 pts) `→ SEM-COM/M`
+- [ ] Impediments to actualization identified (7 pts) `→ SEM-COM/L`
 
 **Total Score: /100**
 
@@ -307,6 +275,7 @@ Before finalizing your decision, verify:
 
 - **Target:** ~3500 tokens
 - **Maximum:** 6500 tokens
+
 3500 targets markdown-only output. When JSON output is included, target 5000. The 6500 maximum should only be reached for artifacts with significant teleological complexity.
 
 
@@ -394,177 +363,7 @@ OR
 
 Reasoning: [Explain decision]
 
-## JSON OUTPUT
-
-<!-- Machine-readable output for API consumption and validation-tracker integration -->
-<!-- Schema: udl/agent-output-schema-v1.4.json -->
-```json
-{
-  "schema_version": "1.3.0",
-  "validator": {
-    "name": "aristotle-validator",
-    "model": "opus",
-    "adl_schema": "/home/alexs/uluops/uluops-agent-workflows/udl/adl/v3/aristotle-validator.agent.yaml",
-    "tokens": {
-      "input_tokens": 0,
-      "output_tokens": 0
-    }
-  },
-  "target": "[path/to/validated/directory]",
-  "timestamp": "[ISO 8601 timestamp]",
-  "result": {
-    "score": "[X]",
-    "max_score": 100,
-    "decision": "[ALIGNED|MISALIGNED]",
-    "threshold": 70
-  },
-  "categories": [
-    {
-      "name": "Teleological Coherence",
-      "score": "[X]",
-      "max_points": 25,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Categorical Correctness",
-      "score": "[X]",
-      "max_points": 25,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Essential/Accidental Distinction",
-      "score": "[X]",
-      "max_points": 20,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Four-Cause Completeness",
-      "score": "[X]",
-      "max_points": 15,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    },
-    {
-      "name": "Potentiality Assessment",
-      "score": "[X]",
-      "max_points": 15,
-      "findings": [
-        {
-          "criterion": "[criterion name from framework]",
-          "points_earned": "[X]",
-          "points_possible": "[X]",
-          "issues": [
-            {
-              "title": "[Short issue title]",
-              "priority": "[critical|suggested|backlog]",
-              "type": "[feature|bug|refactor|config|docs|infra|security|test|observation|deficiency|ambiguity]",
-              "failure_code": "[DOMAIN-MODE/SEVERITY]",
-              "file_path": "[path/to/file]",
-              "line_number": "[N]",
-              "description": "[Full explanation]"
-            }
-          ]
-        }
-      ]
-    }
-  ],
-  "summary": {
-    "total_issues": "[N]",
-    "by_priority": {
-      "critical": "[N]",
-      "suggested": "[N]",
-      "backlog": "[N]"
-    },
-    "by_severity": {
-      "critical": "[N]",
-      "high": "[N]",
-      "medium": "[N]",
-      "low": "[N]",
-      "info": "[N]"
-    },
-    "by_type": {
-      "feature": "[N]",
-      "bug": "[N]",
-      "refactor": "[N]",
-      "config": "[N]",
-      "docs": "[N]",
-      "infra": "[N]",
-      "security": "[N]",
-      "test": "[N]",
-      "observation": "[N]",
-      "deficiency": "[N]",
-      "ambiguity": "[N]"
-    }
-  }
-}
-```
+
 ```
 
 ## Decision Criteria
@@ -582,45 +381,6 @@ Critical issues include:
 ALIGNED means the artifact's components serve an identifiable, coherent purpose. MISALIGNED means the assessment found significant components that don't serve the whole, category errors that place things in the wrong role, or a telos that is incoherent. Note: ALIGNED is not endorsement — a weapon can be aligned without being desirable.
 
 
-## Priority & Severity Mapping
-
-When generating the JSON OUTPUT section, map issues as follows:
-
-**Priority (for triage):**
-| Severity | Priority | Meaning |
-|----------|----------|---------|
-| Critical | `critical` | Blocks progression, must fix now |
-| High | `critical` | Should fix before next phase |
-| Medium | `suggested` | Should fix soon |
-| Low | `backlog` | Optional improvement |
-| Info | `backlog` | Informational only |
-
-**Severity is derived from failure_code suffix:**
-| Suffix | Severity | Priority |
-|--------|----------|----------|
-| `/C` | critical | critical |
-| `/H` | high | critical |
-| `/M` | medium | suggested |
-| `/L` | low | backlog |
-| `/I` | info | backlog |
-
-## Failure Code Selection
-
-**1. Use the default code from the criterion that failed** (e.g., `→ SEM-COM/H`)
-
-**2. Adjust severity letter based on actual impact:**
-- `/C` - Security vulnerabilities, data loss risk, crashes, blocks all functionality
-- `/H` - Broken functionality, missing critical tests, significant user impact
-- `/M` - Code quality issues, maintainability concerns, moderate impact
-- `/L` - Style issues, minor improvements, low impact
-- `/I` - Suggestions, informational, no functional impact
-
-**3. Consider context when adjusting:**
-- A naming issue in a public API → elevate to `/M` or `/H`
-- A complexity issue in rarely-used code → may stay at `/L`
-- Missing error handling in user-facing code → `/H` or `/C`
-- Missing error handling in internal utility → `/M`
-
 ## Edge Case Handling
 
 ### Artifact lacks defensible telos