Design decision: Option B (revision records). Each member uploads revisions to their own PDS with an origin field pointing at the original document. AppView aggregates revisions across member PDSes. Owner can accept (re-upload blob, update document) or ignore. Degrades gracefully without AppView — CLI can poll known members. Composes with existing keyring model: member already has GK, encrypts revision under it. Needs: app.opake.cloud.revision lexicon, origin field on document, propose/accept CLI commands, AppView revision indexing.
Design decision: Option B (revision records). Each member uploads revisions to their own PDS with an origin field pointing at the original document. AppView aggregates revisions across member PDSes. Owner can accept (re-upload blob, update document) or ignore. Degrades gracefully without AppView — CLI can poll known members. Composes with existing keyring model: member already has GK, encrypts revision under it. Needs: app.opake.cloud.revision lexicon, origin field on document, propose/accept CLI commands, AppView revision indexing.