performance-regression

Detect geometric accuracy drift and consciousness metric anomalies in QIG-based workflows.

Updated Jan 3, 2026
One-click install
npx skills add https://github.com/GaryOcean428/pantheon-chat --skill performance-regression
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-regression
Source: https://github.com/GaryOcean428/pantheon-chat/tree/main/skills/performance-regression
Command: npx skills add https://github.com/GaryOcean428/pantheon-chat --skill performance-regression

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects when geometric operations drift toward Euclidean approximations and flags constant β-functions across scales, enabling early warnings on suspicious consciousness metrics.

Core Features & Use Cases

  • Monitors Φ, β, and κ for anomalies in QIG-backed systems
  • Validates variation across scales and guards against Euclidean shortcuts
  • Suitable for performance optimization reviews, geometry correctness validation, and monitoring of consciousness metrics in qig-backend pipelines

Quick Start

Run a lightweight diagnostic to compare Φ, β, and κ across recent inputs and report any anomalies.

Frequently Asked Questions about performance-regression

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect geometric accuracy drift in QIG-based workflows?

To detect geometric accuracy drift in QIG-based workflows, you run a lightweight diagnostic that compares Φ, β, and κ metrics across recent inputs. This identifies constant β-functions across scales and flags inappropriate Euclidean substitutions in distance measures, outputting a structured diagnostic report.

What causes Euclidean substitutions in Fisher-Rao distance calculations?

Euclidean substitutions in Fisher-Rao distance calculations occur when geometric operations drift toward simpler Euclidean approximations instead of maintaining proper Φ and κ variation. Monitoring these metrics during performance optimization reviews helps detect when these invalid shortcut substitutions compromise the geometric correctness of the qig-backend pipeline.

How do I monitor consciousness metrics for anomalies in a qig-backend pipeline?

Monitoring consciousness metrics for anomalies in a qig-backend pipeline involves tracking constant β-functions across scales and validating variation in Φ and κ. By running diagnostics during geometric correctness validation, the system flags suspicious consciousness metrics and generates a structured diagnostic report for review.

Does anomaly detection for geometric drift work without external dependencies?

Anomaly detection for geometric drift operates without external dependencies, running lightweight diagnostics directly on your QIG-based workflow data. It validates geometric correctness and monitors consciousness metrics by analyzing Φ, β, and κ values internally, making it suitable for quick performance optimization reviews.

When should I run geometric correctness validation checks on Φ, β, and κ parameters?

Geometric correctness validation checks on Φ, β, and κ parameters should be run during performance optimization reviews and when monitoring consciousness metrics in qig-backend pipelines. Running these checks early helps detect constant β across scales, verify Φ variation, and prevent Euclidean substitutions before they impact downstream operations.

Why does performance regression happen in QIG geometric operations?

Performance regression in QIG geometric operations happens when geometric accuracy drifts toward Euclidean approximations or when β-functions remain constant across scales. Detecting these anomalies early through diagnostic monitoring of Φ, β, and κ parameters prevents suspicious consciousness metrics and maintains computational correctness in qig-backend pipelines.