The 2010 policy defines foundational terms, while the 2024 document introduces specific current operational terms like 'local teams' and 'active operations' within the exception context.
The document contains policy terms and years but does not mention specific technologies, tools, or protocols by name.
The 2010 operational procedure regarding deletion approval is superseded by the 2024 regional exception which allows local approval, marking the older practice as obsolete in the conflict context.
Scores reflect the high operational focus on deletion timelines, moderate regulatory conflict between policies, and lower technical specificity regarding governance tools.
A major anomaly exists where the 2024 policy permits actions explicitly prohibited by the 2010 enterprise baseline.
The document is invalid as a cohesive governance document because it contains conflicting policies that cannot be simultaneously applied.
{
"badge_class": "score-yellow",
"chunk_id": "db9322ab-9bcb-538d-af5d-6a8359641174",
"confidence": 65.06,
"contextual_qna": [
{
"answer": "Records must be retained for a minimum of seven years from the date of creation.",
"question": "What is the default retention period for customer records?"
},
{
"answer": "Regional teams can delete routine customer service records after three years if approved locally.",
"question": "Can regional teams delete records after three years?"
},
{
"answer": "Deletion must be explicitly approved by the central compliance office.",
"question": "Who must approve the deletion of regulated records?"
},
{
"answer": "A conflict exists between the 2010 enterprise baseline and the 2024 regional exception policy.",
"question": "What constitutes a governance conflict in this document?"
},
{
"answer": "The seven-year enterprise retention baseline is treated as authoritative until resolved.",
"question": "Which policy takes precedence in case of conflict?"
},
{
"answer": "The exception applies to customer service logs, support case notes, and operational follow-up records.",
"question": "What types of records are covered by the local exception?"
},
{
"answer": "Deletions must be documented in the regional exception register when approved locally.",
"question": "What is the role of the regional exception register?"
}
],
"contradictions": [
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "78c611b6-3952-5399-ac23-7f4a55ca0480",
"detected_at": "Thu, 21 May 2026 12:42:45 GMT",
"id": 1,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "db9322ab-9bcb-538d-af5d-6a8359641174"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "78c611b6-3952-5399-ac23-7f4a55ca0480",
"detected_at": "Thu, 21 May 2026 12:42:45 GMT",
"id": 2,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "db9322ab-9bcb-538d-af5d-6a8359641174"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "37025f22-da61-5bbf-933d-2b8797d2ad13",
"detected_at": "Thu, 21 May 2026 12:42:45 GMT",
"id": 3,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "db9322ab-9bcb-538d-af5d-6a8359641174"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "37025f22-da61-5bbf-933d-2b8797d2ad13",
"detected_at": "Thu, 21 May 2026 12:42:45 GMT",
"id": 4,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "db9322ab-9bcb-538d-af5d-6a8359641174"
}
],
"core_answers": {
"What is the main idea?": "The document describes a conflict between a 2010 seven-year retention policy and a 2024 regional three-year deletion policy.",
"What processes or procedures are described?": "Teams must maintain records for seven years unless a central compliance office approves early deletion.",
"What risks or threats are discussed?": "The risk of early data deletion violating enterprise retention requirements due to conflicting local policies."
},
"decay_score": 0.3494,
"decay_summary": {
"anomaly": {
"evidence": [
"The 2024 regional exception policy allows local deletion after three years with only regional approval",
"A regional exception alone is not sufficient to override enterprise retention requirements for regulated records"
],
"status": "MAJOR"
},
"archive_suggestion": true,
"counts": {
"legacy_indicators": 3,
"outdated_terms": 0
},
"legacy": [
{
"label": "written operational controls",
"tag": "LEGACY-VALID"
},
{
"label": "central compliance office",
"tag": "LEGACY-VALID"
},
{
"label": "Obsolete Practice",
"tag": "OBSOLETE_PRACTICE"
}
],
"outdated_terms": [],
"regulatory_gap": false,
"regulatory_score": 6,
"rollup": {
"text": "0 outdated \u00b7 3 legacy \u00b7 anomaly: major \u00b7 validation: invalid \u00b7 reg: 6"
},
"severity": "HIGH",
"validation": {
"reason": "The document is invalid as a cohesive governance document because it contains conflicting policies that cannot be simultaneously applied.",
"status": "INVALID"
}
},
"domain_scores": {
"operational": 2,
"regulatory": 3,
"technical": 1
},
"explanation": "The document describes a conflict between a 2010 seven-year retention policy and a 2024 regional three-year deletion policy.",
"is_archived": false,
"ops": 8.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"written operational controls",
"central compliance office",
"regional exception policy",
"local teams",
"active operations"
],
"explanation": "The 2010 policy defines foundational terms, while the 2024 document introduces specific current operational terms like \u0027local teams\u0027 and \u0027active operations\u0027 within the exception context.",
"terms": [
{
"category": "LEGACY-VALID",
"term": "written operational controls"
},
{
"category": "LEGACY-VALID",
"term": "central compliance office"
},
{
"category": "CURRENT",
"term": "regional exception policy"
},
{
"category": "CURRENT",
"term": "local teams"
},
{
"category": "CURRENT",
"term": "active operations"
}
]
},
"prompt_10": {
"evidence": [
"This creates a contradiction because the newer local rule appears to permit behavior that the enterprise baseline explicitly prohibits"
],
"status": "INVALID",
"summary": "The document is invalid as a cohesive governance document because it contains conflicting policies that cannot be simultaneously applied."
},
"prompt_2": {
"evidence": [],
"explanation": "The document contains policy terms and years but does not mention specific technologies, tools, or protocols by name.",
"references": []
},
"prompt_4": {
"evidence": [
"The 2010 enterprise governance policy requires all regulated teams to maintain written operational controls",
"Any deletion of regulated records before the seven-year retention period is prohibited unless explicitly approved by the central compliance office"
],
"status": "OBSOLETE_PRACTICE",
"summary": "The 2010 operational procedure regarding deletion approval is superseded by the 2024 regional exception which allows local approval, marking the older practice as obsolete in the conflict context."
},
"prompt_6": {
"evidence": [
"seven-year retention period",
"central compliance office",
"regional exception register",
"active operations"
],
"scores": {
"operational": 8,
"regulatory": 6,
"technical": 3
},
"summary": "Scores reflect the high operational focus on deletion timelines, moderate regulatory conflict between policies, and lower technical specificity regarding governance tools."
},
"prompt_9": {
"evidence": [
"The 2024 regional exception policy allows local deletion after three years with only regional approval",
"A regional exception alone is not sufficient to override enterprise retention requirements for regulated records"
],
"status": "MAJOR_ANOMALY",
"summary": "A major anomaly exists where the 2024 policy permits actions explicitly prohibited by the 2010 enterprise baseline."
}
},
"reg": 6.0,
"score_evidence": [
{
"dimension": "regulatory",
"phrase_from_text": "Any deletion of regulated records before the seven-year retention period is prohibited unless explicitly approved by the central compliance office."
}
],
"summary": "The document describes a conflict between a 2010 seven-year retention policy and a 2024 regional three-year deletion policy.",
"supersedence": [],
"tech": 3.0,
"temporal_signals": [
"2010",
"2024",
"seven-year",
"three-year"
]
}