Chunk Diagnosis

🧠 Diagnosis Results for api_test_doc.txt

📄 Chunk: api_test_doc_chunk_0000

Tech: 7.0 Ops: 5.0 Reg: 2.0 83.0%

Core Answers

What is the main idea?: The document serves as a test for API verification purposes.

Contextual Q&A

What is the purpose of this document?: To serve as a test for API verification.
What type of document is this?: A test document.
What is the main focus of the document?: API verification.
What is the intended use of the document?: API verification testing.
Are there any risks mentioned in the document?: No.
What is the document's role in API verification?: It acts as a test document for verification purposes.

Signs of Decay Severity: LOW

0 outdated · 0 legacy · anomaly: no · validation: valid · reg: 2

Signs

🧭 Validation

VALID

The document aligns with best practices for API verification.

🧪 Regulatory

Regulatory score: 2

LLM Explanation

This chunk displays 17% decay, reflecting partial obsolescence in technical (7/10) and operational (5/10) domains, with regulatory (2/10) content being critically outdated. Temporal drift signals are absent, suggesting no clear time-based context for validity assessment. No contradictions or supersedence detected, but domain scores indicate limited relevance to current practices. Evidence: - item1 - item2 Notes: - valid parts: technical concepts - decayed parts: regulatory framework - domain scores: tech (7) indicates partial relevance, ops (5) and reg (2) show severe obsolescence - temporal signals: none - contradictions/supersedence: none

Validation in Progress

The system is generating a deeper validation summary for this chunk. Please wait…

📥 Export Full Report

Download TXT Download MD Download PDF