From a27eaf8f911f75508a9db46d97abda675fa2b448 Mon Sep 17 00:00:00 2001
From: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>
Date: Sun, 11 Oct 2026 23:31:33 -0400
Subject: [PATCH] Feature 23 review fix: narrow the eligibility doc claim
 (#208)

Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>
---
 docs/ARCHITECTURE.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md
index ac36359..33f12dc 100644
--- a/docs/ARCHITECTURE.md
+++ b/docs/ARCHITECTURE.md
@@ -276,9 +276,12 @@ automatic** (D-021).
   `grounded`, `failed` (with its reason) or `skipped`. A dinner whose write
   fails is `failed` with `grounding_error` and left as it was; the others
   still run, then the job fails with `internal_error`, keeping that result.
-  Every dinner response carries `photo_backfill_eligible`, whether the
-  backfill grounds that dinner, computed by the same condition it lists
-  dinners by, so a client offers a search only where one runs.
+  The responses returning a `dinners.Dinner` representation (the list; the
+  create, update, archive, favorite and grounding responses; the idea
+  responses) carry `photo_backfill_eligible`, and
+  `GET /api/v1/dinners/{id}` does not; it says whether the backfill grounds
+  that dinner, computed by the same condition it lists dinners by, so a
+  client offers a search only where one runs.
   `GET /api/v1/dinners/{id}/recipe-candidates`
   searches for the dinner's name and returns `{candidates: [{candidate_id,
   title, site_name, photo_url, minutes}]}`, at most 3, ranked as `Ground`