Document: test1.txt

{
  "badge_class": "score-red",
  "chunk_id": "tmpk8nkx9te_chunk_0000",
  "confidence": 59.58,
  "contextual_qna": [
    {
      "answer": "AES 256 is the minimum acceptable encryption strength.",
      "question": "What is the minimum encryption strength required?"
    },
    {
      "answer": "AES 128 must be phased out immediately as it is considered insecure.",
      "question": "When will AES 128 be phased out?"
    },
    {
      "MERCHANTABILITY": "What is the key rotation frequency?",
      "answer": "Rotation is mandatory every 90 days for certificates, service keys, and tokens."
    },
    {
      "answer": "Automated workflows using centralized KMS tooling are mandatory.",
      "question": "What tools are required for key management?"
    },
    {
      "answer": "HSM support is required for systems containing regulated data.",
      "question": "What is required for systems with regulated data?"
    },
    {
      "answer": "This document replaces all previous encryption guidelines and is the current authoritative standard as of 2024.",
      "question": "When did this document become effective?"
    },
    {
      "answer": "AES 256 is the minimum acceptable encryption strength replacing AES 128.",
      "question": "What is the replacement for AES 128?"
    }
  ],
  "contradictions": [],
  "core_answers": {
    "What is the main idea?": "Enterprise systems must adopt AES 256 encryption, phase out AES 128, and implement automated key management with HSM support for regulated data.",
    "What processes or procedures are described?": "Mandatory key rotation every 90 days, centralized KMS tooling, and certificate/service key/token rotation.",
    "What risks or threats are discussed?": "AES 128 is deemed insecure and poses operational risks if not phased out immediately."
  },
  "decay_score": 0.4042,
  "decay_summary": {
    "anomaly": {
      "evidence": [],
      "status": "NO"
    },
    "archive_suggestion": false,
    "counts": {
      "legacy_indicators": 1,
      "outdated_terms": 1
    },
    "legacy": [
      {
        "label": "AES 128",
        "tag": "OBSOLETE"
      }
    ],
    "outdated_terms": [
      "AES 128"
    ],
    "regulatory_gap": false,
    "regulatory_score": 7,
    "rollup": {
      "text": "1 outdated \u00b7 1 legacy \u00b7 anomaly: no \u00b7 validation: valid \u00b7 reg: 7"
    },
    "severity": "MEDIUM",
    "validation": {
      "reason": "Aligns with best practices for encryption, key management, and rotation policies.",
      "status": "VALID"
    }
  },
  "domain_scores": {
    "operational": 8,
    "regulatory": 9,
    "technical": 9
  },
  "explanation": "This chunk displays 40.42% decay, highlighting critical information degradation. While tech domain strength (10/10) remains intact, ops (9/10) and reg (7/10) domains show erosion. Temporal drift signals \u0027year\u0027 and \u0027version\u0027 indicate versioning but lack explicit supersedence markers. No contradictions exist, but the high decay rate suggests outdated content. Evidence: - item1 - item2 Notes: valid parts include tech domain strengths; decayed parts involve ops/reg weaknesses. Domain scores reflect tech dominance but ops/reg gaps. Temporal signals suggest iterative updates, though no explicit supersedence relationships are documented.",
  "is_archived": false,
  "ops": 9.0,
  "prompt_diagnostics": {
    "prompt_1": {
      "evidence": [
        "AES 256 as the minimum acceptable encryption strength",
        "AES 128 is considered insecure for any operational workload and must be phased out immediately"
      ],
      "explanation": "AES 256 is mandated as current standard, while AES 128 is explicitly labeled outdated.",
      "terms": [
        {
          "category": "CURRENT",
          "term": "AES 256"
        },
        {
          "category": "OUTDATED",
          "term": "AES 128"
        }
      ]
    },
    "prompt_10": {
      "evidence": [
        "AES 256 as the minimum acceptable encryption strength",
        "Key management must follow automated workflows using centralized KMS tooling",
        "Rotation is mandatory every 90 days"
      ],
      "status": "VALID",
      "summary": "Aligns with best practices for encryption, key management, and rotation policies."
    },
    "prompt_2": {
      "evidence": [
        "AES 128 is considered insecure for any operational workload and must be phased out immediately",
        "Key management must follow automated workflows using centralized KMS tooling"
      ],
      "explanation": "AES 128 is obsolete due to insecurity, while KMS tooling is supported as required infrastructure.",
      "references": [
        {
          "category": "OBSOLETE",
          "item": "AES 128"
        },
        {
          "category": "SUPPORTED",
          "item": "KMS tooling"
        }
      ]
    },
    "prompt_4": {
      "evidence": [
        "All enterprise systems must use AES 256 as the minimum acceptable encryption strength",
        "Rotation is mandatory every 90 days and must include certificates service keys and tokens"
      ],
      "status": "STANDARD_PRACTICE",
      "summary": "Standard practices include uniform encryption requirements and mandatory key rotation."
    },
    "prompt_6": {
      "evidence": [
        "AES 256 as the minimum acceptable encryption strength",
        "Rotation is mandatory every 90 days",
        "This document replaces all previous encryption guidelines"
      ],
      "scores": {
        "operational": 9,
        "regulatory": 7,
        "technical": 10
      },
      "summary": "High technical and operational scores due to strong encryption and rotation, moderate regulatory score due to lack of specific compliance references."
    },
    "prompt_9": {
      "evidence": [],
      "status": "NO_ANOMALY",
      "summary": "No inconsistencies detected in the document\u0027s requirements."
    }
  },
  "reg": 7.0,
  "score_evidence": [
    {
      "dimension": "technical",
      "phrase_from_text": "AES 256 as the minimum acceptable encryption strength"
    },
    {
      "dimension": "operational",
      "phrase_from_text": "Rotation is mandatory every 90 days"
    },
    {
      "dimension": "regulatory",
      "phrase_from_text": "HSM support is required for systems containing regulated data"
    }
  ],
  "summary": "This chunk displays 40.42% decay, highlighting critical information degradation. While tech domain strength (10/10) remains intact, ops (9/10) and reg (7/10) domains show erosion. Temporal drift signals \u0027year\u0027 and \u0027version\u0027 indicate versioning but lack explicit supersedence markers. No contradictions exist, but the high decay rate suggests outdated content. Evidence: - item1 - item2 Notes: valid parts include tech domain strengths; decayed parts involve ops/reg weaknesses. Domain scores reflect tech dominance but ops/reg gaps. Temporal signals suggest iterative updates, though no explicit supersedence relationships are documented.",
  "supersedence": [],
  "tech": 10.0,
  "temporal_signals": [
    "year",
    "version"
  ]
}