-
Notifications
You must be signed in to change notification settings - Fork 0
RFC-002: Read-only CRDT collaboration #9
Copy link
Copy link
Open
Labels
compatibilityAffects file formats, exports, or public APIsAffects file formats, exports, or public APIspost-launchPlanned after launch feedback or post-launch windowPlanned after launch feedback or post-launch windowrfcMaintainer-gated design proposalMaintainer-gated design proposalsecurity-reviewRequires security or privacy reviewRequires security or privacy review
Description
Metadata
Metadata
Assignees
Labels
compatibilityAffects file formats, exports, or public APIsAffects file formats, exports, or public APIspost-launchPlanned after launch feedback or post-launch windowPlanned after launch feedback or post-launch windowrfcMaintainer-gated design proposalMaintainer-gated design proposalsecurity-reviewRequires security or privacy reviewRequires security or privacy review
Type
Fields
Give feedbackNo fields configured for issues without a type.
Summary
Evaluate a read-only initial CRDT collaboration model for rubric review after security review.
Trigger
Problem
Teams want shared review visibility, but Rubric Studio Open must stay local-first and avoid silently becoming hosted collaboration software.
Proposal
Define a read-only collaboration data model, storage boundaries, consent model, privacy review, and rollback plan before implementation.
Tests And Evidence
Closure requires CRDT data model, privacy review, tests, docs, and maintainer approval.
Maintainer Decision