Use Superb / Studio workflow

Work with audience interpretation

Superb Studio groups Readback, Notes, and Crowdread around one question: what did your audience think you meant?

Readback#

Start with the original post and a permissioned set of responses. Preserve which phrase each response concerns. Separate interpretations from reactions: “I disagree” does not tell you what the commenter thought the claim was.

For “College isn’t necessary anymore,” distinguish “college has no value” from “not every career requires college.” Both are possible audience readings; they are not interchangeable.

The API’s argument analysis can structure supplied messages. It does not itself provide a validated population-level clustering or percentage estimate. Only calculate proportions from an explicitly defined sample and reviewed grouping.

Notes#

Write down the intended meaning, including the criterion and any excluded claim. For example: “By necessary, I mean a formal requirement for entering this profession. I am not saying education has no value.”

Keep that note labeled as the creator’s declared intent. It should not overwrite the audience’s reading or become a universal definition of the expression.

Crowdread#

Ask people to read the same passage independently before showing other responses. Compare readings and identify the specific word or missing context behind a split.

Report the sample size, how people were selected, and unresolved answers alongside any distribution. A small self-selected group cannot establish what an entire audience believes.

Keep the records separate#

Maintain three records: the original content, audience interpretations, and creator intent. Link them rather than merging them. Private responses do not enter the contribution system automatically.

Next: Observation permissions and product integration.