Epistrophe Template 1
Pattern: [clause 1] [repeated ending]. [clause 2] [repeated ending].
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.
Strong epistrophe makes the repeated ending carry increasing or changing significance as each preceding clause adds a new context; it should sound intentional rather than accidentally repetitive.
Pattern: [clause 1] [repeated ending]. [clause 2] [repeated ending].
Escalation: [action 1] for [phrase], [action 2] for [phrase], even [action 3] for [phrase].
Analysis: The repeated ending “[phrase]” is epistrophe, emphasizing [idea] through recurring closure.
Contrast: Anaphora repeats beginnings; here, the repetition falls at the ends of [clauses/lines].
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 → [ ].