SC
Add data availability statement guard
SCIBASE-AI/SCIBASE.AI#375

/claim #12

Summary

Adds collaborative-data-availability-statement-guard, a self-contained Real-time Collaborative Research Editor slice that gates final manuscript export when data/code availability statement evidence is not review-ready.

The guard evaluates:

  • required data and code availability sections
  • repository accessions and statement citation anchors
  • dataset/code license acceptability
  • reviewer-only access link freshness
  • de-identification evidence for human-derived material
  • required collaborator approvals
  • blocking availability comments and unmerged editor changes

Non-overlap

This is intentionally separate from the existing and competing slices. It is not a reference-library merge guard, notification visibility guard, accessibility checker, presence privacy guard, evidence binding guard, or general embargo-release workflow. It focuses on availability-statement export readiness for a collaborative manuscript package.

Local validation

Run from collaborative-data-availability-statement-guard/:

npm run check
npm test
npm run demo
npm run demo:video

All four commands passed locally.

Reviewer artifacts

  • reports/summary.json
  • reports/reviewer-packet.md
  • reports/summary.svg
  • reports/demo.webm

Safety

All data is synthetic. The module does not call GitHub, Zenodo, OSF, journal systems, identity services, storage APIs, email systems, or live manuscript export services. It does not include private manuscripts, credentials, human-subject records, or reviewer data.

Current status - 2026-05-30 01:00 IST

Visibility refresh after KoiosSG updated same-issue #12 PR #418. PR #375 remains open, non-draft, CLEAN/mergeable, Algora-labeled, and distinct: it gates final manuscript export on data/code availability statement evidence, repository accessions, licenses, reviewer-only link freshness, de-identification evidence, collaborator approvals, and unresolved availability comments. PR #418 remains a separate clipboard/file-import provenance guard before collaborative insertion.

Current status - 2026-05-30 02:17 IST

Visibility refresh after KoiosSG updated same-issue #12 PR #418 again. PR #375 remains open, non-draft, CLEAN/mergeable, Algora-labeled, and claim-marked for issue #12.

PR #375 remains the collaborative data-availability statement guard: required data/code sections, repository accessions, statement citation anchors, dataset/code license acceptability, reviewer-only access freshness, de-identification evidence, collaborator approvals, blocking availability comments, and unmerged editor changes before final manuscript export.

PR #418 remains a separate collaborative clipboard/file-import provenance guard for duplicate anchors, private-reference redaction, table-cell path scanning, formula-cell handling, and source-trust metadata. No contributor-side code changes are pending unless maintainers request revisions.

Current status - 2026-05-30 02:49 IST

Visibility refresh after KoiosSG updated same-issue #12 PR #418 later than my last status. PR #375 remains open, non-draft, CLEAN/mergeable, Algora-labeled, and claim-marked for issue #12.

PR #375 remains the collaborative data-availability statement guard: required data/code sections, repository accessions, statement citation anchors, dataset/code license acceptability, reviewer-only access freshness, de-identification evidence, collaborator approvals, blocking availability comments, and unmerged editor changes before final manuscript export.

PR #418 remains a separate collaborative clipboard/file-import provenance guard. No contributor-side code changes are pending unless maintainers request revisions.

Current status - 2026-05-30 12:06 IST

Visibility refresh after KoiosSG updated same-issue #12 PR #418 later than my last PR-body status. PR #375 remains open, non-draft, MERGEABLE, bounty-labeled, and claim-marked for issue #12. Its Algora claim remains Pending for USD 700: https://algora.io/claims/JXzZctN6u4EnVgcQ

PR #375 remains the collaborative data-availability statement guard for final manuscript export readiness: required data/code sections, repository accessions, statement citation anchors, dataset/code license acceptability, reviewer-only access freshness, de-identification evidence, collaborator approvals, blocking availability comments, and unmerged editor changes.

PR #418 remains a separate clipboard/file-import provenance guard. No contributor-side changes are pending unless maintainers request revisions.

Claim

Total prize pool $700
Total paid $0
Status Pending
Submitted May 22, 2026
Last updated May 22, 2026

Contributors

TA

Taher Dhanerawala

@taherdhanera

100%

Sponsors

SC

SCIBASE.AI

@SCIBASE.AI

$700