Chunk Diagnosis

🧠 Diagnosis Results for canonical_142f4d75

Tech: 0 Ops: 0 Reg: 0 87.79%

Core Answers

What is the main idea?: This document is a test file for evaluating knowledge governance.
What risks or threats are discussed?: The document does not discuss any specific risks or threats.
What processes or procedures are described?: The document outlines the structure required for test document analysis.

Contextual Q&A

What is the purpose of this document?: It serves as a test document for knowledge governance.
Is this a real policy document?: No, it is explicitly labeled as a 'test document'.
Are there any specific guidelines mentioned?: The text contains no specific guidelines beyond the test label.
What is the expected format for this analysis?: A JSON object with specific keys and constraints.
Is this document publicly accessible?: The text does not specify access levels or public status.
What fields are required in the output?: The output must include core_answers, contextual_qna, domain_scores, score_evidence, and temporal_signals.
What are the constraints on the core_answers?: Each answer must be a short, factual sentence of 40 words or fewer.
How are domain_scores defined?: They must be integer values for technical, operational, and regulatory dimensions.

Signs of Decay 🧭 🧪 Severity: MEDIUM

0 outdated · 0 legacy · anomaly: no · validation: uncertain · reg: gap

🧭 Validation

UNCERTAIN

Cannot validate alignment due to lack of content in the provided document chunk.

🧪 Regulatory

LLM Explanation

This document is a test file for evaluating knowledge governance.

Validation in Progress

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

Tech: 5.0 Ops: 8.0 Reg: 6.0 67.29%

Core Answers

What is the main idea?: Production documents require periodic review every 90 days, while those older than 180 days need marking.
What risks or threats are discussed?: Overdue document reviews or unmarked legacy documents may lead to compliance issues.
What processes or procedures are described?: Review all production documents every 90 days and mark legacy documents older than 180 days.

Contextual Q&A

How often must production documents be reviewed?: All production documents must be reviewed every 90 days.
What status should be assigned to documents older than 180 days?: Legacy documents older than 180 days should be marked for review.
What is the time limit for the initial review?: All production documents must be reviewed every 90 days.
What defines a legacy document in this context?: Legacy documents older than 180 days should be marked for review.
What is the specific action required for old documents?: Legacy documents older than 180 days should be marked for review.
What is the maximum time before review is required?: All production documents must be reviewed every 90 days.
What specific wording indicates the need for marking?: Legacy documents older than 180 days should be marked for review.

Signs of Decay 📑 Severity: LOW

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

📑 Legacy practices (2)

Legacy documents (LEGACY-VALID) 180 days (LEGACY-EOL)

🧭 Validation

VALID

The document aligns with best practices by establishing clear review intervals for both active and legacy documents, ensuring no documents exceed a certain age without attention.

🧪 Regulatory

LLM Explanation

Production documents require periodic review every 90 days, while those older than 180 days need marking.

Validation in Progress

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