Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mehen.ophi.dev/llms.txt

Use this file to discover all available pages before exploring further.

RCI answers “Should I review this document carefully?”. A small document can be review-critical if it is dense with technical anchors. RCI combines a per-word DensityScore with a delta term and a changed-links/artifacts term.

​
Formula

DensityScore = mehen-internal blend of:
    MCC per word
  + MDH volume per word
  + RepositoryGroundingScore
  + EvidenceCoverageScore
  + LinkReviewBurden per word
  + embedded code complexity per word

RCI = clamp01(
    0.65 · DensityScore
  + 0.20 · sat(abs(metric_delta_percent); 10, 60)
  + 0.15 · sat(changed_links_or_artifacts; 2, 20)
) · 100

​
Bands

RCIMeaning
0–25Low — skim is fine.
26–50Normal review.
51–75Careful review recommended.
76–100High-risk change.

​
DMI × RCI × Filler matrix

DMIRCIFiller RiskMeaning
HighLowLowLong but easy and probably healthy.
HighLowHighEasy to maintain but likely low-value filler.
LowHighLowDense valuable doc; review carefully.
LowHighHighDangerous: hard to maintain and weakly grounded.
This matrix is the canonical way to summarize a Markdown file in CI.

​
References

  • Bacchelli, A. & Bird, C. (2013). Expectations, outcomes, and challenges of modern code review. ICSE 2013 — empirical basis for prioritizing review attention by per-change density. DOI · Author copy.
  • Rigby, P. C. & Bird, C. (2013). Convergent contemporary software peer review practices. ESEC/FSE 2013 — supports the “review what changed” prioritization that RCI encodes. DOI.

​
See also