Skip to content

Add review retaliation guard - #607

Open
pine-harbor wants to merge 1 commit into
SCIBASE-AI:mainfrom
pine-harbor:review-retaliation-guard-15
Open

Add review retaliation guard#607
pine-harbor wants to merge 1 commit into
SCIBASE-AI:mainfrom
pine-harbor:review-retaliation-guard-15

Conversation

@pine-harbor

Copy link
Copy Markdown

/claim #15

Summary

Adds review-retaliation-guard, a focused reputation-system guard for detecting and freezing post-critical-review retaliation before reputation deltas, badges, endorsements, leaderboards, or public profile exports are applied.

This slice is intentionally narrow for the Community & User Reputation System: after someone leaves a critical review, it asks whether affiliated authors, labs, institutions, funders, or study-team actors punished that reviewer inside a cooling-off window.

What It Covers

  • Critical review detection from recommendation, rating, tone, or criticality score.
  • Author/coauthor/lab/institution/funder/study-team relationship checks for reputation actors.
  • Punitive events such as downvotes, reputation penalties, badge removal, endorsement withdrawal, role revocation, reviewer blocking, and profile visibility reduction.
  • Coercive message detection when a reputation event pressures the reviewer to soften criticism.
  • Clustered retaliation bursts from multiple affiliated actors.
  • Public reputation export freezes while retaliation risk is unresolved.
  • Independent moderator review and appeal-window checks.

Included Artifacts

  • Dependency-free Node module: review-retaliation-guard/src/index.js
  • Synthetic sample packet data: review-retaliation-guard/data/sample_reputation_events.json
  • Tests: review-retaliation-guard/test/review-retaliation-guard.test.js
  • Demo/report generator: review-retaliation-guard/scripts/demo.js
  • Generated reviewer packet, JSON summary, SVG summary, and MP4 slate in review-retaliation-guard/reports/

Validation

  • npm.cmd test: 6 tests passed.
  • npm.cmd run check: syntax checks passed.
  • npm.cmd run demo: generated 4-packet report with CLEAR: 2, REVIEW: 0, HOLD: 2.
  • npm.cmd run video: generated reports/demo.mp4.
  • git diff --check: passed.
  • ffprobe: H.264, 1280x720, 8.000 seconds, 30 fps, 240 frames.

The MP4 is a generated FFmpeg color-source/drawtext slate, not a desktop or browser recording. It contains no private data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants