Q1, run 2026-11-04-1644-haiku

← back to the run

What was Kestrel Energy's rating on 1 January 2025?

Tests: Time: a rating holds from one action to the next, so 'the rating on a date' is the latest action on or before it.

Expected: rating = A-

✅ R1 csv run 1 graded by code

A-. Kestrel Energy (E01) was assigned A- on 2024-03-12 (A01), and the downgrade to BBB came later, in June 2025 (A02).

JSON: {"rating": "A-"}

✅ R1 csv run 2 graded by code

A-. The rating was assigned on 2024-03-12 (A01) and not cut until 2025-06-20 (A02, to BBB), so it was still A- on 1 January 2025.

JSON: {"rating": "A-"}

✅ R1 csv run 3 graded by code

A-. A01 (A-) applied until A02 downgraded Kestrel to BBB on 2025-06-20.

JSON: {"rating": "A-"}

✅ R1 csv run 4 graded by code

A-. A01 (AS, 2024-03-12) was the latest action before 2025-01-01; the downgrade to BBB came later, in A02 (2025-06-20).

JSON: {"rating": "A-"}

✅ R1 csv run 5 graded by code

A-. On 2025-06-20 it was downgraded to BBB (A02), so A01 (A-, 2024-03-12) was still in effect on 1 Jan 2025.

JSON: {"rating": "A-"}

✅ R2 rdf run 1 graded by code

A-
Kestrel Energy's latest rating before 1 Jan 2025 is A01 (A-, 2024-03-12); the next action, A02, is dated 2025-06-20.

JSON: {"rating": "A-"}

✅ R2 rdf run 2 graded by code

A-. Rating A01 (AS, A-, 2024-03-12) was in effect until the downgrade to BBB in A02 (2025-06-20).

JSON: {"rating": "A-"}

✅ R2 rdf run 3 graded by code

A-. The latest long-term rating before 1 Jan 2025 is A- from A01 (2024-03-12). The BBB downgrade (A02) came later, in June 2025.

JSON: {"rating": "A-"}

✅ R2 rdf run 4 graded by code

A-. The last rating before 1 Jan 2025 is A01 (A-, 2024-03-12); the next action, A02 (BBB, 2025-06-20), came later.

JSON: {"rating": "A-"}

✅ R2 rdf run 5 graded by code

A-
Kestrel's last rating before 1 Jan 2025 was A- (assigned in A01, 2024-03-12), and the next action (A02, 2025-06-20) came later.

JSON: {"rating": "A-"}

✅ R6 rdf+ontology run 1 graded by code

A-. A01 (Assigned A-, 2024-03-12) is the latest action before 2025-01-01; the downgrade to BBB in A02 came later, on 2025-06-20.

JSON: {"rating": "A-"}

✅ R6 rdf+ontology run 2 graded by code

A- (long-term FC issuer rating).
E01's A01 (A-, 2024-03-12) held until the DG to BBB in A02 (2025-06-20).

JSON: {"rating": "A-"}

✅ R6 rdf+ontology run 3 graded by code

A-. A01 (AS, 2024-03-12) is the latest FC long-term action before 2025-01-01; A02 (2025-06-20) comes after.

JSON: {"rating": "A-"}

✅ R6 rdf+ontology run 4 graded by code

A-. Latest E01 long-term FC action on or before 2025-01-01 is A01 (AS A-, 2024-03-12); A02 (DG BBB) came later, on 2025-06-20.

JSON: {"rating": "A-"}

✅ R6 rdf+ontology run 5 graded by code

A-. The A- was set by A01 (2024-03-12), and the next action, A02 (2025-06-20, downgrade to BBB), came after 1 January 2025.

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 1 graded by code

A-. Kestrel's LTIDR was assigned A- on 2024-03-12 (A01) and not changed until the downgrade to BBB on 2025-06-20 (A02).

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 2 graded by code

A-. Rating on 1 Jan 2025 is set by A01 (AS, A-, 2024-03-12); A02 (DG to BBB) came later.

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 3 graded by code

A-. E01's LTIDR FC was assigned A- (A01, 2024-03-12) and not changed until the 2025-06-20 downgrade (A02).

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 4 graded by code

A-. Kestrel's last action before 1 Jan 2025 was the assignment at A- (A01, 2024-03-12); the 2025 downgrade (A02) came later.

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 5 graded by code

A-
Latest LTIDR FC action on or before 2025-01-01 is A01 (AS, A-), since A02 (DG to BBB) came later.

JSON: {"rating": "A-"}

✅ R4 csv+markdown run 1 graded by code

A- (BBB from 2025-06-20 onward). Action A01 (2024-03-12) set A-, and the next action, A02 (2025-06-20), was a downgrade to BBB, so the rating on 2025-01-01 was A-.

JSON: {"rating": "A-"}

✅ R4 csv+markdown run 2 graded by code

A-. Kestrel's last LTIDR action before 1 Jan 2025 is A01 (assigned A-, 2024-03-12); the downgrade to BBB came on 2025-06-20 (A02).

JSON: {"rating": "A-"}

✅ R4 csv+markdown run 3 graded by code

A-. The 2024 assignment (A01) is the latest E01 FC long-term action on or before 1 Jan 2025; the downgrade to BBB came later (A02).

JSON: {"rating": "A-"}

✅ R4 csv+markdown run 4 graded by code

A-. E01's LTIDR (FC) was A- from A01 (2024-03-12) until downgraded to BBB on 2025-06-20 (A02), so the 1 Jan 2025 rating is A-.

JSON: {"rating": "A-"}

✅ R4 csv+markdown run 5 graded by code

A-. The latest action on or before 1 Jan 2025 is A01 (assigned A-, 2024-03-12); A02 (downgrade to BBB) came later, on 2025-06-20.

JSON: {"rating": "A-"}

✅ R3 csv+padding run 1 graded by code

A-. The rating was assigned at A- on 2024-03-12 (A01) and not changed until the 2025-06-20 downgrade (A02).

JSON: {"rating": "A-"}

✅ R3 csv+padding run 2 graded by code

A-. The FC issuer rating was A- from A01 (2024-03-12) until the downgrade to BBB in A02 (2025-06-20).

JSON: {"rating": "A-"}

✅ R3 csv+padding run 3 graded by code

A-. A01 assigned A- on 2024-03-12, and the downgrade to BBB (A02) came on 2025-06-20, after 1 Jan 2025.

JSON: {"rating": "A-"}

✅ R3 csv+padding run 4 graded by code

A-. A01 assigned A- on 2024-03-12, and the next action, the downgrade to BBB in A02 (2025-06-20), came later.

JSON: {"rating": "A-"}

✅ R3 csv+padding run 5 graded by code

A-. A01 (2024-03-12) assigned A-, and the downgrade to BBB in A02 came on 2025-06-20, after this date.

JSON: {"rating": "A-"}