Emotional Vocabulary Template 1
Emotion map: Trigger → broad family → intensity → duration → mixed emotion → visible behavior.
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
Richer emotional vocabulary improves writing when it sharpens observation rather than decorating it: the chosen word should fit what triggered the feeling and how the person experiences or expresses it.
Emotion map: Trigger → broad family → intensity → duration → mixed emotion → visible behavior.
Scene line: [Person] felt [precise emotion] when [trigger], shown by [behavior/thought].
Contrast: Not [nearby emotion], but [more precise emotion] because [difference].
Revision: Replace “felt bad/good” with [emotion] only when the context supports [specific cause].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].