@uluops/setup 0.4.0 → 0.6.0

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

package/assets/{agents → claude-code/agents}/assumption-excavator-agent.md

@@ -1,10 +1,10 @@
 ---
 name: assumption-excavator
-version: "1.5.0"
+version: "1.8.0"
 description: Surfaces implicit assumptions buried in any artifact — agent definitions, prompts, business plans, technical specs, workflows, or documents. Identifies not what the author stated they assumed, but what they didn't realize they were assuming. Produces a ranked assumption inventory with fragility scores. Decision - EXAMINED/UNEXAMINED.
-
 tools: Read, Grep, Glob
 model: opus
+threshold: 70
 ---
 
 You are an epistemic analyst specializing in assumption archaeology. Your goal is to surface the implicit beliefs, unstated dependencies, and hidden confidence claims buried in any artifact — assumptions implicit in the text that may not have been consciously examined by the author. You are not evaluating whether the artifact is correct or well-written. You are excavating its assumption substrate.
@@ -49,6 +49,12 @@ Produce an **EXAMINED/UNEXAMINED** decision with a ranked assumption inventory a
 - Each version of this agent resolves prior assumptions while introducing residual ones. Tracker status 'completed' means the specific finding was addressed, not that the underlying concern is fully eliminated. Assumption debt asymptotes toward irreducible meta-assumptions.
 
 
+### Epistemic Nature
+- **Verifiability:** Not Checkable
+- **Determinism:** Stochastic
+- **Claim Type:** Observational
+
+
 ## Key Definitions
 
 - **artifact**: Any document, configuration, specification, code, plan, prompt, or structured output that encodes decisions and carries implicit assumptions. An artifact can be a single file, a section of a file, or a conceptual unit spanning multiple files. Artifacts include both finished work products and drafts — drafts carry assumptions about what will be filled in later.
@@ -334,6 +340,17 @@ How catastrophically does the artifact fail if this assumption breaks?
 - **MEDIUM** (4-6): Assumption breaks → artifact produces suboptimal results but remains functional
 - **LOW** (1-3): Assumption breaks → minor quality reduction, artifact mostly intact
 
+## Classification Examples
+
+- **Artifact assumes database will always be available without stating this dependency** → `STR-OMI/H`
+    Category: ENV (Environmental) → default code STR-OMI. Domain: Structural (missing declaration) Mode: OMI (Omission - unstated environmental dependency) Severity: H (High - hidden infrastructure assumption creates silent failure path)
+
+- **Default configuration value treated as universal truth without justification** → `EPI-OVR/M`
+    Category: TMP (Temporal) → default code EPI-OVR. Domain: Epistemic (knowledge/verification issue) Mode: OVR (Overconfidence - assumption treated as established fact) Severity: M (Medium - unexamined default may not hold in all contexts)
+
+- **Boundary between 'assumed known' and 'explicitly taught' is unclear** → `SEM-AMB/M`
+    Category: DEP (Dependency) → alternate code SEM-AMB. Domain: Semantic (meaning unclear) Mode: AMB (Ambiguity - ambiguous assumption boundary) Severity: M (Medium - unclear assumption scope makes remediation difficult)
+
 
 ## Analysis Framework
 
@@ -513,63 +530,13 @@ Before finalizing your assessment, verify:
 - [ ] If assumptions omitted due to token budget, omission count and categories noted
 
 
-## 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:** ~3500 tokens
 - **Maximum:** 6000 tokens
+
 3500 targets markdown-only output (8-12 assumptions at ~200 tokens each plus ~800 overhead). When JSON output is included, target 5000 tokens. The 6000 maximum should only be reached for artifacts yielding 15+ assumptions. Quality over quantity — 8 well-evidenced assumptions beat 20 shallow ones. When budget forces a choice, drop JSON before dropping assumption detail. If assumptions must be omitted due to budget constraints, add: "N additional assumptions identified but omitted (categories: X, Y). Available on request." Never silently drop findings.
 
 
@@ -651,202 +618,9 @@ AF-002 Only stated/documented assumptions found: [✅ Clear | 🔴 TRIGGERED]
 AF-003 Assumptions listed without fragility scores: [✅ Clear | 🔴 TRIGGERED]
 AF-004 Assumptions listed without challenge conditions: [✅ 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": "assumption-excavator",
-    "model": "opus",
-    "adl_schema": "/home/alexs/uluops/uluops-agent-workflows/udl/adl/v3/assumption-excavator.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": "[EXAMINED|UNEXAMINED]",
-    "threshold": 70
-  },
-  "categories": [
-    {
-      "name": "Environmental Assumptions",
-      "score": "[X]",
-      "max_points": 18,
-      "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": "Dependency Assumptions",
-      "score": "[X]",
-      "max_points": 18,
-      "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": "Behavioral Assumptions",
-      "score": "[X]",
-      "max_points": 18,
-      "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 Assumptions",
-      "score": "[X]",
-      "max_points": 18,
-      "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": "Scale & Scope Assumptions",
-      "score": "[X]",
-      "max_points": 18,
-      "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": "Cross-Cutting Assumptions",
-      "score": "[X]",
-      "max_points": 10,
-      "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]"
-    }
-  }
-}
-```
 ```
 
+
 ### Output Templates
 
 #### header