Q18, run 2026-11-04-1616-sonnet

← back to the run

Which issuers were on Rating Watch Negative on 1 October 2026?

Tests: Watch over time: Marlow's Watch ended with its 2026 affirmation.

Expected: issuers = ['E06']

✅ R1 csv run 1 graded by code

E06 (A17). E14's watch (A35) was resolved by the affirmation A33, which carries no watch.

JSON: {"issuers": ["E06"]}

✅ R1 csv run 2 graded by code

E06 (A17). E14's earlier watch (A35) was superseded by A33.

JSON: {"issuers": ["E06"]}

✅ R1 csv run 3 graded by code

E06, from A17. E14's watch (A35) was resolved by A33, which carries no watch.

JSON: {"issuers": ["E06"]}

✅ R1 csv run 4 graded by code

E06 (A17). E14's watch from A35 was resolved by the affirmation with a Stable outlook in A33.

JSON: {"issuers": ["E06"]}

✅ R1 csv run 5 graded by code

E06, from A17. E14's watch (A35) was superseded by A33, which has no watch.

JSON: {"issuers": ["E06"]}

✅ R2 rdf run 1 graded by code

E06, from A17 (2026-09-03). E14's earlier watch (A35) was followed by the affirmation A33.

JSON: {"issuers": ["E06"]}

✅ R2 rdf run 2 graded by code

E06 (A17). E14's earlier Watch (A35) was resolved by A33.

JSON: {"issuers": ["E06"]}

✅ R2 rdf run 3 graded by code

E06. A17 (2026-09-03) placed it on Rating Watch Negative, with no later action.

JSON: {"issuers": ["E06"]}

✅ R2 rdf run 4 graded by code

E06 (A17). E14's earlier watch (A35) was superseded by the affirmation with a Stable outlook in A33.

JSON: {"issuers": ["E06"]}

✅ R2 rdf run 5 graded by code

E06 (A17). E14's earlier watch (A35) was superseded by an affirmation with a Stable outlook on 2026-05-01 (A33).

JSON: {"issuers": ["E06"]}

✅ R6 rdf+ontology run 1 graded by code

E06. A17 (2026-09-03) put it on RWN. E14's watch (A35) was superseded by the affirmation in A33, which carries no watch.

JSON: {"issuers": ["E06"]}

✅ R6 rdf+ontology run 2 graded by code

E06. A17 (2026-09-03) is its latest action. E14's Watch (A35) was followed by the A33 affirmation, which ended it.

JSON: {"issuers": ["E06"]}

✅ R6 rdf+ontology run 3 graded by code

E06. A17 (2026-09-03) is its latest action. E14's Watch (A35) was followed by the A33 affirmation, which carries no Watch.

JSON: {"issuers": ["E06"]}

✅ R6 rdf+ontology run 4 graded by code

E06. A17 (2026-09-03) put it on Rating Watch Negative. E14's Watch (A35) was superseded by the affirmation A33.

JSON: {"issuers": ["E06"]}

✅ R6 rdf+ontology run 5 graded by code

E06. A17 (2026-09-03) placed it on RWN. E14's earlier Watch (A35) was superseded by A33.

JSON: {"issuers": ["E06"]}

✅ R5 csv+ontology run 1 graded by code

E06. A17 put it on RWN on 2026-09-03. E14's earlier Watch (A35) was superseded by A33.

JSON: {"issuers": ["E06"]}

✅ R5 csv+ontology run 2 graded by code

E06. A17 placed it on RWN in 2026-09. E14's Watch (A35) was resolved by the affirmation A33, which carries no Watch.

JSON: {"issuers": ["E06"]}

✅ R5 csv+ontology run 3 graded by code

E06. A17 put it on RWN on 2026-09-03. E14's earlier watch (A35) was superseded by A33, which carries no watch.

JSON: {"issuers": ["E06"]}

✅ R5 csv+ontology run 4 graded by code

E06. A17 (2026-09-03) placed it on RWN. E14's earlier Watch (A35) ended with the affirmation A33.

JSON: {"issuers": ["E06"]}

✅ R5 csv+ontology run 5 graded by code

E06. A17 (2026-09-03) put it on RWN. E14's Watch (A35) was resolved by the affirmation in A33.

JSON: {"issuers": ["E06"]}