call-cross-call-consistency-checker

call-cross-call-consistency-checker

Call someone twice and say two different things, and you were never really trusted the first time.

Every other skill in this repository analyzes one call. This one analyzes the space BETWEEN two calls to the same person: did the organization tell them the same price, the same date, the same time it told them before? Contradictions across calls are how campaigns lose people - each new call quietly rewrites reality, and the person on the line is the only one who notices.

When To Use

• when a destination has received two or more calls and any result from the latest one will be written somewhere
• before drafting the NEXT call to a person whose earlier call had disputed or confusing values
• to generate a consistency-guarded goal for the follow-up plan_call

When Not To Use

• to decide which call's value is true; the record (or a human with it) decides - this skill only routes to verification
• on calls to different destinations; comparing unrelated people's facts is meaningless
• as a memory system; it compares two transcripts you hand it, it stores nothing
• during a call; strictly post-call analysis plus pre-call goal crafting

Workflow

Compare two finished calls

python3 scripts/cross_call_consistency_checker.py analyze \
  --transcript-a path/to/call-a.json --transcript-b path/to/call-b.json

Reads the real get_call_run result shape ({status, result: {transcript}}) or the flat fixture shape used by sibling skills. Emits a card:

• comparisons[] per fact kind (amount / date_weekday / date_day / time; weekdays and day-of-months are separate sub-kinds so "Tuesday the 15th" vs "Wednesday the 15th" contradicts on the weekday instead of hiding behind the shared day number):
  • CONSISTENT with the shared values when the calls overlap
  • CONTRADICTED when both calls state the kind and share no value
  • ONLY_STATED when just one call mentions the kind
• Only AGENT turns are extracted: the organization's statements must stay consistent; the callee mentioning a different value is a correction, not a record
• Legitimate reschedules do not self-contradict: "we moved you from the 12th to the 15th" shares a value with a later call that says "the 15th"
• verdict: CONTRADICTIONS_FOUND / CONSISTENT / NOTHING_TO_COMPARE, plus unclear paths for empty or agent-less inputs
• Values are normalized ($45 = "45 dollars"; Tuesday the 15th = weekday + ordinal; 2 p.m. = 1400) and masked in output