Add project funding attribution guard#304
Conversation
|
/claim #11 |
|
Quick follow-up: this PR remains open, mergeable, and ready for review for #11. Happy to adjust if maintainers prefer a different direction for this scoped implementation. |
|
Quick follow-up on this PR since it is still open. If there’s anything you want adjusted for merge, I can update quickly. If it looks good, a review/merge when you have bandwidth would be appreciated. For bounty processing, I will keep payout handling strictly through the platform-supported escrow/Stripe rails. |
|
Maintenance follow-up: this PR remains open and mergeable on my side. If you want any revisions, I can turn them around quickly. Thanks for the review when you have bandwidth. |
|
Maintenance follow-up: this PR is still open and mergeable on my side. I can make revisions quickly if maintainers want a different direction or narrower scope. |
Summary
Scope
This focuses on project-level funding and institutional attribution readiness for #11 and avoids overlapping with existing workspace/RBAC ledger, privacy review, member lifecycle, institutional recertification, anonymous review escrow, identity merge/export, data-room consent, researcher profile sync, archive handoff, access-audit anomaly, role delegation, invitation-domain, and MFA enforcement slices.
Verification
node project-funding-attribution-guard/test.jsnode project-funding-attribution-guard/demo.jsnode --check project-funding-attribution-guard/index.jsnode --check project-funding-attribution-guard/sample-data.jsnode --check project-funding-attribution-guard/test.jsnode --check project-funding-attribution-guard/demo.jsffprobe -v error -show_entries format=duration,size -show_entries stream=codec_name,width,height -of default=noprint_wrappers=1 project-funding-attribution-guard/reports/demo.mp4git diff --check/claim #11