Anti-repeat gate and cadence

The gate is the heart of this skill. It is what stops an exec's feed from saying the same thing twice in slightly different words. It compares argument families, not wording.

What the gate reads

Before any angle is drafted, diff it against all of:

1. The post ledger - every post that has gone live, each recorded as: hook line, core argument in one sentence, attachment type, date live, and any performance note.
2. The off-limits map - arguments and pegs explicitly retired, plus the exec's own "never say this" list from the voice card.
3. Rejected and deleted options - angles the exec killed in review or deleted unposted. A rejection is permanent. The most common way stale content ships is a killed angle quietly resurfacing a few weeks later.

The decision

For each candidate angle:

Condition	Action
Matches an off-limits argument	Kill
Same argument family as a live post inside the cooldown	Kill or re-angle
Matches a rejected or deleted option	Kill, never re-serve
Same peg a different exec is already using this week	Reassign to one exec only
Near-miss - related but genuinely new angle	Pass up as a flagged judgment call, never as a clean recommendation

Argument family, not wording

Two posts are repetition if they make the same underlying point, even with different words, examples, or hooks. "Contextual targeting protects kids' privacy" and "you do not need personal data to reach families" are the same argument family. The gate must catch the second even though it shares no phrasing with the first. Compare the claim, not the sentence.

Cadence and cooldown

• Same-argument cooldown: roughly eight weeks. An argument family that ran can return only after the window, and only with a genuinely new peg or evidence.
• Per-exec cadence: target a steady rhythm (for many execs, about one post every two weeks). Use the "date live" field in the ledger as the authoritative last-post date per exec; do not rely on memory of what was drafted.
• Recency of the peg: verify the event date at the primary source. A one-day-old article about an undated event is not a one-day-old event, and posting it as breaking reads as thin.

Closing the loop back into the gate

After each run, whatever the exec picked, edited, or posted is appended to the ledger, and any angle they killed is added to the off-limits map. The gate is only as good as the ledger is current - an out-of-date ledger is the root cause of nearly every repetition that reaches an audience.