|
| 1 | +# Automation System Configuration |
| 2 | +# Version: 1.0.0 |
| 3 | +# Last Updated: 2025-11-14 |
| 4 | +# Purpose: Production-ready configuration file for the automation system |
| 5 | + |
| 6 | +# ============================================================================== |
| 7 | +# METADATA |
| 8 | +# ============================================================================== |
| 9 | +metadata: |
| 10 | + version: 1.0.0 |
| 11 | + last_updated: 2025-11-14 |
| 12 | + description: Automation system configuration |
| 13 | + |
| 14 | +# ============================================================================== |
| 15 | +# PRINCIPLES (5 Core Principles) |
| 16 | +# ============================================================================== |
| 17 | +principles: |
| 18 | + R1: |
| 19 | + name: Idempotencia |
| 20 | + description: All operations must be idempotent |
| 21 | + enforcement: Operations can be executed multiple times with same result |
| 22 | + |
| 23 | + R2: |
| 24 | + name: Sin Emojis |
| 25 | + description: No emojis or icons in outputs |
| 26 | + enforcement: All output must be text-only for automation compatibility |
| 27 | + |
| 28 | + R3: |
| 29 | + name: Verificacion |
| 30 | + description: All changes must be verified |
| 31 | + enforcement: Verification step required after each operation |
| 32 | + |
| 33 | + R4: |
| 34 | + name: Documentacion |
| 35 | + description: All changes must be documented |
| 36 | + enforcement: Documentation update required for all modifications |
| 37 | + |
| 38 | + R5: |
| 39 | + name: Trazabilidad |
| 40 | + description: Complete traceability of changes |
| 41 | + enforcement: All changes must be logged with context and metadata |
| 42 | + |
| 43 | +# ============================================================================== |
| 44 | +# RULES (6 Operational Rules) |
| 45 | +# ============================================================================== |
| 46 | +rules: |
| 47 | + rule_1: |
| 48 | + name: Exit Codes |
| 49 | + description: Standardized exit codes for all operations |
| 50 | + implementation: |
| 51 | + success: 0 |
| 52 | + failure: 1 |
| 53 | + warnings: 2 |
| 54 | + |
| 55 | + rule_2: |
| 56 | + name: JSON Output Format |
| 57 | + description: Agent results must use JSON format |
| 58 | + implementation: All agent outputs structured as valid JSON |
| 59 | + |
| 60 | + rule_3: |
| 61 | + name: Logging Standards |
| 62 | + description: Logging to STDERR, results to STDOUT |
| 63 | + implementation: |
| 64 | + logs: STDERR |
| 65 | + results: STDOUT |
| 66 | + |
| 67 | + rule_4: |
| 68 | + name: Configuration Validation |
| 69 | + description: Configuration validation before execution |
| 70 | + implementation: Validate all config files before running operations |
| 71 | + |
| 72 | + rule_5: |
| 73 | + name: Graceful Degradation |
| 74 | + description: Graceful degradation on errors |
| 75 | + implementation: Continue execution with reduced functionality on non-critical errors |
| 76 | + |
| 77 | + rule_6: |
| 78 | + name: Parallel Execution |
| 79 | + description: Parallel execution where possible |
| 80 | + implementation: Maximize parallelization for independent operations |
| 81 | + |
| 82 | +# ============================================================================== |
| 83 | +# AGENT CONFIGURATION (8 Real Automation Agents) |
| 84 | +# ============================================================================== |
| 85 | +agent_configuration: |
| 86 | + schema_validator_agent: |
| 87 | + schemas_dir: schemas/ |
| 88 | + validation_mode: strict |
| 89 | + output_format: json |
| 90 | + fail_on_warnings: false |
| 91 | + |
| 92 | + devcontainer_validator_agent: |
| 93 | + devcontainer_config: .devcontainer/devcontainer.json |
| 94 | + check_extensions: true |
| 95 | + check_features: true |
| 96 | + output_format: json |
| 97 | + |
| 98 | + metrics_collector_agent: |
| 99 | + metrics_output: /tmp/automation_metrics.json |
| 100 | + track_execution_time: true |
| 101 | + track_success_rate: true |
| 102 | + retention_days: 30 |
| 103 | + |
| 104 | + coherence_analyzer_agent: |
| 105 | + ui_path: frontend/src/components |
| 106 | + api_path: api/callcentersite |
| 107 | + analysis_depth: full |
| 108 | + report_mismatches: true |
| 109 | + output_format: json |
| 110 | + |
| 111 | + constitution_validator_agent: |
| 112 | + rules_to_check: |
| 113 | + - R1 # Branch protection |
| 114 | + - R2 # No emojis |
| 115 | + - R3 # UI/API coherence |
| 116 | + - R4 # Database router |
| 117 | + - R5 # Test execution |
| 118 | + - R6 # DevContainer validation |
| 119 | + enforcement_mode: strict |
| 120 | + |
| 121 | + ci_pipeline_orchestrator_agent: |
| 122 | + config_file: .ci-local.yaml |
| 123 | + max_concurrent_jobs: 10 |
| 124 | + fail_fast: true |
| 125 | + smart_detection: true |
| 126 | + |
| 127 | + pdca_agent: |
| 128 | + dora_metrics_enabled: true |
| 129 | + pdca_cycle_tracking: true |
| 130 | + improvement_suggestions: true |
| 131 | + output_format: json |
| 132 | + |
| 133 | + business_rules_validator_agent: |
| 134 | + docs_dir: docs/gobernanza/requisitos/REGLAS_NEGOCIO |
| 135 | + check_structure: true |
| 136 | + check_categorization: true |
| 137 | + check_examples: true |
| 138 | + check_references: true |
| 139 | + check_matrices: true |
| 140 | + output_format: json |
| 141 | + |
| 142 | + compliance_validator_agent: |
| 143 | + spec_file: docs/gobernanza/requisitos/REGLAS_NEGOCIO/ESPECIFICACION_TESTS_COMPLIANCE.md |
| 144 | + check_coverage: true |
| 145 | + check_structure: true |
| 146 | + check_naming: true |
| 147 | + check_levels: true |
| 148 | + output_format: json |
| 149 | + |
| 150 | +# ============================================================================== |
| 151 | +# METRICS CONFIGURATION |
| 152 | +# ============================================================================== |
| 153 | +metrics_configuration: |
| 154 | + enable_metrics: true |
| 155 | + metrics_output: /tmp/automation_metrics.json |
| 156 | + track_execution_time: true |
| 157 | + track_success_rate: true |
| 158 | + |
| 159 | +# ============================================================================== |
| 160 | +# EVOLUTION GUIDELINES |
| 161 | +# ============================================================================== |
| 162 | +evolution_guidelines: |
| 163 | + schema_versioning: |
| 164 | + description: Use semantic versioning for schema changes |
| 165 | + breaking_changes: Increment major version for breaking changes |
| 166 | + backward_compatibility: Maintain compatibility within major versions |
| 167 | + |
| 168 | + backward_compatibility: |
| 169 | + description: Requirements for backward compatibility |
| 170 | + policy: New minor versions must support previous minor version configurations |
| 171 | + deprecation_notice: Provide at least one minor version deprecation notice |
| 172 | + |
| 173 | + migration_path: |
| 174 | + description: Migration path documentation requirements |
| 175 | + requirement: All breaking changes must include migration documentation |
| 176 | + location: Document migration steps in CHANGELOG.md and migration guides |
0 commit comments