Skip to content

Add collaborative ethics consent guard - #606

Open
pine-harbor wants to merge 1 commit into
SCIBASE-AI:mainfrom
pine-harbor:collaborative-ethics-consent-12
Open

Add collaborative ethics consent guard#606
pine-harbor wants to merge 1 commit into
SCIBASE-AI:mainfrom
pine-harbor:collaborative-ethics-consent-12

Conversation

@pine-harbor

Copy link
Copy Markdown

/claim #12

Summary

Adds collaborative-ethics-consent-guard/, a self-contained export guard for ethics and consent content inside the real-time collaborative research editor.

The guard analyzes synthetic collaborative manuscript packets before publication export and emits deterministic RELEASE, REVIEW, or HOLD decisions with evidence-linked remediation for:

  • missing ethics approval identifiers
  • expired approvals
  • missing exemption rationale
  • vulnerable-population review gaps
  • missing consent statements or waiver rationale
  • consent-scope mismatch against the requested export scope
  • missing translated-consent coverage
  • pending edits in locked ethics sections
  • stale ethics-section review after collaborative edits
  • private ethics comments visible in export
  • participant-like identifiers in collaborative comments

Issue #12 fit

  • Real-time collaboration: reviews collaborative comments, pending edits, locks, and section state before export.
  • Change tracking and suggestions: detects pending ethics edits and unresolved ethics comments.
  • Rich scientific manuscript export: guards ethics/consent statements before manuscript export.
  • Version history and autosave: checks review freshness after collaborative changes.
  • Inline comments and review sidebar: blocks private reviewer notes and participant-like identifiers from public export.
  • Publication-ready formatting: confirms consent scope, translated-consent coverage, and ethics approval metadata.

Validation

Locally verified on Windows:

npm.cmd test
# tests 7
# pass 7

npm.cmd run demo
# packetCount 4
# RELEASE 1 / REVIEW 1 / HOLD 2

npm.cmd run video
# reports/demo.mp4 generated

npm.cmd run check
# syntax checks passed

git diff --check
# passed

ffprobe reports/demo.mp4
# H.264, 1280x720, 8.000 seconds, 30 fps, 240 frames

Demo and privacy

The demo MP4 is generated from an FFmpeg synthetic color background plus hard-coded text overlays. It is not a screen recording and contains no desktop/browser capture, notifications, real participant data, credentials, private manuscripts, or local personal information.

Safety

Uses synthetic data only. No external APIs, private manuscripts, real participant data, credentials, payment systems, network calls, or live editor data.

AI assistance disclosure

Implemented with Codex assistance and verified locally with deterministic tests and generated artifacts.

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