No technical terminology or specific term classifications (CURRENT, LEGACY-VALID, OUTDATED) were found in the provided document chunk, which only contains metadata about the document's preparation date and audience.
No specific technologies, tools, or protocols were mentioned in the document chunk. It only lists 'Treasury, CFO office, and lenders' observer group' as the audience.
The document chunk is a header containing only administrative details (date, audience, company) and does not describe any operational procedures to assess.
Scores are assigned 0 because the document chunk lacks any substantive content regarding technical, operational, or regulatory details; it is limited to a prepared date of 22 April 2026.
There are no inconsistencies detected because the provided text is a consistent header block with no conflicting data.
The status is VALID because the text is internally consistent and correctly identifies the company as 'Orion Vale Components Ltd. (fictional case company)', indicating the data is coherent, even if it lacks specific substantive claims to validate.
{
"badge_class": "score-green",
"chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f",
"confidence": 84.51,
"contextual_qna": [
{
"answer": "Orion Vale Components Ltd.",
"question": "What is the name of the company?"
},
{
"answer": "22 April 2026",
"question": "When was the document prepared?"
},
{
"answer": "Treasury, CFO office, and lenders\u0027 observer group",
"question": "Who is the intended audience for this document?"
},
{
"answer": "No, the text specifies it is a fictional case company.",
"question": "Is this a real company?"
},
{
"answer": "The text states the document was \u0027Prepared\u0027 but does not specify the type.",
"question": "What type of document was prepared?"
},
{
"answer": "DD Month YYYY",
"question": "What is the date format used?"
}
],
"contradictions": [
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d62a0b81-63d2-5749-9c7e-bbf11e44f17a",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 782,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 783,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "99a29d1a-676e-5b09-a61b-01b5106b0c95",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 784,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "caf11235-8513-5ec6-a552-7d071c19497b",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 785,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "e8db38cd-c6d6-5a2b-987a-19af4622a1d5",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 786,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "2962e8a3-906f-579d-94cc-391d3499a222",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 787,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "ff16ee99-581f-5440-8b55-5b9a3f0277b5",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 788,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "46e07a09-497f-5fa9-bdae-2962bae34bff",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 789,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "3134e86b-2dfc-5718-baf8-40121b25b173",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 790,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 791,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "caf11235-8513-5ec6-a552-7d071c19497b",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 792,
"justification": "No reason provided.",
"question": "Who is the intended audience for this document?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "94670ffa-d5c5-5d59-b29d-8917dd8b76fc",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 793,
"justification": "No reason provided.",
"question": "Who is the intended audience for this document?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "e8db38cd-c6d6-5a2b-987a-19af4622a1d5",
"detected_at": "Tue, 26 May 2026 17:23:57 GMT",
"id": 794,
"justification": "No reason provided.",
"question": "Who is the intended audience for this document?",
"source_chunk_id": "700661ba-2340-54c1-bb78-25996bdaeb0f"
}
],
"core_answers": {
"What is the main idea?": "Orion Vale Components Ltd. submitted prepared documents to Treasury, CFO, and lenders on 22 April 2026.",
"What processes or procedures are described?": "The text describes a document preparation event addressed to specific financial stakeholders.",
"What risks or threats are discussed?": "The provided text contains no discussion of risks, threats, or specific challenges."
},
"decay_score": 0.1549,
"decay_summary": {
"anomaly": {
"evidence": [],
"status": "NO"
},
"archive_suggestion": false,
"counts": {
"legacy_indicators": 0,
"outdated_terms": 0
},
"legacy": [],
"outdated_terms": [],
"regulatory_gap": true,
"regulatory_score": 0,
"rollup": {
"text": "0 outdated \u00b7 0 legacy \u00b7 anomaly: no \u00b7 validation: valid \u00b7 reg: gap"
},
"severity": "MEDIUM",
"validation": {
"reason": "The status is VALID because the text is internally consistent and correctly identifies the company as \u0027Orion Vale Components Ltd. (fictional case company)\u0027, indicating the data is coherent, even if it lacks specific substantive claims to validate.",
"status": "VALID"
}
},
"domain_scores": {
"operational": 0,
"regulatory": 0,
"technical": 0
},
"explanation": "Orion Vale Components Ltd. submitted prepared documents to Treasury, CFO, and lenders on 22 April 2026.",
"is_archived": false,
"ops": 0.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [],
"explanation": "No technical terminology or specific term classifications (CURRENT, LEGACY-VALID, OUTDATED) were found in the provided document chunk, which only contains metadata about the document\u0027s preparation date and audience.",
"terms": []
},
"prompt_10": {
"evidence": [],
"status": "VALID",
"summary": "The status is VALID because the text is internally consistent and correctly identifies the company as \u0027Orion Vale Components Ltd. (fictional case company)\u0027, indicating the data is coherent, even if it lacks specific substantive claims to validate."
},
"prompt_2": {
"evidence": [],
"explanation": "No specific technologies, tools, or protocols were mentioned in the document chunk. It only lists \u0027Treasury, CFO office, and lenders\u0027 observer group\u0027 as the audience.",
"references": []
},
"prompt_4": {
"evidence": [],
"status": "UNCERTAIN",
"summary": "The document chunk is a header containing only administrative details (date, audience, company) and does not describe any operational procedures to assess."
},
"prompt_6": {
"evidence": [],
"scores": {
"operational": 0,
"regulatory": 0,
"technical": 0
},
"summary": "Scores are assigned 0 because the document chunk lacks any substantive content regarding technical, operational, or regulatory details; it is limited to a prepared date of 22 April 2026."
},
"prompt_9": {
"evidence": [],
"status": "NO_ANOMALY",
"summary": "There are no inconsistencies detected because the provided text is a consistent header block with no conflicting data."
}
},
"reg": 0.0,
"score_evidence": [
{
"dimension": "operational",
"phrase_from_text": "Prepared: 22 April 2026"
}
],
"summary": "Orion Vale Components Ltd. submitted prepared documents to Treasury, CFO, and lenders on 22 April 2026.",
"supersedence": [],
"tech": 0.0,
"temporal_signals": [
"year",
"modern"
]
}
FY2025 is the current fiscal year referenced for performance. February 2025 is a past date relative to the March 2026 context, making it legacy but still valid as a historical reference point compared to the superseding October 2025 update.
Both the Board Finance Pack and Credit Committee Update are explicitly stated as superseded documents, rendering them obsolete or legacy-end-of-life relative to the current note.
Current operational procedure requires explaining the timing and cure of any breach, rather than providing a binary yes/no answer.
Scores reflect the nuanced compliance status: technical details are clear (8), regulatory standing is resolved via waiver (7), and operational impact is explained by the necessity of timing explanations (6).
No major inconsistencies found; the document correctly differentiates between historical context (October memo) and current status (March 2026 compliance).
The document aligns with best practices by clearly superseding outdated documents and providing a nuanced explanation of technical breaches and waivers.
{
"badge_class": "score-yellow",
"chunk_id": "31a24665-9a6f-5066-9080-e31b513f0eb2",
"confidence": 70.32,
"contextual_qna": [
{
"answer": "The technical leverage breach occurred at 31 December 2025.",
"question": "When did the technical leverage breach occur?"
},
{
"answer": "The breach was waived on 18 February 2026.",
"question": "When was the leverage breach waived?"
},
{
"answer": "Yes, the company is compliant under the amended facility as of 31 March 2026.",
"question": "Is the company compliant as of 31 March 2026?"
},
{
"answer": "This note supersedes the February 2025 Board Finance Pack for financial metrics.",
"question": "Which document supersedes the February 2025 Board Finance Pack?"
},
{
"answer": "The October memo remains useful for explaining why lender reporting was tightened but should not be treated as the latest answer for covenant compliance.",
"question": "What should be done with the October Credit Committee Update?"
},
{
"answer": "The company is operating under an amended facility with a waived breach condition.",
"question": "What is the current status of the facility terms?"
},
{
"answer": "A system that answers only \u0027no breach\u0027 or only \u0027company breached covenant\u0027 is incomplete unless it explains the timing and cure.",
"question": "Why might a simple yes/no answer be incomplete?"
}
],
"contradictions": [],
"core_answers": {
"What is the main idea?": "Orion Vale waived a technical leverage breach on 18 Feb 2026, remaining compliant as of 31 March 2026 under the amended facility.",
"What processes or procedures are described?": "The document describes lender reporting tightening and the process for waiving covenant breaches in the amended facility terms.",
"What risks or threats are discussed?": "A technical leverage breach occurred at 31 December 2025, which was later waived by the lender on 18 February 2026."
},
"decay_score": 0.2968,
"decay_summary": {
"anomaly": {
"evidence": [
"The October memo remains useful for explaining why lender reporting was tightened, but it should not be treated as the latest answer for whether the company is currently compliant."
],
"status": "NO"
},
"archive_suggestion": false,
"counts": {
"legacy_indicators": 3,
"outdated_terms": 0
},
"legacy": [
{
"label": "FY2025",
"tag": "LEGACY-VALID"
},
{
"label": "Board Finance Pack",
"tag": "OBSOLETE"
},
{
"label": "Credit Committee Update",
"tag": "LEGACY-EOL"
}
],
"outdated_terms": [],
"regulatory_gap": false,
"regulatory_score": 7,
"rollup": {
"text": "0 outdated \u00b7 3 legacy \u00b7 anomaly: no \u00b7 validation: valid \u00b7 reg: 7"
},
"severity": "LOW",
"validation": {
"reason": "The document aligns with best practices by clearly superseding outdated documents and providing a nuanced explanation of technical breaches and waivers.",
"status": "VALID"
}
},
"domain_scores": {
"operational": 1,
"regulatory": 0,
"technical": 1
},
"explanation": "Orion Vale waived a technical leverage breach on 18 Feb 2026, remaining compliant as of 31 March 2026 under the amended facility.",
"is_archived": false,
"ops": 6.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"FY2025",
"February 2025"
],
"explanation": "FY2025 is the current fiscal year referenced for performance. February 2025 is a past date relative to the March 2026 context, making it legacy but still valid as a historical reference point compared to the superseding October 2025 update.",
"terms": [
{
"category": "CURRENT",
"term": "FY2025"
},
{
"category": "LEGACY-VALID",
"term": "FY2025"
}
]
},
"prompt_10": {
"evidence": [
"It supersedes the February 2025 Board Finance Pack for financial metrics",
"It supersedes the October 2025 Credit Committee Update for covenant status and cash action items"
],
"status": "VALID",
"summary": "The document aligns with best practices by clearly superseding outdated documents and providing a nuanced explanation of technical breaches and waivers."
},
"prompt_2": {
"evidence": [
"supersedes the February 2025 Board Finance Pack",
"supersedes the October 2025 Credit Committee Update"
],
"explanation": "Both the Board Finance Pack and Credit Committee Update are explicitly stated as superseded documents, rendering them obsolete or legacy-end-of-life relative to the current note.",
"references": [
{
"category": "OBSOLETE",
"item": "Board Finance Pack"
},
{
"category": "LEGACY-EOL",
"item": "Credit Committee Update"
}
]
},
"prompt_4": {
"evidence": [
"The most important point is nuanced: Orion Vale did experience a technical leverage breach at 31 December 2025, but the breach was waived on 18 February 2026. As of 31 March 2026, the company is compliant under the amended facility. A system that answers only \u0027no breach\u0027 or only \u0027company breached covenant\u0027 is incomplete unless it explains the timing and cure."
],
"status": "STANDARD_PRACTICE",
"summary": "Current operational procedure requires explaining the timing and cure of any breach, rather than providing a binary yes/no answer."
},
"prompt_6": {
"evidence": [
"Orion Vale did experience a technical leverage breach",
"breach was waived on 18 February 2026",
"compliant under the amended facility"
],
"scores": {
"operational": 6,
"regulatory": 7,
"technical": 8
},
"summary": "Scores reflect the nuanced compliance status: technical details are clear (8), regulatory standing is resolved via waiver (7), and operational impact is explained by the necessity of timing explanations (6)."
},
"prompt_9": {
"evidence": [
"The October memo remains useful for explaining why lender reporting was tightened, but it should not be treated as the latest answer for whether the company is currently compliant."
],
"status": "NO_ANOMALY",
"summary": "No major inconsistencies found; the document correctly differentiates between historical context (October memo) and current status (March 2026 compliance)."
}
},
"reg": 7.0,
"score_evidence": [
{
"dimension": "technical",
"phrase_from_text": "Orion Vale did experience a technical leverage breach at 31 December 2025"
},
{
"dimension": "regulatory",
"phrase_from_text": "the breach was waived on 18 February 2026"
}
],
"summary": "Orion Vale waived a technical leverage breach on 18 Feb 2026, remaining compliant as of 31 March 2026 under the amended facility.",
"supersedence": [
{
"detected_at": "Tue, 26 May 2026 17:24:55 GMT",
"id": 1,
"new_chunk_id": "31a24665-9a6f-5066-9080-e31b513f0eb2",
"old_chunk_id": "2962e8a3-906f-579d-94cc-391d3499a222",
"reason": "Updated financial metrics to FY2025 and added critical fact about the technical covenant breach occurring at year-end and being waived, plus context on amended facility terms."
}
],
"tech": 8.0,
"temporal_signals": [
"2025",
"2026",
"February",
"March"
]
}
Terms referencing FY2024 and historical plans are legacy. Terms referencing FY2025 and Q1 2026 are current. Terms referencing February/October 2025 plans are outdated relative to the FY2025 audit.
Atlas repricing is treated as a past event causing prior issues. The waiver mechanism is currently active to resolve the Dec 2025 breach.
Operational procedures rely on historical audit completion and past debt reduction methods, indicating legacy practices rather than updated strategic protocols.
Technical scores reflect modest recovery and compliance. Operational scores are high due to restored liquidity. Regulatory scores are lower due to the reliance on waivers for breach resolution.
A minor anomaly exists between the reported FY2025 EBITDA (AED 52.4m) and the Q1 2026 projection (AED 14.6m), as well as the gap between the audited figure and the excluded February plan (AED 67.8m), which creates inconsistency in performance trajectory.
Alignment with best practices is confirmed as the document explicitly states audited figures are the correct numbers to use, and the company is deemed compliant post-waiver.
{
"badge_class": "score-red",
"chunk_id": "2087af7e-c345-5ad6-8de5-750e7a59c127",
"confidence": 59.32,
"contextual_qna": [
{
"answer": "AED 429.7m",
"question": "What is the audited revenue for FY2025?"
},
{
"answer": "AED 52.4m",
"question": "What is the audited adjusted EBITDA for FY2025?"
},
{
"answer": "Q1 2026 revenue is AED 112.8m while FY2025 was AED 429.7m.",
"question": "How does Q1 2026 revenue compare to FY2025?"
},
{
"answer": "The Dec 2025 breach was waived and the latest position is compliant.",
"question": "What was the company\u0027s position regarding the Dec 2025 breach?"
},
{
"answer": "The Feb 2025 plan was AED 67.8m",
"question": "What was the Feb 2025 plan for Adjusted EBITDA?"
},
{
"answer": "FY2025 net debt was AED 144.9m versus AED 151.8m in FY2024.",
"question": "How did FY2025 net debt compare to FY2024?"
},
{
"answer": "EBITDA recovered in Q1 2026, but remains below the February 2025 plan.",
"question": "What does the current interpretation say about Q1 2026 EBITDA?"
},
{
"answer": "Working-capital release reduced debt after year-end.",
"question": "What caused the reduction in net debt in FY2025?"
}
],
"contradictions": [
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d62a0b81-63d2-5749-9c7e-bbf11e44f17a",
"detected_at": "Tue, 26 May 2026 17:24:55 GMT",
"id": 795,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "2087af7e-c345-5ad6-8de5-750e7a59c127"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:24:55 GMT",
"id": 796,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "2087af7e-c345-5ad6-8de5-750e7a59c127"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "5b28652e-17ba-519d-8bfc-8da2bc0685d4",
"detected_at": "Tue, 26 May 2026 17:24:55 GMT",
"id": 797,
"justification": "No reason provided.",
"question": "What is the audited adjusted EBITDA for FY2025?",
"source_chunk_id": "2087af7e-c345-5ad6-8de5-750e7a59c127"
}
],
"core_answers": {
"What is the main idea?": "FY2025 is audited showing modest revenue growth, a debt breach waiver, and compliant metrics.",
"What processes or procedures are described?": "FY2025 figures were audited and compared against previous forecasts and management plans.",
"What risks or threats are discussed?": "The company faced a Dec 2025 covenant breach which was subsequently waived."
},
"decay_score": 0.4068,
"decay_summary": {
"anomaly": {
"evidence": [
"AED 429.7m",
"AED 67.8m",
"AED 52.4m",
"AED 14.6m",
"AED 59.6m"
],
"status": "MINOR"
},
"archive_suggestion": true,
"counts": {
"legacy_indicators": 3,
"outdated_terms": 3
},
"legacy": [
{
"label": "FY2024 audited",
"tag": "LEGACY-VALID"
},
{
"label": "Atlas repricing",
"tag": "OBSOLETE"
},
{
"label": "Legacy Practice",
"tag": "LEGACY_PRACTICE"
}
],
"outdated_terms": [
"February board pack",
"October credit committee forecast",
"Feb 2025 plan"
],
"regulatory_gap": false,
"regulatory_score": 5,
"rollup": {
"text": "3 outdated \u00b7 3 legacy \u00b7 anomaly: minor \u00b7 validation: valid \u00b7 reg: 5"
},
"severity": "HIGH",
"validation": {
"reason": "Alignment with best practices is confirmed as the document explicitly states audited figures are the correct numbers to use, and the company is deemed compliant post-waiver.",
"status": "VALID"
}
},
"domain_scores": {
"operational": 1,
"regulatory": 1,
"technical": 0
},
"explanation": "FY2025 is audited showing modest revenue growth, a debt breach waiver, and compliant metrics.",
"is_archived": false,
"ops": 7.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"FY2024 audited",
"FY2025 audited",
"Q1 2026 management",
"February board pack",
"October credit committee forecast",
"Dec 2025 breach",
"February 2025 plan"
],
"explanation": "Terms referencing FY2024 and historical plans are legacy. Terms referencing FY2025 and Q1 2026 are current. Terms referencing February/October 2025 plans are outdated relative to the FY2025 audit.",
"terms": [
{
"category": "LEGACY-VALID",
"term": "FY2024 audited"
},
{
"category": "CURRENT",
"term": "FY2025 audited"
},
{
"category": "CURRENT",
"term": "Q1 2026 management"
},
{
"category": "OUTDATED",
"term": "February board pack"
},
{
"category": "OUTDATED",
"term": "October credit committee forecast"
},
{
"category": "CURRENT",
"term": "Dec 2025 breach"
},
{
"category": "OUTDATED",
"term": "Feb 2025 plan"
}
]
},
"prompt_10": {
"evidence": [
"FY2025 has now been audited",
"These are the numbers to use in current answers",
"latest position is compliant",
"Growth is modest but real"
],
"status": "VALID",
"summary": "Alignment with best practices is confirmed as the document explicitly states audited figures are the correct numbers to use, and the company is deemed compliant post-waiver."
},
"prompt_2": {
"evidence": [
"Atlas repricing",
"The Dec 2025 breach was waived"
],
"explanation": "Atlas repricing is treated as a past event causing prior issues. The waiver mechanism is currently active to resolve the Dec 2025 breach.",
"references": [
{
"category": "OBSOLETE",
"item": "Atlas repricing"
},
{
"category": "SUPPORTED",
"item": "waiver"
}
]
},
"prompt_4": {
"evidence": [
"FY2025 has now been audited",
"The company did not collapse after Atlas repricing",
"Working-capital release reduced debt after year-end"
],
"status": "LEGACY_PRACTICE",
"summary": "Operational procedures rely on historical audit completion and past debt reduction methods, indicating legacy practices rather than updated strategic protocols."
},
"prompt_6": {
"evidence": [
"Growth is modest but real",
"EBITDA recovered in Q1 2026",
"The Dec 2025 breach was waived",
"compliant",
"Refinancing and collections restored short-term headroom"
],
"scores": {
"operational": 7,
"regulatory": 5,
"technical": 6
},
"summary": "Technical scores reflect modest recovery and compliance. Operational scores are high due to restored liquidity. Regulatory scores are lower due to the reliance on waivers for breach resolution."
},
"prompt_9": {
"evidence": [
"AED 429.7m",
"AED 67.8m",
"AED 52.4m",
"AED 14.6m",
"AED 59.6m"
],
"status": "MINOR_ANOMALY",
"summary": "A minor anomaly exists between the reported FY2025 EBITDA (AED 52.4m) and the Q1 2026 projection (AED 14.6m), as well as the gap between the audited figure and the excluded February plan (AED 67.8m), which creates inconsistency in performance trajectory."
}
},
"reg": 5.0,
"score_evidence": [
{
"dimension": "regulatory",
"phrase_from_text": "The Dec 2025 breach was waived; latest position is compliant."
},
{
"dimension": "operational",
"phrase_from_text": "Working-capital release reduced debt after year-end."
}
],
"summary": "FY2025 is audited showing modest revenue growth, a debt breach waiver, and compliant metrics.",
"supersedence": [
{
"detected_at": "Tue, 26 May 2026 17:25:27 GMT",
"id": 2,
"new_chunk_id": "2087af7e-c345-5ad6-8de5-750e7a59c127",
"old_chunk_id": "caf11235-8513-5ec6-a552-7d071c19497b",
"reason": "Replaced projected/management-close numbers with actual audited FY2025 results and Q1 2026 data; updated financial metric values (Revenue, EBITDA, Debt) and corrected the FY2025 EBITDA from the older February forecast of AED 67.8m to AED 52.4m."
}
],
"tech": 6.0,
"temporal_signals": [
"year",
"version",
"legacy"
]
}
The term 'adjusted EBITDA' appears in the original threshold context, while the amended covenant uses 'net debt / EBITDA' directly.
No specific technologies, tools, or protocols are mentioned in the text.
The document describes a covenant amendment process triggered by a technical breach and subsequent waiver, but does not explicitly describe operational procedures to assess as standard or legacy.
Scores are assigned based on qualitative analysis of the text. The regulatory score is high due to specific covenant terms and thresholds.
While the text shows a progression from a 2.75x threshold to a 2.85x cap, this is a standard covenant amendment sequence rather than an inconsistency or anomaly.
The waiver of a technical breach following met conditions aligns with standard lending practices for covenant waivers.
{
"badge_class": "score-green",
"chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a",
"confidence": 85.94,
"contextual_qna": [
{
"answer": "The original threshold was 2.75x.",
"question": "What was the original net debt threshold?"
},
{
"answer": "The audited year-end ratio was 2.77x.",
"question": "What was the audited year-end ratio?"
},
{
"answer": "The lenders issued a waiver on 18 February 2026.",
"question": "On what date was the waiver issued?"
},
{
"answer": "The AED 9.6m public-sector receivable cleared.",
"question": "What was the first condition for the waiver?"
},
{
"answer": "The NorthDock full-capacity procurement orders were cancelled before deposit lock-in.",
"question": "What was the second condition for the waiver?"
},
{
"answer": "The company agreed to a temporary quarterly reporting package through March 2027.",
"question": "What was the third condition for the waiver?"
},
{
"answer": "The amended covenant allows net debt / EBITDA up to 2.85x through Q2 2026.",
"question": "What is the amended covenant limit for Q2 2026?"
},
{
"answer": "At 31 March 2026, Orion Vale\u0027s ratio was 2.63x.",
"question": "What was the company\u0027s ratio at 31 March 2026?"
}
],
"contradictions": [
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d62a0b81-63d2-5749-9c7e-bbf11e44f17a",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 798,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 799,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "99a29d1a-676e-5b09-a61b-01b5106b0c95",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 800,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "e8db38cd-c6d6-5a2b-987a-19af4622a1d5",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 801,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "37025f22-da61-5bbf-933d-2b8797d2ad13",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 802,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "f2a9f1fd-0823-5ff8-a378-7ec914665e27",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 803,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d0fc537f-80c6-5216-895f-61ee9ea93230",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 804,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "ff16ee99-581f-5440-8b55-5b9a3f0277b5",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 805,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "46e07a09-497f-5fa9-bdae-2962bae34bff",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 806,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "3134e86b-2dfc-5718-baf8-40121b25b173",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 807,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:25:28 GMT",
"id": 808,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a"
}
],
"core_answers": {
"What is the main idea?": "A company waived a net debt covenant breach after meeting three specific conditions to regain compliance.",
"What processes or procedures are described?": "Lenders issued a waiver after conditions were met and approved an amended covenant structure.",
"What risks or threats are discussed?": "The risk of covenant breach due to missing the 2.75x net debt to adjusted EBITDA threshold."
},
"decay_score": 0.1406,
"decay_summary": {
"anomaly": {
"evidence": [],
"status": "NO"
},
"archive_suggestion": false,
"counts": {
"legacy_indicators": 1,
"outdated_terms": 0
},
"legacy": [
{
"label": "net debt / adjusted EBITDA",
"tag": "LEGACY-VALID"
}
],
"outdated_terms": [],
"regulatory_gap": false,
"regulatory_score": null,
"rollup": {
"text": "0 outdated \u00b7 1 legacy \u00b7 anomaly: no \u00b7 validation: valid \u00b7 reg: \u2014"
},
"severity": "LOW",
"validation": {
"reason": "The waiver of a technical breach following met conditions aligns with standard lending practices for covenant waivers.",
"status": "VALID"
}
},
"domain_scores": {
"operational": 0,
"regulatory": 0,
"technical": 1
},
"explanation": "A company waived a net debt covenant breach after meeting three specific conditions to regain compliance.",
"is_archived": false,
"ops": 0.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"The original threshold was 2.75x and the audited year-end ratio was 2.77x",
"The amended covenant for 2026 allows net debt / EBITDA up to 2.85x"
],
"explanation": "The term \u0027adjusted EBITDA\u0027 appears in the original threshold context, while the amended covenant uses \u0027net debt / EBITDA\u0027 directly.",
"status": "complete",
"terms": [
{
"category": "LEGACY-VALID",
"term": "net debt / adjusted EBITDA"
},
{
"category": "CURRENT",
"term": "net debt / EBITDA"
}
]
},
"prompt_10": {
"evidence": [],
"status": "complete",
"summary": "The waiver of a technical breach following met conditions aligns with standard lending practices for covenant waivers."
},
"prompt_2": {
"evidence": [],
"explanation": "No specific technologies, tools, or protocols are mentioned in the text.",
"references": [],
"status": "complete"
},
"prompt_4": {
"evidence": [],
"status": "complete",
"summary": "The document describes a covenant amendment process triggered by a technical breach and subsequent waiver, but does not explicitly describe operational procedures to assess as standard or legacy."
},
"prompt_6": {
"evidence": [],
"status": "complete",
"summary": "Scores are assigned based on qualitative analysis of the text. The regulatory score is high due to specific covenant terms and thresholds."
},
"prompt_9": {
"evidence": [],
"status": "complete",
"summary": "While the text shows a progression from a 2.75x threshold to a 2.85x cap, this is a standard covenant amendment sequence rather than an inconsistency or anomaly."
}
},
"reg": 0.0,
"score_evidence": [
{
"dimension": "technical",
"phrase_from_text": "the company missed the original net debt / adjusted EBITDA threshold"
}
],
"summary": "A company waived a net debt covenant breach after meeting three specific conditions to regain compliance.",
"supersedence": [
{
"detected_at": "Tue, 26 May 2026 17:25:55 GMT",
"id": 3,
"new_chunk_id": "b549b5cd-68f0-5252-ac7b-34f21abd1b9a",
"old_chunk_id": "2962e8a3-906f-579d-94cc-391d3499a222",
"reason": "The new version states a breach of the 2.75x threshold occurred at year-end 2025, which was subsequently waived and amended, whereas the old version incorrectly claimed the covenant status was comfortable and assumed no material audit adjustments."
}
],
"tech": 0.0,
"temporal_signals": [
"year",
"version"
]
}
The text explicitly states the arrangement is 'no longer' take-or-pay and defines the current structure as a volume-band arrangement with rebates.
Atlas Metro is the subject of the current valid contract. The October stress value is identified as an earlier assumption that has been replaced.
Recognition against shipments and earned rebates aligns with current standard accounting practices for volume-based contracts, avoiding fixed floor assumptions.
Scores reflect clear financial data (technical), specific contractual notice requirements (operational), and standard accounting guidance (regulatory).
A minor anomaly exists regarding the timeline; the side letter is dated March 2026, which implies the document is written from a future perspective or contains a date inconsistency relative to current reality.
The alignment is valid because the document clearly redefines the contract terms from an outdated take-or-pay model to a more standard volume-band structure with conditional rebates.
{
"badge_class": "score-yellow",
"chunk_id": "bc499868-af2b-522f-b562-054c7c1c0c9a",
"confidence": 70.51,
"contextual_qna": [
{
"answer": "No, it is no longer a five-year take-or-pay contract.",
"question": "Is the Atlas Metro contract still a take-or-pay agreement?"
},
{
"answer": "It is a three-year volume band arrangement with rebate incentives.",
"question": "What type of contract arrangement does the Atlas Metro deal involve?"
},
{
"answer": "The customer must give nine months\u0027 notice before moving below the lower band.",
"question": "How long must the customer provide notice to reduce their volume?"
},
{
"answer": "The current planning value is AED 118.0m over three years.",
"question": "What is the current planning value for the Atlas Metro relationship?"
},
{
"answer": "The earlier take-or-pay assumption was AED 165.0m.",
"question": "What was the previous take-or-pay value used?"
},
{
"answer": "The October stress value was AED 102.0m.",
"question": "What is the stress value from October?"
},
{
"answer": "Revenue should be recognized against shipments and earned service rebates, not against a fixed minimum volume floor.",
"question": "How should revenue be recognized for this contract?"
},
{
"answer": "The final side letter signed in March 2026 establishes the current terms.",
"question": "What specific side letter established the current terms?"
}
],
"contradictions": [],
"core_answers": {
"What is the main idea?": "The Atlas Metro contract is a three-year volume band arrangement with service rebates, not a take-or-pay contract.",
"What processes or procedures are described?": "Revenue is recognized against shipments and earned rebates, requiring nine months\u0027 notice for volume adjustments.",
"What risks or threats are discussed?": "There are no major threats, though the customer requires nine months\u0027 notice to move below the volume band."
},
"decay_score": 0.2949,
"decay_summary": {
"anomaly": {
"evidence": [
"The final side letter signed in March 2026",
"October AED 102.0m stress value"
],
"status": "MINOR"
},
"archive_suggestion": false,
"counts": {
"legacy_indicators": 0,
"outdated_terms": 0
},
"legacy": [],
"outdated_terms": [],
"regulatory_gap": false,
"regulatory_score": 6,
"rollup": {
"text": "0 outdated \u00b7 0 legacy \u00b7 anomaly: minor \u00b7 validation: valid \u00b7 reg: 6"
},
"severity": "MEDIUM",
"validation": {
"reason": "The alignment is valid because the document clearly redefines the contract terms from an outdated take-or-pay model to a more standard volume-band structure with conditional rebates.",
"status": "VALID"
}
},
"domain_scores": {
"operational": 1,
"regulatory": 0,
"technical": 0
},
"explanation": "The Atlas Metro contract is a three-year volume band arrangement with service rebates, not a take-or-pay contract.",
"is_archived": false,
"ops": 9.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"The Atlas Metro arrangement is no longer a five-year take-or-pay contract",
"It is a lower-commitment volume-band arrangement with service rebates"
],
"explanation": "The text explicitly states the arrangement is \u0027no longer\u0027 take-or-pay and defines the current structure as a volume-band arrangement with rebates.",
"status": {
"terms": [
{
"category": "OUTDATED",
"term": "take-or-pay"
},
{
"category": "CURRENT",
"term": "volume-band arrangement"
},
{
"category": "CURRENT",
"term": "service rebates"
}
]
}
},
"prompt_10": {
"evidence": [
"Current planning value for the Atlas Metro relationship is AED 118.0m over three years",
"It is a lower-commitment volume-band arrangement with service rebates"
],
"status": "VALID",
"summary": "The alignment is valid because the document clearly redefines the contract terms from an outdated take-or-pay model to a more standard volume-band structure with conditional rebates."
},
"prompt_2": {
"evidence": [
"The Atlas Metro arrangement",
"October AED 102.0m stress value"
],
"explanation": "Atlas Metro is the subject of the current valid contract. The October stress value is identified as an earlier assumption that has been replaced.",
"status": {
"references": [
{
"category": "SUPPORTED",
"item": "Atlas Metro"
},
{
"category": "OBSOLETE",
"item": "October stress value"
}
]
}
},
"prompt_4": {
"evidence": [
"Revenue should be recognized against shipments and earned service rebates, not against a fixed minimum volume floor",
"Minimum guaranteed volume is lower than the original board case"
],
"status": {
"status": "STANDARD_PRACTICE"
},
"summary": "Recognition against shipments and earned rebates aligns with current standard accounting practices for volume-based contracts, avoiding fixed floor assumptions."
},
"prompt_6": {
"evidence": [
"AED 118.0m over three years",
"nine months\u0027 notice",
"Revenue should be recognized against shipments"
],
"scores": {
"operational": 9,
"regulatory": 6,
"technical": 8
},
"summary": "Scores reflect clear financial data (technical), specific contractual notice requirements (operational), and standard accounting guidance (regulatory)."
},
"prompt_9": {
"evidence": [
"The final side letter signed in March 2026",
"October AED 102.0m stress value"
],
"status": "MINOR_ANOMALY",
"summary": "A minor anomaly exists regarding the timeline; the side letter is dated March 2026, which implies the document is written from a future perspective or contains a date inconsistency relative to current reality."
}
},
"reg": 6.0,
"score_evidence": [
{
"dimension": "operational",
"phrase_from_text": "The Atlas Metro arrangement is no longer a five-year take-or-pay contract."
}
],
"summary": "The Atlas Metro contract is a three-year volume band arrangement with service rebates, not a take-or-pay contract.",
"supersedence": [
{
"detected_at": "Tue, 26 May 2026 17:26:24 GMT",
"id": 4,
"new_chunk_id": "bc499868-af2b-522f-b562-054c7c1c0c9a",
"old_chunk_id": "b86e44e3-3e2a-5d13-a678-90fe9cced6f0",
"reason": "The new version clarifies that the Atlas Metro arrangement is no longer a take-or-pay contract (replaced by a three-year volume band), updates the planning value from AED 165.0m to AED 118.0m, and corrects the revenue recognition method."
}
],
"tech": 8.0,
"temporal_signals": [
"year",
"version",
"modern"
]
}
Terms are categorized based on their current applicability and presence in the text. 'Safety and reliability' refers to active work, while 'full expansion' describes the historical plan and 'cancelled' is explicitly advised against.
No specific technologies, tools, or protocols (e.g., software versions, specific machinery brands beyond 'machining cell' which is too generic without a brand) are explicitly classified as supported or obsolete. 'Machining cell', 'compact powder-coat line', 'compressed-air monitoring', 'high-failure coolant pumps', and 'compact drive module' are described as items to be inspected, deferred, or monitored but lack explicit EOL/OB markers in this text.
The resumed scope includes standard industrial safety protocols like machine guarding and automated inspection.
Scores reflect the detail of operational conditions (9), the specificity of technical thresholds (8), and the relative ambiguity of the regulatory status of the pause (5).
A minor anomaly exists in the apparent contradiction between stating the expansion is paused while management has 'restarted' a specific scope, clarified by the text distinguishing the two plans.
The document aligns with best practices by clearly separating ongoing safety work from deferred expansion conditions and defining clear financial triggers for the next phase.
{
"badge_class": "score-yellow",
"chunk_id": "7614b089-d2f4-58a2-b00b-1f9c57d3fc2d",
"confidence": 61.14,
"contextual_qna": [
{
"answer": "The full NorthDock expansion remains paused with safety and reliability work restarted.",
"question": "What is the current status of the NorthDock expansion?"
},
{
"answer": "The current approved 2026 NorthDock budget is AED 17.0m.",
"question": "What is the current approved budget for the scope?"
},
{
"answer": "It is not the same as the February 2025 full expansion plan.",
"question": "How does the current situation differ from the February 2025 plan?"
},
{
"answer": "Net debt / EBITDA below 2.35x, Atlas Metro call-offs exceed AED 11.0m, and warranty claims stay below 1.8%.",
"question": "What three conditions must be met before deferred items resume?"
},
{
"answer": "Tasks include machine guarding, automated inspection, compressed-air monitoring, and replacing two high-failure coolant pumps.",
"question": "Which specific safety tasks are currently active?"
},
{
"answer": "Current management language should not describe NorthDock as cancelled.",
"question": "Is the full expansion considered cancelled?"
},
{
"answer": "The work includes replacement of two high-failure coolant pumps.",
"question": "Which machinery replacement involves high-failure pumps?"
}
],
"contradictions": [
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:26:24 GMT",
"id": 809,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "7614b089-d2f4-58a2-b00b-1f9c57d3fc2d"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "e8db38cd-c6d6-5a2b-987a-19af4622a1d5",
"detected_at": "Tue, 26 May 2026 17:26:24 GMT",
"id": 810,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "7614b089-d2f4-58a2-b00b-1f9c57d3fc2d"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "ff16ee99-581f-5440-8b55-5b9a3f0277b5",
"detected_at": "Tue, 26 May 2026 17:26:24 GMT",
"id": 811,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "7614b089-d2f4-58a2-b00b-1f9c57d3fc2d"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "46e07a09-497f-5fa9-bdae-2962bae34bff",
"detected_at": "Tue, 26 May 2026 17:26:24 GMT",
"id": 812,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "7614b089-d2f4-58a2-b00b-1f9c57d3fc2d"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "3134e86b-2dfc-5718-baf8-40121b25b173",
"detected_at": "Tue, 26 May 2026 17:26:24 GMT",
"id": 813,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "7614b089-d2f4-58a2-b00b-1f9c57d3fc2d"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:26:24 GMT",
"id": 814,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "7614b089-d2f4-58a2-b00b-1f9c57d3fc2d"
}
],
"core_answers": {
"What is the main idea?": "NorthDock expansion is paused with only safety and reliability work proceeding under an AED 17.0m budget.",
"What processes or procedures are described?": "Management is executing machine guarding, automated inspection, and coolant pump replacements under a reduced budget.",
"What risks or threats are discussed?": "Future expansion remains deferred until debt ratios, call-offs, and warranty claims meet specific thresholds."
},
"decay_score": 0.3886,
"decay_summary": {
"anomaly": {
"evidence": [
"The full NorthDock expansion remains paused",
"Management has restarted only the safety and reliability scope",
"This is not the same as the February 2025 full expansion plan"
],
"status": "MINOR"
},
"archive_suggestion": false,
"counts": {
"legacy_indicators": 1,
"outdated_terms": 1
},
"legacy": [
{
"label": "safety and reliability",
"tag": "LEGACY-VALID"
}
],
"outdated_terms": [
"cancelled"
],
"regulatory_gap": false,
"regulatory_score": 5,
"rollup": {
"text": "1 outdated \u00b7 1 legacy \u00b7 anomaly: minor \u00b7 validation: valid \u00b7 reg: 5"
},
"severity": "MEDIUM",
"validation": {
"reason": "The document aligns with best practices by clearly separating ongoing safety work from deferred expansion conditions and defining clear financial triggers for the next phase.",
"status": "VALID"
}
},
"domain_scores": {
"operational": 0,
"regulatory": 0,
"technical": 1
},
"explanation": "NorthDock expansion is paused with only safety and reliability work proceeding under an AED 17.0m budget.",
"is_archived": false,
"ops": 9.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"Management has restarted only the safety and reliability scope",
"This is not the same as the February 2025 full expansion plan",
"Current management language should not describe NorthDock as cancelled"
],
"explanation": "Terms are categorized based on their current applicability and presence in the text. \u0027Safety and reliability\u0027 refers to active work, while \u0027full expansion\u0027 describes the historical plan and \u0027cancelled\u0027 is explicitly advised against.",
"terms": [
{
"category": "LEGACY-VALID",
"term": "safety and reliability"
},
{
"category": "CURRENT",
"term": "full expansion"
},
{
"category": "OUTDATED",
"term": "cancelled"
}
]
},
"prompt_10": {
"evidence": [
"management has restarted only the safety and reliability scope",
"The second machining cell and compact powder-coat line remain deferred until three conditions are satisfied",
"net debt / EBITDA is below 2.35x for two consecutive quarters"
],
"status": "VALID",
"summary": "The document aligns with best practices by clearly separating ongoing safety work from deferred expansion conditions and defining clear financial triggers for the next phase."
},
"prompt_2": {
"evidence": [],
"explanation": "No specific technologies, tools, or protocols (e.g., software versions, specific machinery brands beyond \u0027machining cell\u0027 which is too generic without a brand) are explicitly classified as supported or obsolete. \u0027Machining cell\u0027, \u0027compact powder-coat line\u0027, \u0027compressed-air monitoring\u0027, \u0027high-failure coolant pumps\u0027, and \u0027compact drive module\u0027 are described as items to be inspected, deferred, or monitored but lack explicit EOL/OB markers in this text.",
"references": []
},
"prompt_4": {
"evidence": [
"machine guarding",
"automated inspection",
"compressed-air monitoring"
],
"status": "STANDARD_PRACTICE",
"summary": "The resumed scope includes standard industrial safety protocols like machine guarding and automated inspection."
},
"prompt_6": {
"evidence": [
"net debt / EBITDA is below 2.35x for two consecutive quarters",
"Atlas Metro quarterly call-offs exceed AED 11.0m for two consecutive quarters",
"warranty claims on the compact drive module remain below 1.8% of shipments"
],
"scores": {
"operational": 9,
"regulatory": 5,
"technical": 8
},
"summary": "Scores reflect the detail of operational conditions (9), the specificity of technical thresholds (8), and the relative ambiguity of the regulatory status of the pause (5)."
},
"prompt_9": {
"evidence": [
"The full NorthDock expansion remains paused",
"Management has restarted only the safety and reliability scope",
"This is not the same as the February 2025 full expansion plan"
],
"status": "MINOR_ANOMALY",
"summary": "A minor anomaly exists in the apparent contradiction between stating the expansion is paused while management has \u0027restarted\u0027 a specific scope, clarified by the text distinguishing the two plans."
}
},
"reg": 5.0,
"score_evidence": [
{
"dimension": "technical",
"phrase_from_text": "replacement of two high-failure coolant pumps"
}
],
"summary": "NorthDock expansion is paused with only safety and reliability work proceeding under an AED 17.0m budget.",
"supersedence": [
{
"detected_at": "Tue, 26 May 2026 17:26:53 GMT",
"id": 5,
"new_chunk_id": "7614b089-d2f4-58a2-b00b-1f9c57d3fc2d",
"old_chunk_id": "b5ecfd46-a0f2-5a4c-8099-cd7cbee4e2ec",
"reason": "The project status changed from \u0027approved\u0027 to \u0027paused\u0027, the Capex budget was reduced from AED 54.0m to AED 17.0m, and three specific financial and operational thresholds (debt/EBITDA ratio, Atlas Metro volumes, and warranty claims) were added as prerequisites for resuming the deferred elements (machining cell and powder-coat line)."
}
],
"tech": 8.0,
"temporal_signals": [
"year",
"version"
]
}
Compact-drive is marked as obsolete due to irreparable state, while 'retrofit' is treated as a legacy but valid term regarding customer status.
Both references are associated with improvements in receivable days and are currently operational.
Operational procedure requires confirming structural improvements over two quarters before presentation, indicating a cautious standard practice.
High operational relevance due to specific revenue metrics; lower technical score reflects unclear reworkability; moderate regulatory due to audit implications.
Minor anomaly identified where 'improvement' is described as real but not yet structural, creating a potential discrepancy in reporting expectations.
The document aligns with best practices by cautioning against overstating interim structural changes based on incomplete data.
{
"badge_class": "score-yellow",
"chunk_id": "2ae9eed1-dee7-576b-b011-af4a25692628",
"confidence": 67.93,
"contextual_qna": [
{
"answer": "AED 11.9m.",
"question": "What is the total inventory impairment for FY2024 and FY2025?"
},
{
"answer": "AED 8.7m.",
"question": "What was the post-audit impairment amount?"
},
{
"answer": "AED 3.2m.",
"question": "What was the charge amount for compact-drive parts?"
},
{
"answer": "Older aluminum subframe components.",
"question": "In which component is the remaining inventory risk concentrated?"
},
{
"answer": "They improved from 78 days to 63 days.",
"question": "How did receivable days change from 30 September 2025 to 31 March 2026?"
},
{
"answer": "The public sector and two retrofit customers.",
"question": "Which customer types contributed to the cash improvement?"
},
{
"answer": "The next two quarters must confirm the improvement.",
"question": "What condition must be met before calling the cash improvement structural?"
},
{
"answer": "After the FY2024 audit.",
"question": "When was the post-audit impairment recognized?"
}
],
"contradictions": [
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:26:54 GMT",
"id": 815,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "2ae9eed1-dee7-576b-b011-af4a25692628"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "e8db38cd-c6d6-5a2b-987a-19af4622a1d5",
"detected_at": "Tue, 26 May 2026 17:26:54 GMT",
"id": 816,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "2ae9eed1-dee7-576b-b011-af4a25692628"
}
],
"core_answers": {
"What is the main idea?": "Total inventory impairment of 11.9m includes post-audit charges and concentrated risk in aluminum subframes.",
"What processes or procedures are described?": "Receivable days improved due to public-sector collection and revised payment calendars with customers.",
"What risks or threats are discussed?": "Inventory risk is concentrated in older aluminum subframe components that pose financial loss risks."
},
"decay_score": 0.3207,
"decay_summary": {
"anomaly": {
"evidence": [
"The cash improvement is real, but management should not present it as structural until the next two quarters confirm it."
],
"status": "NO"
},
"archive_suggestion": false,
"counts": {
"legacy_indicators": 1,
"outdated_terms": 1
},
"legacy": [
{
"label": "retrofit",
"tag": "LEGACY-VALID"
}
],
"outdated_terms": [
"compact-drive"
],
"regulatory_gap": false,
"regulatory_score": 5,
"rollup": {
"text": "1 outdated \u00b7 1 legacy \u00b7 anomaly: no \u00b7 validation: valid \u00b7 reg: 5"
},
"severity": "MEDIUM",
"validation": {
"reason": "The document aligns with best practices by cautioning against overstating interim structural changes based on incomplete data.",
"status": "VALID"
}
},
"domain_scores": {
"operational": 1,
"regulatory": 0,
"technical": 1
},
"explanation": "Total inventory impairment of 11.9m includes post-audit charges and concentrated risk in aluminum subframes.",
"is_archived": false,
"ops": 8.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"compact-drive parts that cannot be economically reworked",
"two retrofit customers"
],
"explanation": "Compact-drive is marked as obsolete due to irreparable state, while \u0027retrofit\u0027 is treated as a legacy but valid term regarding customer status.",
"status": "completed",
"terms": [
{
"category": "OUTDATED",
"term": "compact-drive"
},
{
"category": "LEGACY-VALID",
"term": "retrofit"
}
]
},
"prompt_10": {
"evidence": [
"management should not present it as structural until the next two quarters confirm it"
],
"status": "completed",
"summary": "The document aligns with best practices by cautioning against overstating interim structural changes based on incomplete data."
},
"prompt_2": {
"evidence": [
"public-sector collection",
"revised payment calendar"
],
"explanation": "Both references are associated with improvements in receivable days and are currently operational.",
"references": [
{
"category": "SUPPORTED",
"item": "public-sector collection"
},
{
"category": "SUPPORTED",
"item": "revised payment calendar"
}
],
"status": "completed"
},
"prompt_4": {
"evidence": [
"The cash improvement is real, but management should not present it as structural until the next two quarters confirm it."
],
"status": "completed",
"summary": "Operational procedure requires confirming structural improvements over two quarters before presentation, indicating a cautious standard practice."
},
"prompt_6": {
"evidence": [
"The total inventory impairment recorded across FY2024 and FY2025 is AED 11.9m",
"Receivable days improved from 78 days at 30 September 2025 to 63 days at 31 March 2026"
],
"scores": {
"operational": 8,
"regulatory": 5,
"technical": 7
},
"status": "completed",
"summary": "High operational relevance due to specific revenue metrics; lower technical score reflects unclear reworkability; moderate regulatory due to audit implications."
},
"prompt_9": {
"evidence": [
"The cash improvement is real, but management should not present it as structural until the next two quarters confirm it."
],
"status": "completed",
"summary": "Minor anomaly identified where \u0027improvement\u0027 is described as real but not yet structural, creating a potential discrepancy in reporting expectations."
}
},
"reg": 5.0,
"score_evidence": [
{
"dimension": "technical",
"phrase_from_text": "older aluminum subframe components"
},
{
"dimension": "operational",
"phrase_from_text": "public-sector collection"
}
],
"summary": "Total inventory impairment of 11.9m includes post-audit charges and concentrated risk in aluminum subframes.",
"supersedence": [],
"tech": 7.0,
"temporal_signals": [
"year",
"version",
"modern"
]
}
Terms related to current and future fiscal periods (Q4 2026) are marked CURRENT. References to past dates (Q3 2025) and the 'February 2025 idea' are marked OUTDATED. Technical financial ratios and currency amounts are marked LEGACY-VALID as they define the future criteria.
The document mentions a financial metric 'net debt / EBITDA', which is a standard business calculation rather than a specific software or hardware technology. Therefore, no specific technology tools or protocols are found to classify as SUPPORTED, LEGACY-EOL, or OBSOLETE.
The requirement to maintain specific liquidity levels post-distribution is a standard financial governance practice.
Clear, quantitative thresholds provide strong operational, technical, and regulatory alignment with best practices.
There are no contradictions. The document consistently states that past dividend ideas are obsolete and the base case assumes no distribution, despite mentioning a hypothetical 'symbolic' discussion.
The policy is clear, specific, and aligns with prudent financial management best practices.
{
"badge_class": "score-red",
"chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132",
"confidence": 46.22,
"contextual_qna": [
{
"answer": "No dividend should be paid before Q4 2026.",
"question": "When should dividends not be paid according to the text?"
},
{
"answer": "Net debt / EBITDA must be below 2.30x.",
"question": "What financial ratio must be met to consider a dividend in Q4 2026?"
},
{
"answer": "Liquidity must remain above AED 35.0m.",
"question": "What liquidity level must remain after the distribution?"
},
{
"answer": "The February 2025 idea of a Q3 2025 dividend is obsolete.",
"question": "What is the status of the February 2025 idea about a Q3 2025 dividend?"
},
{
"answer": "The board may discuss a symbolic distribution in late 2026.",
"question": "Can the board discuss a dividend in late 2026?"
},
{
"answer": "Treasury\u0027s recommended base case assumes no shareholder distribution in FY2026.",
"question": "What is treasury\u0027s base case for shareholder distributions in FY2026?"
},
{
"answer": "The text specifies Q4 2026 as the earliest consideration date.",
"question": "What is the specific timing mentioned for Q4 2026?"
},
{
"answer": "Conditions include net debt / EBITDA below 2.30x and liquidity above AED 35.0m.",
"question": "What conditions are required even in Q4 2026?"
}
],
"contradictions": [
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d62a0b81-63d2-5749-9c7e-bbf11e44f17a",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 817,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 818,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "99a29d1a-676e-5b09-a61b-01b5106b0c95",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 819,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "caf11235-8513-5ec6-a552-7d071c19497b",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 820,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "e8db38cd-c6d6-5a2b-987a-19af4622a1d5",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 821,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "8a8a3636-0fb7-50d9-97a5-0a71934164cf",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 822,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "37025f22-da61-5bbf-933d-2b8797d2ad13",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 823,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "430d8bb2-90ef-5567-bb8f-021409b30e6a",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 824,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "f2a9f1fd-0823-5ff8-a378-7ec914665e27",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 825,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d0fc537f-80c6-5216-895f-61ee9ea93230",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 826,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "6bc62eb1-b875-5609-bb65-edf39310d745",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 827,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "db9322ab-9bcb-538d-af5d-6a8359641174",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 828,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9ce2663a-766b-51e9-9a39-be9565a0230f",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 829,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "88d967cb-ecb4-5bd1-8fc4-2d810ac728c9",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 830,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "ff16ee99-581f-5440-8b55-5b9a3f0277b5",
"detected_at": "Tue, 26 May 2026 17:27:20 GMT",
"id": 831,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132"
}
],
"core_answers": {
"What is the main idea?": "Dividends should not be paid before Q4 2026, and even then only if net debt/EBITDA is under 2.30x and liquidity exceeds AED 35.0m.",
"What processes or procedures are described?": "The board may discuss symbolic distributions in late 2026, while treasury assumes no distribution in FY2026.",
"What risks or threats are discussed?": "Risk includes paying dividends before meeting financial conditions or if liquidity drops below AED 35.0m after distribution."
},
"decay_score": 0.5378,
"decay_summary": {
"anomaly": {
"evidence": [
"\"The February 2025 idea of a Q3 2025 dividend is obsolete\"",
"\"treasury\u0027s recommended base case assumes no shareholder distribution in FY2026\""
],
"status": "NO"
},
"archive_suggestion": false,
"counts": {
"legacy_indicators": 3,
"outdated_terms": 2
},
"legacy": [
{
"label": "FY2026",
"tag": "LEGACY-VALID"
},
{
"label": "net debt / EBITDA",
"tag": "LEGACY-VALID"
},
{
"label": "AED 35.0m",
"tag": "LEGACY-VALID"
}
],
"outdated_terms": [
"Q3 2025",
"Q4 2025"
],
"regulatory_gap": false,
"regulatory_score": 10,
"rollup": {
"text": "2 outdated \u00b7 3 legacy \u00b7 anomaly: no \u00b7 validation: valid \u00b7 reg: 10"
},
"severity": "MEDIUM",
"validation": {
"reason": "The policy is clear, specific, and aligns with prudent financial management best practices.",
"status": "VALID"
}
},
"domain_scores": {
"operational": 1,
"regulatory": 1,
"technical": 1
},
"explanation": "Dividends should not be paid before Q4 2026, and even then only if net debt/EBITDA is under 2.30x and liquidity exceeds AED 35.0m.",
"is_archived": false,
"ops": 10.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"\"No dividend should be paid before Q4 2026\"",
"\"Even in Q4 2026, a dividend should only be considered\"",
"\"net debt / EBITDA is below 2.30x\"",
"\"liquidity remains above AED 35.0m\"",
"\"The February 2025 idea of a Q3 2025 dividend is obsolete\"",
"\"late 2026\"",
"\"FY2026\""
],
"explanation": "Terms related to current and future fiscal periods (Q4 2026) are marked CURRENT. References to past dates (Q3 2025) and the \u0027February 2025 idea\u0027 are marked OUTDATED. Technical financial ratios and currency amounts are marked LEGACY-VALID as they define the future criteria.",
"terms": [
{
"category": "CURRENT",
"term": "Q4 2026"
},
{
"category": "OUTDATED",
"term": "Q3 2025"
},
{
"category": "OUTDATED",
"term": "Q4 2025"
},
{
"category": "LEGACY-VALID",
"term": "FY2026"
},
{
"category": "LEGACY-VALID",
"term": "net debt / EBITDA"
},
{
"category": "LEGACY-VALID",
"term": "AED 35.0m"
}
]
},
"prompt_10": {
"evidence": [
"\"No dividend should be paid before Q4 2026\"",
"\"net debt / EBITDA is below 2.30x\""
],
"status": "VALID",
"summary": "The policy is clear, specific, and aligns with prudent financial management best practices."
},
"prompt_2": {
"evidence": [
"\"net debt / EBITDA\""
],
"explanation": "The document mentions a financial metric \u0027net debt / EBITDA\u0027, which is a standard business calculation rather than a specific software or hardware technology. Therefore, no specific technology tools or protocols are found to classify as SUPPORTED, LEGACY-EOL, or OBSOLETE.",
"references": []
},
"prompt_4": {
"evidence": [
"\"liquidity remains above AED 35.0m after the distribution\""
],
"status": "STANDARD_PRACTICE",
"summary": "The requirement to maintain specific liquidity levels post-distribution is a standard financial governance practice."
},
"prompt_6": {
"evidence": [
"\"net debt / EBITDA is below 2.30x\"",
"\"liquidity remains above AED 35.0m\""
],
"scores": {
"operational": 10,
"regulatory": 10,
"technical": 10
},
"summary": "Clear, quantitative thresholds provide strong operational, technical, and regulatory alignment with best practices."
},
"prompt_9": {
"evidence": [
"\"The February 2025 idea of a Q3 2025 dividend is obsolete\"",
"\"treasury\u0027s recommended base case assumes no shareholder distribution in FY2026\""
],
"status": "NO_ANOMALY",
"summary": "There are no contradictions. The document consistently states that past dividend ideas are obsolete and the base case assumes no distribution, despite mentioning a hypothetical \u0027symbolic\u0027 discussion."
}
},
"reg": 10.0,
"score_evidence": [
{
"dimension": "operational",
"phrase_from_text": "No dividend should be paid before Q4 2026."
},
{
"dimension": "technical",
"phrase_from_text": "net debt / EBITDA is below 2.30x"
},
{
"dimension": "regulatory",
"phrase_from_text": "liquidity remains above AED 35.0m after the distribution"
}
],
"summary": "Dividends should not be paid before Q4 2026, and even then only if net debt/EBITDA is under 2.30x and liquidity exceeds AED 35.0m.",
"supersedence": [
{
"detected_at": "Tue, 26 May 2026 17:27:49 GMT",
"id": 6,
"new_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132",
"old_chunk_id": "2962e8a3-906f-579d-94cc-391d3499a222",
"reason": "New version introduces a Q4 2026 timeline, lowers the EBITDA threshold from 2.75x to 2.30x, raises liquidity from AED 20.0m to AED 35.0m, and declares the February 2025/Q3 2025 plan obsolete. The old FY2024 data is outdated."
}
],
"tech": 10.0,
"temporal_signals": [
"year",
"legacy"
]
}
Terms like 'older documents' and 'take-or-pay' are marked outdated or legacy, while 'volume-band', 'headroom', and 'impairment' appear in current context descriptions.
Forecasting is currently active. Take-or-pay is identified as legacy in contrast to volume-bands. Safety scope is currently supported.
The approval of the full expansion has transitioned into a paused state, indicating the original operational procedure is obsolete while a revised safety scope remains active.
Technical data is current with audit values. Operational flexibility has tightened due to leverage gates. Regulatory compliance shifted via an amended test and waiver.
A significant contradiction exists between the earlier statement that no impairment was needed and the later recording of an AED 11.9m impairment.
The document explicitly advises caution when interpreting older data positions, making it uncertain whether the stated earlier positions represent current best practices or merely historical records.
{
"badge_class": "score-yellow",
"chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9",
"confidence": 62.05,
"contextual_qna": [
{
"answer": "AED 75.2m forecast or AED 49.8m revised forecast.",
"question": "What was the original FY2025 EBITDA forecast before revision?"
},
{
"answer": "AED 52.4m audited.",
"question": "What is the current audited FY2025 EBITDA?"
},
{
"answer": "Five-year take-or-pay became a three-year volume-band with service rebates, AED 118.0m planning value.",
"question": "How did the Atlas Metro agreement change from the earlier position?"
},
{
"answer": "Full expansion paused; AED 17.0m safety/reliability scope continues.",
"question": "What is the current status of the NorthDock expansion?"
},
{
"answer": "Dec 2025 breach waived; Mar 2026 compliant under amended test.",
"question": "What change occurred regarding the Covenant status in December 2025?"
},
{
"answer": "No dividend before Q4 2026, and only under leverage/liquidity gates.",
"question": "When is the next dividend proposed according to the latest data?"
},
{
"answer": "AED 11.9m total impairment recorded.",
"question": "What impact did the inventory assessment have compared to earlier views?"
},
{
"answer": "Older documents may produce plausible but outdated answers.",
"question": "Why should older documents be treated carefully?"
}
],
"contradictions": [
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d62a0b81-63d2-5749-9c7e-bbf11e44f17a",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 832,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 833,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "caf11235-8513-5ec6-a552-7d071c19497b",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 834,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "e8db38cd-c6d6-5a2b-987a-19af4622a1d5",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 835,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "8a8a3636-0fb7-50d9-97a5-0a71934164cf",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 836,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "37025f22-da61-5bbf-933d-2b8797d2ad13",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 837,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "f2a9f1fd-0823-5ff8-a378-7ec914665e27",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 838,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d0fc537f-80c6-5216-895f-61ee9ea93230",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 839,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "6bc62eb1-b875-5609-bb65-edf39310d745",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 840,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "db9322ab-9bcb-538d-af5d-6a8359641174",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 841,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9ce2663a-766b-51e9-9a39-be9565a0230f",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 842,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "88d967cb-ecb4-5bd1-8fc4-2d810ac728c9",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 843,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "ff16ee99-581f-5440-8b55-5b9a3f0277b5",
"detected_at": "Tue, 26 May 2026 17:27:50 GMT",
"id": 844,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9"
}
],
"core_answers": {
"What is the main idea?": "This document highlights significant changes in financial and operational positions, noting that older forecasts are now outdated or audited figures.",
"What processes or procedures are described?": "The text describes shifts from planned take-or-pay contracts to volume-banded service agreements with specific financial caps.",
"What risks or threats are discussed?": "The text discusses Covenant breaches waived due to leverage gates, inventory impairments, and dividend deferrals."
},
"decay_score": 0.3795,
"decay_summary": {
"anomaly": {
"evidence": [
"\"No impairment needed\"",
"\"AED 11.9m total impairment recorded\""
],
"status": "MAJOR"
},
"archive_suggestion": true,
"counts": {
"legacy_indicators": 3,
"outdated_terms": 1
},
"legacy": [
{
"label": "take-or-pay",
"tag": "LEGACY-VALID"
},
{
"label": "take-or-pay",
"tag": "LEGACY-EOL"
},
{
"label": "Obsolete Practice",
"tag": "OBSOLETE_PRACTICE"
}
],
"outdated_terms": [
"older documents"
],
"regulatory_gap": false,
"regulatory_score": 7,
"rollup": {
"text": "1 outdated \u00b7 3 legacy \u00b7 anomaly: major \u00b7 validation: uncertain \u00b7 reg: 7"
},
"severity": "HIGH",
"validation": {
"reason": "The document explicitly advises caution when interpreting older data positions, making it uncertain whether the stated earlier positions represent current best practices or merely historical records.",
"status": "UNCERTAIN"
}
},
"domain_scores": {
"operational": 0,
"regulatory": 0,
"technical": 1
},
"explanation": "This document highlights significant changes in financial and operational positions, noting that older forecasts are now outdated or audited figures.",
"is_archived": false,
"ops": 6.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"\"Older documents may produce plausible but outdated answers.\"",
"\"Five-year take-or-pay\"",
"\"Three-year volume-band with service rebates, AED 118.0m planning value\"",
"\"Comfortable headroom or no waiver needed\"",
"\"AED 11.9m total impairment recorded\""
],
"explanation": "Terms like \u0027older documents\u0027 and \u0027take-or-pay\u0027 are marked outdated or legacy, while \u0027volume-band\u0027, \u0027headroom\u0027, and \u0027impairment\u0027 appear in current context descriptions.",
"status": "terms_detected",
"terms": [
{
"category": "OUTDATED",
"term": "older documents"
},
{
"category": "LEGACY-VALID",
"term": "take-or-pay"
},
{
"category": "CURRENT",
"term": "volume-band"
},
{
"category": "CURRENT",
"term": "headroom"
},
{
"category": "CURRENT",
"term": "impairment"
}
]
},
"prompt_10": {
"evidence": [
"\"Older documents may produce plausible but outdated answers.\"",
"\"The following items should be treated carefully by any governance or retrieval system:"
],
"status": "UNCERTAIN",
"summary": "The document explicitly advises caution when interpreting older data positions, making it uncertain whether the stated earlier positions represent current best practices or merely historical records."
},
"prompt_2": {
"evidence": [
"\"AED 75.2m forecast or AED 49.8m revised forecast\"",
"\"Five-year take-or-pay\"",
"\"AED 17.0m safety/reliability scope continues\""
],
"explanation": "Forecasting is currently active. Take-or-pay is identified as legacy in contrast to volume-bands. Safety scope is currently supported.",
"references": [
{
"category": "SUPPORTED",
"item": "EBITDA forecasting"
},
{
"category": "LEGACY-EOL",
"item": "take-or-pay"
},
{
"category": "SUPPORTED",
"item": "safety/reliability scope"
}
],
"status": "references_detected"
},
"prompt_4": {
"evidence": [
"\"Full AED 54.0m expansion approved\"",
"\"Full expansion paused; AED 17.0m safety/reliability scope continues\""
],
"status": "OBSOLETE_PRACTICE",
"summary": "The approval of the full expansion has transitioned into a paused state, indicating the original operational procedure is obsolete while a revised safety scope remains active."
},
"prompt_6": {
"evidence": [
"\"AED 52.4m audited\"",
"\"Dec 2025 breach waived; Mar 2026 compliant under amended test\"",
"\"only under leverage/liquidity gates\""
],
"scores": {
"operational": 6,
"regulatory": 7,
"technical": 8
},
"status": "scores_assigned",
"summary": "Technical data is current with audit values. Operational flexibility has tightened due to leverage gates. Regulatory compliance shifted via an amended test and waiver."
},
"prompt_9": {
"evidence": [
"\"No impairment needed\"",
"\"AED 11.9m total impairment recorded\""
],
"status": "MAJOR_ANOMALY",
"summary": "A significant contradiction exists between the earlier statement that no impairment was needed and the later recording of an AED 11.9m impairment."
}
},
"reg": 7.0,
"score_evidence": [
{
"dimension": "technical",
"phrase_from_text": "Older documents may produce plausible but outdated answers."
}
],
"summary": "This document highlights significant changes in financial and operational positions, noting that older forecasts are now outdated or audited figures.",
"supersedence": [
{
"detected_at": "Tue, 26 May 2026 17:28:20 GMT",
"id": 7,
"new_chunk_id": "f7028329-c778-537a-8cd3-51544a97bcf9",
"old_chunk_id": "2962e8a3-906f-579d-94cc-391d3499a222",
"reason": "Updated with audited FY2025 EBITDA data, corrected Atlas Metro deal terms (from 5-year to 3-year), reflected changes in NorthDock expansion status, revised covenant compliance (waived breach, amended test), clarified dividend restrictions, and noted inventory impairment."
}
],
"tech": 8.0,
"temporal_signals": [
"year",
"version",
"legacy",
"modern"
]
}
The document explicitly prioritizes the April 2026 note for current reporting while referencing February 2025 and October 2025 documents only for historical context, classifying the latter months as outdated relative to the current date.
No specific technologies, tools, or protocols are mentioned in the provided text chunk.
The text mandates precise, date-specific reporting and explicitly states that a compliance status statement is incomplete without a specific date and covenant reference, representing a standard best practice.
Scores reflect strong operational clarity regarding status changes (growth case, tightening, stabilization). Regulatory compliance is clearly defined but relies on external 'amended covenant' details not fully elaborated in the text.
The anomaly is minor: the text recommends using the April 2026 note 'ahead of' older documents for current reporting, yet simultaneously states that 'all three documents are useful' for historical context, creating a slight ambiguity on the utility of legacy data versus the strict preference for current data.
The document aligns with best practices by emphasizing date-specific reporting, precise terminology, and clear distinctions between current status and historical context.
{
"badge_class": "score-red",
"chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e",
"confidence": 56.67,
"contextual_qna": [
{
"answer": "The February 2025 board pack, October 2025 credit memo, and April 2026 note are all useful.",
"question": "What documents are useful for the history of this issue?"
},
{
"answer": "The February 2025 board pack showed the original growth case.",
"question": "Which period showed the original growth case?"
},
{
"answer": "The October 2025 period showed the lender tightening phase.",
"question": "What happened during the October 2025 period?"
},
{
"answer": "Orion Vale is compliant only when tied to 31 March 2026 and the amended covenant.",
"question": "What state was Orion Vale in regarding compliance?"
},
{
"answer": "The full expansion is paused at NorthDock.",
"question": "Is the full expansion at NorthDock still active?"
},
{
"answer": "Reduced safety and reliability work continues at NorthDock.",
"question": "What work continues at NorthDock?"
},
{
"answer": "The April document shows partial stabilization after waiver and collections.",
"question": "What is the significance of the April document?"
},
{
"answer": "Current statements should be date-specific to ensure accuracy and compliance.",
"question": "Why must current statements be date-specific?"
}
],
"contradictions": [
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:28:21 GMT",
"id": 845,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "caf11235-8513-5ec6-a552-7d071c19497b",
"detected_at": "Tue, 26 May 2026 17:28:21 GMT",
"id": 846,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "e8db38cd-c6d6-5a2b-987a-19af4622a1d5",
"detected_at": "Tue, 26 May 2026 17:28:21 GMT",
"id": 847,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "8a8a3636-0fb7-50d9-97a5-0a71934164cf",
"detected_at": "Tue, 26 May 2026 17:28:21 GMT",
"id": 848,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "f2a9f1fd-0823-5ff8-a378-7ec914665e27",
"detected_at": "Tue, 26 May 2026 17:28:21 GMT",
"id": 849,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d0fc537f-80c6-5216-895f-61ee9ea93230",
"detected_at": "Tue, 26 May 2026 17:28:21 GMT",
"id": 850,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "3134e86b-2dfc-5718-baf8-40121b25b173",
"detected_at": "Tue, 26 May 2026 17:28:21 GMT",
"id": 851,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "ff16ee99-581f-5440-8b55-5b9a3f0277b5",
"detected_at": "Tue, 26 May 2026 17:28:21 GMT",
"id": 852,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "46e07a09-497f-5fa9-bdae-2962bae34bff",
"detected_at": "Tue, 26 May 2026 17:28:21 GMT",
"id": 853,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e"
}
],
"core_answers": {
"What is the main idea?": "April 2026 reporting documents show partial stabilization after regulatory waivers and collections.",
"What processes or procedures are described?": "Reports must be date-specific and tied to amended covenants and specific board packs.",
"What risks or threats are discussed?": "Lender tightening occurred in October 2025, causing a pause in full expansion."
},
"decay_score": 0.4333,
"decay_summary": {
"anomaly": {
"evidence": [
"For current management reporting, this April 2026 note should be used ahead of the February 2025 board pack and the October 2025 credit memo. For a history of the issue, all three documents are useful",
"The NorthDock position also requires precision: the full expansion is paused, but reduced safety and reliability work continues."
],
"status": "MINOR"
},
"archive_suggestion": false,
"counts": {
"legacy_indicators": 2,
"outdated_terms": 2
},
"legacy": [
{
"label": "February 2025 board pack",
"tag": "LEGACY-VALID"
},
{
"label": "October 2025 credit memo",
"tag": "LEGACY-VALID"
}
],
"outdated_terms": [
"February",
"October"
],
"regulatory_gap": false,
"regulatory_score": 7,
"rollup": {
"text": "2 outdated \u00b7 2 legacy \u00b7 anomaly: minor \u00b7 validation: valid \u00b7 reg: 7"
},
"severity": "MEDIUM",
"validation": {
"reason": "The document aligns with best practices by emphasizing date-specific reporting, precise terminology, and clear distinctions between current status and historical context.",
"status": "VALID"
}
},
"domain_scores": {
"operational": 2,
"regulatory": 3,
"technical": 1
},
"explanation": "April 2026 reporting documents show partial stabilization after regulatory waivers and collections.",
"is_archived": false,
"ops": 9.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"For current management reporting, this April 2026 note should be used ahead of the February 2025 board pack and the October 2025 credit memo. For a history of the issue, all three documents are useful: February shows the original growth case, October shows the lender tightening phase, and April shows the partial stabilization after waiver and collections."
],
"explanation": "The document explicitly prioritizes the April 2026 note for current reporting while referencing February 2025 and October 2025 documents only for historical context, classifying the latter months as outdated relative to the current date.",
"terms": [
{
"category": "CURRENT",
"term": "current management reporting"
},
{
"category": "LEGACY-VALID",
"term": "February 2025 board pack"
},
{
"category": "LEGACY-VALID",
"term": "October 2025 credit memo"
},
{
"category": "OUTDATED",
"term": "February"
},
{
"category": "OUTDATED",
"term": "October"
},
{
"category": "CURRENT",
"term": "April"
}
]
},
"prompt_10": {
"evidence": [
"For current management reporting, this April 2026 note should be used ahead of the February 2025 board pack and the October 2025 credit memo.",
"Current statements should be date-specific.",
"The NorthDock position also requires precision"
],
"status": "VALID",
"summary": "The document aligns with best practices by emphasizing date-specific reporting, precise terminology, and clear distinctions between current status and historical context."
},
"prompt_2": {
"evidence": [],
"explanation": "No specific technologies, tools, or protocols are mentioned in the provided text chunk.",
"references": []
},
"prompt_4": {
"evidence": [
"Current statements should be date-specific.",
"Orion Vale is compliant"
],
"status": "STANDARD_PRACTICE",
"summary": "The text mandates precise, date-specific reporting and explicitly states that a compliance status statement is incomplete without a specific date and covenant reference, representing a standard best practice."
},
"prompt_6": {
"evidence": [
"Orion Vale is compliant",
"lender tightening phase",
"partial stabilization after waiver and collections"
],
"scores": {
"operational": 9,
"regulatory": 7,
"technical": 8
},
"summary": "Scores reflect strong operational clarity regarding status changes (growth case, tightening, stabilization). Regulatory compliance is clearly defined but relies on external \u0027amended covenant\u0027 details not fully elaborated in the text."
},
"prompt_9": {
"evidence": [
"For current management reporting, this April 2026 note should be used ahead of the February 2025 board pack and the October 2025 credit memo. For a history of the issue, all three documents are useful",
"The NorthDock position also requires precision: the full expansion is paused, but reduced safety and reliability work continues."
],
"status": "MINOR_ANOMALY",
"summary": "The anomaly is minor: the text recommends using the April 2026 note \u0027ahead of\u0027 older documents for current reporting, yet simultaneously states that \u0027all three documents are useful\u0027 for historical context, creating a slight ambiguity on the utility of legacy data versus the strict preference for current data."
}
},
"reg": 7.0,
"score_evidence": [
{
"dimension": "regulatory",
"phrase_from_text": "October shows the lender tightening phase"
},
{
"dimension": "technical",
"phrase_from_text": "Orion Vale is compliant"
},
{
"dimension": "operational",
"phrase_from_text": "reduced safety and reliability work continues"
}
],
"summary": "April 2026 reporting documents show partial stabilization after regulatory waivers and collections.",
"supersedence": [
{
"detected_at": "Tue, 26 May 2026 17:28:53 GMT",
"id": 8,
"new_chunk_id": "02b87ffb-6f21-5e83-8d86-12346f25814e",
"old_chunk_id": "94670ffa-d5c5-5d59-b29d-8917dd8b76fc",
"reason": "The new version updates the document date to April 2026 (replacing February 2025), clarifies that current statements are date-specific (referencing 31 March 2026), and provides specific updates on NorthDock\u0027s operational status (partial expansion paused, safety work continuing)."
}
],
"tech": 8.0,
"temporal_signals": [
"year",
"version",
"legacy",
"modern"
]
}
All key financial terms relate to current market conditions and do not reflect obsolete or deprecated language.
No specific technologies, tools, or protocols are mentioned in the text.
The current procedure of constraining capital until leverage decreases is classified as legacy because it relies on an outdated leverage target rather than modern risk metrics.
Technical viability is moderate due to the lack of specific metrics, operational relevance is high given the focus on constraints, and regulatory impact is noted through waiver terms but lacks detail.
A minor anomaly exists in the timeline as the company corrected its overcommitment in late 2025 but remained unstable until early 2026, suggesting a gap between correction and full stabilization.
The statement aligns with standard financial analysis practices by recognizing complexity beyond simple distress, validating operational viability, and recommending prudent capital management.
{
"badge_class": "score-red",
"chunk_id": "db436456-efb7-512c-932f-fb7981d5686c",
"confidence": 58.8,
"contextual_qna": [
{
"answer": "The company remains operationally viable.",
"question": "What is Orion Vale\u0027s current operational status?"
},
{
"answer": "The growth plan was overcommitted in early 2025.",
"question": "When was the initial growth plan implemented?"
},
{
"answer": "Lenders corrected the situation in late 2025.",
"question": "How did lenders address the overcommitment?"
},
{
"answer": "Cash collection and waiver terms stabilized the situation in early 2026.",
"question": "What helped stabilize the situation in 2026?"
},
{
"answer": "Leverage must move below the mid-2x range.",
"question": "What leverage threshold must be reached before easing capital constraints?"
},
{
"answer": "No, Orion Vale is not in a simple distress story.",
"question": "Is this a simple distress story?"
}
],
"contradictions": [
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d62a0b81-63d2-5749-9c7e-bbf11e44f17a",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 854,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "9b13b13e-ea27-59ec-b6bf-3294c75d3e51",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 855,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "caf11235-8513-5ec6-a552-7d071c19497b",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 856,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "e8db38cd-c6d6-5a2b-987a-19af4622a1d5",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 857,
"justification": "No reason provided.",
"question": "What is the main idea?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "8a8a3636-0fb7-50d9-97a5-0a71934164cf",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 858,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "37025f22-da61-5bbf-933d-2b8797d2ad13",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 859,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "f2a9f1fd-0823-5ff8-a378-7ec914665e27",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 860,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "d0fc537f-80c6-5216-895f-61ee9ea93230",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 861,
"justification": "No reason provided.",
"question": "What risks or threats are discussed?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "3134e86b-2dfc-5718-baf8-40121b25b173",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 862,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "ff16ee99-581f-5440-8b55-5b9a3f0277b5",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 863,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "46e07a09-497f-5fa9-bdae-2962bae34bff",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 864,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "3c382351-10b6-57d7-8dc7-7cc80cc74132",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 865,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
},
{
"canonical_conflicting_chunk_id": null,
"canonical_source_chunk_id": null,
"conflicting_chunk_id": "2962e8a3-906f-579d-94cc-391d3499a222",
"detected_at": "Tue, 26 May 2026 17:28:54 GMT",
"id": 866,
"justification": "No reason provided.",
"question": "What processes or procedures are described?",
"source_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c"
}
],
"core_answers": {
"What is the main idea?": "A growth plan was overcommitted in early 2025, corrected by lenders in late 2025, and stabilized by cash collection.",
"What processes or procedures are described?": "Lenders corrected the overcommitted growth plan in late 2025.",
"What risks or threats are discussed?": "Capital allocation must stay constrained until leverage moves below the mid-2x range."
},
"decay_score": 0.412,
"decay_summary": {
"anomaly": {
"evidence": [
"overcommitted in early 2025",
"corrected by lenders in late 2025",
"stabilized by cash collection and waiver terms in early 2026"
],
"status": "MINOR"
},
"archive_suggestion": true,
"counts": {
"legacy_indicators": 1,
"outdated_terms": 0
},
"legacy": [
{
"label": "Legacy Practice",
"tag": "LEGACY_PRACTICE"
}
],
"outdated_terms": [],
"regulatory_gap": false,
"regulatory_score": 6,
"rollup": {
"text": "0 outdated \u00b7 1 legacy \u00b7 anomaly: minor \u00b7 validation: valid \u00b7 reg: 6"
},
"severity": "HIGH",
"validation": {
"reason": "The statement aligns with standard financial analysis practices by recognizing complexity beyond simple distress, validating operational viability, and recommending prudent capital management.",
"status": "VALID"
}
},
"domain_scores": {
"operational": 0,
"regulatory": 0,
"technical": 1
},
"explanation": "A growth plan was overcommitted in early 2025, corrected by lenders in late 2025, and stabilized by cash collection.",
"is_archived": false,
"ops": 8.0,
"prompt_diagnostics": {
"prompt_1": {
"evidence": [
"a growth plan",
"corrected by lenders",
"cash collection",
"waiver terms",
"leverage"
],
"explanation": "All key financial terms relate to current market conditions and do not reflect obsolete or deprecated language.",
"status": "COMPLETE",
"terms": [
{
"category": "CURRENT",
"term": "growth plan"
},
{
"category": "CURRENT",
"term": "lenders"
},
{
"category": "CURRENT",
"term": "cash collection"
},
{
"category": "CURRENT",
"term": "waiver terms"
},
{
"category": "CURRENT",
"term": "leverage"
}
]
},
"prompt_10": {
"evidence": [
"Orion Vale is not in a simple distress story",
"The better reading is that a growth plan was overcommitted in early 2025",
"The company remains operationally viable"
],
"status": "VALID",
"summary": "The statement aligns with standard financial analysis practices by recognizing complexity beyond simple distress, validating operational viability, and recommending prudent capital management."
},
"prompt_2": {
"evidence": [],
"explanation": "No specific technologies, tools, or protocols are mentioned in the text.",
"references": [],
"status": "COMPLETE"
},
"prompt_4": {
"evidence": [
"capital allocation must stay constrained",
"until leverage moves below the mid-2x range"
],
"status": "LEGACY_PRACTICE",
"summary": "The current procedure of constraining capital until leverage decreases is classified as legacy because it relies on an outdated leverage target rather than modern risk metrics."
},
"prompt_6": {
"evidence": [
"operationally viable",
"capital allocation must stay constrained",
"waiver terms"
],
"scores": {
"operational": 8,
"regulatory": 6,
"technical": 7
},
"status": "COMPLETE",
"summary": "Technical viability is moderate due to the lack of specific metrics, operational relevance is high given the focus on constraints, and regulatory impact is noted through waiver terms but lacks detail."
},
"prompt_9": {
"evidence": [
"overcommitted in early 2025",
"corrected by lenders in late 2025",
"stabilized by cash collection and waiver terms in early 2026"
],
"status": "MINOR_ANOMALY",
"summary": "A minor anomaly exists in the timeline as the company corrected its overcommitment in late 2025 but remained unstable until early 2026, suggesting a gap between correction and full stabilization."
}
},
"reg": 6.0,
"score_evidence": [
{
"dimension": "technical",
"phrase_from_text": "A short direct quote."
}
],
"summary": "A growth plan was overcommitted in early 2025, corrected by lenders in late 2025, and stabilized by cash collection.",
"supersedence": [
{
"detected_at": "Tue, 26 May 2026 17:29:20 GMT",
"id": 9,
"new_chunk_id": "db436456-efb7-512c-932f-fb7981d5686c",
"old_chunk_id": "94670ffa-d5c5-5d59-b29d-8917dd8b76fc",
"reason": "New version updates the fundamental situation from a static \u0027sensitive assumption\u0027 pack to a dynamic narrative about an overcommitted growth plan being corrected by lenders and stabilization measures, adding specific new context about leverage targets."
}
],
"tech": 7.0,
"temporal_signals": [
"year",
"version",
"legacy",
"modern"
]
}