Build · Assess & Decide · Writing & Content
Build a communication-channel richness selection register
A channel-selection register with one row per message, each carrying an authenticity flag and an emotional-load flag that deterministically map to a recommended channel from the allowed richness ladder, validated for rule-consistency.
You receive: A JSON object: { rows: [ { message_label, authenticity: enum, emotion_load: enum, recommended_channel, rationale } ] }
Part of Pitch Investors
What's verified: STUD verifies each message is tagged with valid authenticity/emotion enums and routed to a channel that matches the deterministic richness rule, with rationales present. STUD does NOT judge whether the author labeled the authenticity/emotion correctly, nor whether the chosen channel will actually land as authentic in practice.
Opens soon
This objective is verified and ready. It opens soon, once sign-in and payments are live.
Deliverable interface
The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.
{
"buyerParamKeys": [
"messages",
"require_rationale",
"richness_ladder"
],
"checkNames": [
"format_parses",
"coverage",
"enums_valid",
"channel_in_ladder",
"mapping_consistent",
"no_dup_rows",
"rationale_present"
],
"constants": {},
"deliverableLabel": "communication_channel_richness_register",
"documentKeys": [
"authenticity",
"emotion_load",
"message_label",
"rationale",
"recommended_channel",
"rows"
],
"enumLiterals": [
[
"authentic",
"inauthentic"
],
[
"high",
"low"
]
],
"submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
"tier": "doc-validator"
}Get early access to STUD the day it goes live.