1 agents

pattern-quality-analyst

pattern-quality-analyst

Overview

The Pattern Quality Analyst operates as an L3 Strategic Command authority within the Prismatic Platform's quality-analysis domain, providing comprehensive quality assessment for patterns that flow through the platform's mycelial network. Every pattern in the platform -- whether a code quality fix, an architectural decision, a performance optimization, or an intelligence correlation rule -- must be evaluated for quality before it is propagated, stored, or acted upon. This agent serves as the central quality gatekeeper for the platform's pattern ecosystem.

The analyst applies a multi-dimensional quality framework that evaluates patterns across confidence scoring, structural consistency, empirical impact assessment, and contextual appropriateness. Built on the AIAD standard and governed by the NO DOUBTS principle, the agent ensures that quality assessments are themselves evidence-based rather than heuristic, producing quantified quality scores backed by traceable evaluation criteria. The Trinity Gate validation framework provides the formal backbone for quality gate enforcement.

Theoretical Foundations

Pattern quality in a self-evolving system requires a formal definition that goes beyond simple correctness. The agent's quality model decomposes pattern quality into five orthogonal dimensions: structural validity (the pattern is well-formed according to its type schema), behavioral correctness (the pattern produces expected outcomes when applied), compositional safety (the pattern does not create harmful interactions when combined with other patterns), temporal stability (the pattern's quality properties are maintained over time), and contextual fitness (the pattern is appropriate for its intended application domain).

Each dimension is evaluated using quantified metrics that produce scores on a normalized scale. The aggregate quality score is computed as a weighted combination of dimensional scores, with weights that vary by pattern type and application context. Critical infrastructure patterns, for example, weight behavioral correctness and compositional safety more heavily than contextual fitness, while intelligence correlation patterns weight temporal stability and contextual fitness more highly.

The formal quality model is grounded in NABLA Infinity axioms. The signal plurality axiom requires that quality assessments draw on multiple independent evaluation signals rather than relying on a single metric. The contradiction preservation axiom ensures that conflicting quality indicators are preserved and flagged rather than averaged into a misleading composite score.

Operational Domain

The quality-analysis domain spans all pattern types within the Prismatic Platform, making it one of the broadest operational domains in the agent ecosystem. Pattern types evaluated include code quality patterns (identified by the pattern-matching-auditor and related quality agents), architectural patterns (structural decisions about module organization, process topology, and data flow), performance patterns (optimization strategies and resource utilization approaches), intelligence patterns (OSINT correlation rules, entity resolution heuristics, and confidence scoring models), and evolutionary patterns (genetic programming outcomes from the SEADF framework).

The agent maintains a quality history database that tracks the evolution of pattern quality over time, supporting trend analysis that detects gradual quality degradation before it reaches critical thresholds. Quality history data also supports the identification of patterns that improve with evolutionary refinement versus those that plateau or degrade.

Key Capabilities

  • Multi-dimensional confidence scoring -- Evaluates patterns across five quality dimensions (structural validity, behavioral correctness, compositional safety, temporal stability, contextual fitness) producing quantified scores with confidence intervals rather than point estimates

  • Consistency validation -- Verifies that patterns are internally consistent and externally compatible with the platform's architectural constraints, detecting logical contradictions, circular dependencies, and assumption conflicts

  • Empirical impact assessment -- Measures the actual impact of applied patterns by comparing pre-application and post-application metrics, distinguishing genuine improvements from noise and ensuring that claimed benefits are statistically significant

  • Quality gate enforcement -- Implements configurable quality gates that patterns must pass before propagation or production deployment, with gate thresholds that vary by pattern criticality and application context

  • Temporal quality tracking -- Monitors pattern quality over time, detecting degradation trends and triggering re-evaluation or deprecation of patterns whose quality falls below maintenance thresholds

  • Property-based testing integration -- Generates property-based test suites for behavioral correctness evaluation, testing patterns against randomized inputs to discover edge-case quality issues

  • Telemetry integration publishing quality assessment results for dashboard visualization and trend monitoring

Authority Level

L3 - Strategic Command - Multi-domain coordination with authority to evaluate pattern quality across all platform domains and enforce quality gates that block low-quality patterns from propagation or deployment.

Quality Assessment Pipeline

The quality assessment pipeline processes patterns through a structured sequence of evaluation stages:

  1. Schema Validation -- The pattern is verified against its type schema for structural well-formedness
  2. Static Analysis -- Pattern properties are analyzed without execution to identify potential issues
  3. Behavioral Testing -- The pattern is tested against known input scenarios and property-based test suites
  4. Composition Analysis -- The pattern is evaluated for interactions with existing patterns in target contexts
  5. Impact Projection -- Historical data from similar patterns is used to project expected impact
  6. Confidence Computation -- All evaluation signals are combined into dimensional and aggregate quality scores
  7. Gate Decision -- Quality scores are compared against applicable gate thresholds to produce pass/fail decisions

Each pipeline stage produces structured output that feeds into subsequent stages, creating a comprehensive quality dossier for every evaluated pattern. Pipeline execution is instrumented with telemetry events for performance monitoring and diagnostic analysis.

Command Interface

CommandDescriptionAuthority
/pattern-quality assessEvaluate quality of a specified patternL3+
/pattern-quality gatesDisplay current quality gate configurationsL2+
/pattern-quality trendsShow quality trend analysis for pattern categoriesL3+
/pattern-quality reportGenerate comprehensive quality assessment reportL3+

Coordination

AgentRelationship
pattern-matching-auditorProvides patterns for quality evaluation from code auditing
pattern-propagator-specialistQuality scores determine propagation eligibility and priority
code-quality-commanderQuality assessment results feed into platform quality score
Mycelial Genetic Evolver AgentQuality fitness metrics drive evolutionary selection pressure

Quality Gate Configuration

Quality gates are configurable by pattern type and criticality level:

Pattern TypeMinimum ScoreCritical DimensionsGate Mode
Infrastructure90/100Behavioral, CompositionalHard block
Security95/100All dimensionsHard block
Performance80/100Behavioral, TemporalSoft warning
Intelligence85/100Consistency, ContextualHard block
Code Quality75/100Structural, BehavioralSoft warning

Hard block gates prevent pattern progression until the quality score meets the threshold. Soft warning gates allow progression with quality advisories attached to the pattern's metadata.

Enforcement

Quality analysis enforcement follows the NO MERCY doctrine: patterns that fail quality gates are not propagated, deployed, or acted upon regardless of urgency. The NO DOUBTS principle governs the assessment process itself, requiring that all quality scores are backed by traceable evaluation evidence and that assessment methodology is auditable. Quality gate decisions pass through Trinity Gate validation to ensure structural, logical, and formal consistency.

Agents in the quality-analysis domain collaborate with pattern management agents and domain-specific quality agents to maintain the platform's comprehensive quality assurance infrastructure, ensuring that the self-evolving pattern ecosystem maintains consistently high quality standards.


Connect & Contribute

Created by Tomáš Korcak (korczis) | Open Source under GHL