coulomb-social/docs/usecases/productive-content-acceptance-session.md

Productive content acceptance session

The combined image7906f461 is independently verified at Helm revision20, completed2026-10-31T20:22:30Z. Record your review date and actual verdicts.

Use your normal account at https://app.coulomb.social. Create two private spaces, acceptance-a-20261031 and acceptance-b-20261031, or choose unused names if those already exist. These are disposable review spaces. Keep existing workspaces and their grants intact. Keep the review artifacts until the verdicts are recorded.

1. Authoring and attachments — UC-003 / WP-0013-T06

In space A, create a page titled Acceptance notes, file name notes, and abstract Content and attachment review. Use this body:

Acceptance notes.

<ol start="3">
<li>Third item</li>
<li>Fourth item</li>
</ol>

**Keep this text when adding or removing attachments.**

Save and reopen. The list should start at3. In Attachments, add attachment-check.txt and visual-check.png. Download the text file and open the image: the text has two short lines and the image has blue and yellow halves. Files should remain available after reopening.

To check a page Visual, use Open image and take the assets/... part of its address as the Visual field in the page editor. Save and check the displayed image. Edit the title/abstract/body and reopen to check persistence.

Open the page editor in two tabs. Save a change in the first; then try saving the older second tab. The second submission must retain your submitted text and ask you to reopen/merge rather than overwrite the newer page. Return to the current page and check that its attachments and Visual remain intact.

Verdicts: UC-003 accepted/gap and attachments accepted/gap, with any observed difference. The custom-topic rendering and obsolete-scrap dispositions are already recorded; they do not need another review.

2. Independent copy and move — UC-004

Duplicate the page into space B with file name copied. Change its body and remove its text attachment. Reopen the original in A: its body and downloadable text file should remain unchanged. The removed copy's earlier revisions retain the file, as agreed in the retention policy.

Create another duplicate in A with file name moving, retaining both files. Save its address before moving it to B with file name moved. Its content, Visual and downloads should remain intact. Its old address should reach the destination for an authorized account; the sharing check below verifies denial when the destination is private to you.

Verdict: UC-004 accepted/gap, including the incoming-address permission result once the second participant has checked it.

3. Sharing and revocation — UC-005

The user nominated testuser as the second participant. The live app had only one member at preparation. Have testuser sign in to the same tenant and obtain their member ID from Your app data. The same participant can cover the ungranted, viewer and revoked states in sequence, using their own browser session.

Before a grant, they try the A page and its direct image/download URLs: access must be denied. In A's Share space screen, grant their member ID Viewer access. They should now read and download, but receive denial for direct edit/copy/move URLs copied from your session. Space B stays private: they must be denied both the moved page and its old incoming address.

Revoke their A access. They retry the page, image and saved download URLs: each must be denied. Review the remaining grants and creator access in Share space. Sharing does not send email.

Verdict: UC-005 accepted/gap, including the participant's three access states.

4. Account-local portability — UC-006

Open https://app.coulomb.social/account/data/ and Export my account records. Inspect the downloaded JSON privately: profile, identity references and space memberships should match your local account. Pages/assets remain in their spaces; this account export is distinct from the complete operator client-data export.

Review Leaving the app and the ownership/succession explanation. Sole-owned spaces must gain another active owner before local account removal. Shared content remains, while platform identity and mailbox remain under their existing owners. Review these screens with your productive account. Any actual account removal exercise needs a separately selected disposable member.

Verdict: UC-006 accepted/gap, stating whether export and the displayed exit/ succession semantics meet your needs. Keep the account export private.

Result record

Record the deployed revision/date and each verdict independently:

• UC-003 authoring:
• Attachments:
• UC-004 copy/move and old-address permissions:
• UC-005 sharing/revocation:
• UC-006 account-local export and exit/succession semantics:

An unresolved gap or an unperformed participant check stays open. Automated regression, native postflight and recovered-store proofs remain supporting evidence and do not supply these user verdicts.