From 491e7d246074f887d1d8b3b3bec856bc0d547edf Mon Sep 17 00:00:00 2001 From: "Short, Aidan" Date: Fri, 27 Feb 2026 22:41:15 +0000 Subject: [PATCH 1/3] Update incomplete-obligations array max size from 10 to 100 --- docs/_spec/components/schemas/array-max-monitored-elements.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_spec/components/schemas/array-max-monitored-elements.yaml b/docs/_spec/components/schemas/array-max-monitored-elements.yaml index 2a370be..43741d0 100644 --- a/docs/_spec/components/schemas/array-max-monitored-elements.yaml +++ b/docs/_spec/components/schemas/array-max-monitored-elements.yaml @@ -190,7 +190,7 @@ common-proposal-status: case for this set is debugging and troubleshooting. minItems: 0 - maxItems: 10 + maxItems: 100 items: $ref: ./names.yaml From d314a20c7d57873f94d1cd18fe0ef8e6e5c5ae33 Mon Sep 17 00:00:00 2001 From: "Short, Aidan" Date: Fri, 27 Feb 2026 22:41:42 +0000 Subject: [PATCH 2/3] Replace uses of incomplete-facilities with incomplete-obligations --- docs/_spec/components/schemas/array-max-monitored-elements.yaml | 2 +- docs/example-narratives/submitting-forecasts.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/_spec/components/schemas/array-max-monitored-elements.yaml b/docs/_spec/components/schemas/array-max-monitored-elements.yaml index 43741d0..e77ae6e 100644 --- a/docs/_spec/components/schemas/array-max-monitored-elements.yaml +++ b/docs/_spec/components/schemas/array-max-monitored-elements.yaml @@ -169,7 +169,7 @@ common-proposal-status: The number of facilities for this provider whose Ratings Obligation has not been met in this forecast window. This number may be larger than the - size of `incomplete-facilities`, since the latter has a pre-defined + size of `incomplete-obligations`, since the latter has a pre-defined upper bound for performance and application security reasons. The Ratings Provider should check that this value is zero when they diff --git a/docs/example-narratives/submitting-forecasts.md b/docs/example-narratives/submitting-forecasts.md index d870dd6..c8a363b 100644 --- a/docs/example-narratives/submitting-forecasts.md +++ b/docs/example-narratives/submitting-forecasts.md @@ -125,7 +125,7 @@ defines `incomplete-obligation-count`: > The number of facilities for this provider whose Ratings Obligation has > not been met in this forecast window. This number may be larger than the -> size of `incomplete-facilities`, since the latter has a pre-defined +> size of `incomplete-obligations`, since the latter has a pre-defined > upper bound for performance and application security reasons. > The Ratings Provider should check that this value is zero when they From 170e2706e3cf661609fdb10db1eb0211651f7b5a Mon Sep 17 00:00:00 2001 From: "Short, Aidan" Date: Tue, 10 Mar 2026 17:05:39 +0000 Subject: [PATCH 3/3] Increases max incomplete-obligations to max-facilities --- docs/_spec/components/schemas/array-max-monitored-elements.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_spec/components/schemas/array-max-monitored-elements.yaml b/docs/_spec/components/schemas/array-max-monitored-elements.yaml index e77ae6e..0030c54 100644 --- a/docs/_spec/components/schemas/array-max-monitored-elements.yaml +++ b/docs/_spec/components/schemas/array-max-monitored-elements.yaml @@ -190,7 +190,7 @@ common-proposal-status: case for this set is debugging and troubleshooting. minItems: 0 - maxItems: 100 + maxItems: *max-facilities items: $ref: ./names.yaml