SC
Add manuscript evidence binding guard
SCIBASE-AI/SCIBASE.AI#335

Summary

/claim #12

Adds manuscript-evidence-binding-guard/, a self-contained release guard for the real-time collaborative research editor. It binds publication-ready manuscript claims, figures, tables, and equations to locked evidence anchors with section version hashes, notebook output digests, upstream dataset/code digests, DOI/citation metadata, and reviewer actions.

Why this solves the poster value

This solves a concrete submission failure mode for issue #12: a collaborative manuscript can look ready while claims or assets still point to stale notebook output, changed datasets, missing citations, or outdated section versions. The poster value is correctness, auditability, and reproducibility at the final export step: the guard blocks stale or unbound evidence before submission and gives reviewers a decision packet they can verify in minutes.

Why this submission should be rewarded

Compared with broad editor demos and formatting slices, this adds a distinct release-quality control at the point where a bounty poster would care most: whether the final manuscript can be trusted for submission. It is complete end-to-end for that slice: evaluator, sample release data, regression tests, JSON/Markdown/SVG reports, requirement map, acceptance notes, and a short H.264 MP4 demo.

Requirements and non-overlap

  • Requirements map: manuscript-evidence-binding-guard/requirements-map.md
  • Acceptance notes: manuscript-evidence-binding-guard/acceptance-notes.md
  • Non-overlap audit: searched issue #12 attempts and open PRs for broad editor foundation, operation replay, offline conflict, notebook workbench, reference formatting, authorship governance, freeze/recovery, figure/table review, discussion sidebar, round-trip fidelity, review decision, task dependency, equation/figure anchor, kernel lease, presence privacy, and accessibility parity. This PR is narrower: manuscript evidence binding at submission export time.

Artifacts

  • Demo video: manuscript-evidence-binding-guard/reports/demo.mp4
  • JSON summary: manuscript-evidence-binding-guard/reports/summary.json
  • Markdown review packet: manuscript-evidence-binding-guard/reports/evidence-binding-review-packet.md
  • SVG summary: manuscript-evidence-binding-guard/reports/summary.svg

Validation

  • npm run check
  • npm test
  • npm run demo
  • npm run video
  • git diff --check
  • Disclosure-term scan over the new module

Reviewer path

  1. cd manuscript-evidence-binding-guard
  2. Run npm run check && npm test && npm run demo.
  3. Optional: run npm run video to regenerate the H.264 walkthrough.
  4. Open reports/evidence-binding-review-packet.md and confirm the stale evidence, missing citation, section lock, and section hash cases are held.

Scope boundaries and residual risk

This does not implement editor UI, realtime transport, notebook execution, storage, or citation manager integrations. It is intentionally a focused release guard that those systems can call before submission export. Regression risk is low because the module is isolated and dependency-free.

Claim

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

Contributors

MJ

mjshanker

@mjshanker

100%

Sponsors

SC

SCIBASE.AI

@SCIBASE.AI

$700