Skip to content

Add dataset split release guard - #611

Open
pine-harbor wants to merge 1 commit into
SCIBASE-AI:mainfrom
pine-harbor:dataset-split-release-14
Open

Add dataset split release guard#611
pine-harbor wants to merge 1 commit into
SCIBASE-AI:mainfrom
pine-harbor:dataset-split-release-14

Conversation

@pine-harbor

Copy link
Copy Markdown

/claim #14

Summary

Adds dataset-split-release-guard, a focused Scientific/Engineering Data & Code Hosting guard for train/validation/test split manifests before DOI publication, public API release, public previews, or reproducibility badges.

This is intentionally narrow: it does not rebuild broad FAIR manifests, artifact package integrity, schema evolution, data dictionaries, malware quarantine, sandbox egress, notebook rerun determinism, spreadsheet formula provenance, accessibility previews, SBOM checks, or general license metadata. It covers the release boundary for split artifacts.

What It Covers

  • Required train, validation, and test split manifests.
  • Dataset record count parity with split record totals.
  • Record identifier overlap across splits.
  • Group-level leakage across participant, patient, subject, lab, or other grouping identifiers.
  • Deterministic seed and split-script hash provenance.
  • Per-split checksum and manifest-hash coverage.
  • License and access-state parity across split artifacts.
  • Class or stratum balance drift beyond release policy.
  • Embargoed records present in public split manifests.
  • Public DOI/API release left enabled while split-integrity findings are unresolved.

Included Artifacts

  • Dependency-free Node module: dataset-split-release-guard/src/index.js
  • Synthetic split release packets: dataset-split-release-guard/data/sample_split_release_packets.json
  • Tests: dataset-split-release-guard/test/dataset-split-release-guard.test.js
  • Demo/report generator: dataset-split-release-guard/scripts/demo.js
  • Generated reviewer packet, JSON summary, SVG summary, and MP4 slate in dataset-split-release-guard/reports/

Validation

  • npm.cmd test: 8 tests passed.
  • npm.cmd run check: syntax checks passed.
  • npm.cmd run demo: generated 4-packet report with RELEASE: 1, REVIEW_RELEASE: 1, HOLD_RELEASE: 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