COI
Code Orthogonal Integrity
Structural stability and maintainability
Guide · MistSeeker Coder
Score utilization guide for COI, ORI, and GSS.
MistSeeker measures structural, operational, and semantic stability. Use this guide to interpret score combinations and prioritize engineering decisions.
SCORE INTERPRETATION
SCORE FRAMEWORK
Three axes for stability evaluation
ORI
Operational Robustness Index
Execution safety and side-effect risk
GSS
Geometric Stability Score
Semantic stability under small changes
COI
Structural Integrity
COI evaluates function complexity, nesting, and structural density to show where refactoring risk is concentrated.
USE CASES
- •Refactoring priority decisions
- •Module-level design quality checks
- •Code review focus selection
LOW SCORE SIGNALS
- •Deep nesting and oversized functions
- •Repeated patterns and low cohesion
- •Rising maintenance and defect probability
ORI
Operational Robustness
ORI quantifies instability from external I/O, global state changes, randomness, and environment dependencies.
USE CASES
- •Production risk pre-check
- •Side-effect isolation in core flows
- •Security and reliability review support
LOW SCORE SIGNALS
- •Environment-sensitive behavior
- •Hidden side effects in control flow
- •Unpredictable runtime outcomes
GSS
Semantic Stability
GSS measures semantic movement under perturbation to detect whether code meaning is structurally stable.
USE CASES
- •LLM-generated code validation
- •Post-refactoring semantic verification
- •Long-term semantic drift monitoring
LOW SCORE SIGNALS
- •Meaning shifts under minor edits
- •Hidden semantic fragility zones
- •Higher long-term regression risk
COMBINATION MATRIX
How to read score combinations
| Combination | Characteristics | Interpretation |
|---|---|---|
| COI↑ / ORI↑ / GSS↑ | Balanced and stable | Healthy baseline for scale and change |
| COI↓ / ORI↑ / GSS↑ | Structurally weak | Prioritize refactoring and modular cleanup |
| COI↑ / ORI↓ / GSS↑ | Operationally fragile | Reduce side effects and environment coupling |
| COI↑ / ORI↑ / GSS↓ | Semantically unstable | Verify logic meaning and boundary behavior |
| COI↓ / ORI↓ / GSS↓ | High structural risk | Immediate deep inspection recommended |
CONCLUSION
Use all three scores together, not in isolation
COI explains structural quality, ORI explains runtime risk, and GSS explains semantic resilience. The combined view provides decision-ready guidance for refactoring, test strategy, and release risk control.