The Photo-Sequence Predicate Gap

Case 23-009185 | Card 8 | 4880 T Street, Sacramento CA 95819

The produced 04/10/2023 photo-name sequence places the only backyard verification frames for 4880 T Street after photographs from three other City case files, and the produced record contains no 04/11/2023 photographs behind the next-day issuance note. Paul's RE-INSPECTION entry dated 04/10/2023 ends "A N&O will be requested" M001. The next day's Notes entry states he arrived at 7:00 a.m. to "take photos and update case files" and "issued the Notice and Order" because of "lack of contact from the Owner and failure to obtain an HDB permit" M024. The produced Documents inventory lists no photographs dated 04/11/2023 M013. The only photographic support for "I did verify there is an addition to the detached garage" is IMG_1492 and IMG_1493, the last 4880 T frames in the 04/10/2023 sequence.

The sequence is not confined to this case. The 4880 T file begins with front and card-left images IMG_1372 through IMG_1374; comparator pages produced under R.26-1863 show same-day photographs from three other City case files inside the gap; and only then do IMG_1492 and IMG_1493 appear as the neighbor-yard verification frames M013 R.26-1863.1 R.26-1863.2 R.26-1863.3. The same verification narrative appears under two different dates in two different sections of the file. The produced record does not show a completed-inspection predicate before the order; it shows a backyard-verification sequence ending after three other cases' photographs, a narrative duplicated under two dates, and a next-day issuance note without 04/11 photographs.

If the City contends the IMG names were assigned, renamed, or resequenced after capture by CitizenServe or staff, that explanation depends on records: native image files, image-attachment inventory fields, per-entry created/modified metadata, or audit/workflow logs. Those categories were requested in R.25-3549, R.26-1549, R.26-1963, and R.26-1964; the metadata and audit requests were closed by saying no additional responsive records existed because all records had already been provided under R.26-1549 Card 4. Without a produced renaming, upload, metadata, or audit record, the four-case sequence remains the City's own produced sequence.

The 4880 T Street file holds five photographs dated 04/10/2023: three front-of-dwelling frames taken early (IMG_1372–1374), and two backyard frames (IMG_1492, IMG_1493). There is a 118-frame gap between them. Photographs from three other Sacramento case files, produced as comparator case-file extracts under NextRequest 26-1863, fall inside that gap:

Each frame below is dated 04/10/2023 and carries the City's own caption. IMG_1372 (Case 23-009185, 4880 T St) — View of detached garage from front of dwelling. IMG_1373 (23-009185, 4880 T St) — Entry to dwelling. IMG_1374 (23-009185, 4880 T St) — Card left at site. IMG_1483 (Case 23-000633, R.26-1863.1 comparator page; address not shown on cited page) — Front of dwelling. IMG_1484 (Case 23-000351, R.26-1863.2 comparator page; address not shown on cited page) — Tree damage at roof. IMG_1486 and IMG_1487 (Case 23-007617, 7311 Krishna Dr) — Beds in sunroom. IMG_1488 (23-007617, 7311 Krishna Dr) — Sac Co room and board. IMG_1489 (23-007617, 7311 Krishna Dr) — Signs someone is living in garage. IMG_1492 and IMG_1493 (23-009185, 4880 T St) — View from neighbors lot of work performed.

Produced same-day photo-name sequence: 1372 → 1373 → 1374 [4880 T front] → 1483 [R.26-1863.1 comparator] → 1484 [R.26-1863.2 comparator] → 1486 → 1487 → 1488 → 1489 [7311 Krishna Dr] → 1492 → 1493 [4880 T backyard].

The two backyard photographs — the only photographic support for the verification narrative — are the last frames in the produced same-day sequence: front of 4880 T, three other properties, then the neighbor-yard verification frames at 4880 T. In that sequence the verification is the final photographed step, not a completed predicate documented before issuance.

Source pages for the three cross-anchoring cases are local extracts R.26-1863.1, R.26-1863.2, and R.26-1863.3, all delivered under public request R.26-1863. They are Documents-table pages from the three comparator case-file exports. The 4880 T photo inventory is the case-file Documents page M013.

IN PLAIN TERMS

This card is about timing. The order says the City had already inspected and determined the building was substandard. The photo list shows a different order of events: front-of-house images first, photos from three other cases in between, then the backyard verification images last. Paul's verification note still says a Notice and Order "will be requested." His next-day note says he arrived to take photos, but the file lists no photos from that day. If the City says the filenames were changed later, records could show that. The requester asked for the native images, metadata, attachment inventory, and audit trail. The City closed those requests without producing such records.

RECORD CHAIN

  1. The 04/10/2023 verification entry describes the Notice and Order as a future act. The RE-INSPECTION entry reads: "I met with neighbors to access their backyard to verify work performed. I did verify there is an addition to the detached garage going on... I took pictures of what I saw from where I was standing. A N&O will be requested" M001. As of that entry, the order had not issued; the entry places the request for it after the verification.
  2. The produced photo names interleave across four cases. The 118-number interval between the 4880 T front shots (1374) and backyard shots (1492) contains comparator photographs produced from three other properties that day — 1483, 1484, and 1486–1489 — each listed in a separate City case file (23-000633, 23-000351, 23-007617) in ascending same-day IMG-name order. As produced, four separate case files align into one ascending same-day photo-name sequence, with unlisted numbers remaining in the interval.
  3. The records that would document any post-capture renaming or resequencing were requested and not produced. The requester asked for the original/native inspection images and metadata, the image attachment inventory including filenames and date/time fields, image-handling/transformation records, and audit/workflow records in the R.25-3549 thread. R.26-1549 then asked for a current export of Case 23-009185 and all attachments linked to the case, including photographs, uploaded documents, inspection reports, correspondence, and any files added or modified; the portal shows it was opened and closed the same day, 04/20/2026, releasing 23-009185_Redacted.pdf (Card 49). The requester then asked for CitizenServe per-entry metadata for documents/photos/attachments in R.26-1963, and the case-level audit trail/change history/workflow history in R.26-1964; both were received 05/17/2026 and closed the next morning, 05/18/2026, with statements that no additional responsive records existed because all responsive records had already been provided under R.26-1549. Those closures stand as the City's written position on the existence of such records Card 4.
  4. No produced record documents a renaming or relabeling across the four case files. A manual-renaming explanation for the produced sequence would require records showing who had access to the original same-day image set, who renamed files or changed captions for 4880 T Street and the three comparator cases, when that happened, and how the renamed files were uploaded into four separate case files. Any such accounting would span both the 4880 T production and the R.26-1863 comparator productions. The cited comparator pages identify same-date case photos inside the 4880 T filename interval; they do not identify a different photographer or uploader, and no produced metadata, audit trail, or upload log identifies who performed any renaming or resequencing.
  5. The produced inventory lists no 04/11/2023 photographs behind the issuance note. The 04/11/2023 Notes entry reads "7:00 am. I arrived to SFR to take photos and update case files... I issued the Notice and Order" M024. The Documents inventory carries no photograph dated 04/11/2023 M013. As produced, no 04/11 photo inventory supports the note's "take photos" language.
  6. The verification narrative is logged twice, under two dates. The same RE-INSPECTION text appears at Activities p.1 (dated 04/10/2023) M001 and again in Notes under 04/11/2023, the same date as the issuance entry M024. The second entry places the verification narrative under the issuance date. The produced record does not resolve which date the verification occurred on, and it does not establish a completed pre-order inspection.
  7. The statutory inspection predicate is not supplied by the produced sequence. The Notice and Order recites that the Chief Building Official "has caused to be inspected and has determined" that the building is "in sub-standard and/or dangerous condition" M124. That past-tense sentence tracks the statutory trigger of HSC.17980.C.1. The produced photo-name sequence places the only photographs offered as verification after the front/card-left frames and after the comparator case photos. The cited pages show the order's printed recital of a CBO determination, not a separate findings or delegation record; Paul's note reads, "I issued the Notice and Order" M024.
  8. The timeline most favorable to the issuance note still lacks the predicate document. A Notice and Order is not a request for an inspection; it is the instrument reciting that an inspection and a determination have already occurred. Its face states that the Chief Building Official "has caused to be inspected and has determined" that the building is "in sub-standard and/or dangerous condition" M124, and it must contain "a brief and concise description of the conditions found to render the building substandard" SCC.8.100.720(A)(2) Card 1. On the most favorable reading, the neighbor meeting was set for "Monday (4/10/24) at 3:00 pm" M024 — a source typo in an April 2023 note — after Paul's stated hours of "Monday - Friday. 8:00am - 2:00 pm" E1.7. Issuance is logged the next morning at "7:00 am" M024. Even on that timeline, the served order's Correction List carries only B31/B59 placeholders on a list stating "Neither interior nor exterior has been completely inspected" M125 Card 1. The cited pages show no separate findings or delegation record behind the CBO-determination recital; Paul's note reads, "I issued the Notice and Order" M024; and the verification note ends "A N&O will be requested," describing only "what I saw from where I was standing" M001. The gap is the missing predicate document, not the hour-by-hour sequence.

FULL CIRCLE

The produced photo-name sequence does not supply the completed inspection predicate the order recites. The 4880 T front/card-left frames precede other same-day case photos; the backyard verification frames appear later in the same sequence; and the verification note still describes a Notice and Order as one that "will be requested" M001 M013. The next-day issuance note states Paul arrived to take photos and issued the order, but the produced inventory lists no 04/11 photographs M024 M013.

The City may argue that IMG_####.jpg filenames can be resequenced at upload, that "will be requested" was loose language for an already-made decision, that the duplicated 04/10 narrative is a clerical artifact, or that the 04/11 Notes entry is itself the inspection record. Each of those explanations depends on a record. The requester asked for native inspection photographs, original metadata, image inventories, image-handling records, and audit/change/workflow history R.25-3549 R.26-1549 R.26-1963 R.26-1964. The City closed the metadata and audit requests by saying no additional responsive records existed because all records had already been provided under R.26-1549.

On the produced record, a resequencing explanation would require an unproduced record showing who changed the filenames or sequence in both the 4880 T file and the R.26-1863 comparator exports. The finding is an unresolved gap in the inspection-predicate foundation: the backyard verification photos appear after other same-day case photos, the verification note is future-tense, and the records that could support a resequencing explanation were not produced.

APPLICABLE LAW

SOURCE CITATIONS USED BY THIS CARD

CARD REFERENCES