# DC truck source navigation ledger — method

Edition: 24 October 2026. Service context: Washington DC, Maryland and Virginia. This edition describes where operators publish information. It does not locate trucks or offer a dated-stop feed.

## What was compiled

The fixed 20-operator roster from the prior edition is preserved, in the same order and with the same record IDs. Each row now records cuisine, expressly published service footprint, the operator's instruction for finding its locations, schedule-channel type, menu routes, booking routes and ordering routes. Sixteen comparison fields sit alongside field-level provenance and observation dates. Operator names are identifiers, not a claim that every business currently runs a public truck.

The review retained 55 source records, including the prior edition's historical event evidence. Thirty-eight operator-page retrievals completed in this revision; one additional guessed Fava Pot route returned 404 and is not used as evidence. Relevant text and links were read from the operators' own websites. Fava Pot's menu, catering and ordering routes were read from page data published in its own HTML. Raw page bodies remain in the working research folder and are not part of this distribution.

## How schedule channels are assigned

- **Website calendar:** the operator directs visitors to a calendar or truck-schedule page. The channel can exist even if no entries are readable in the retrieved page.
- **Named social profile:** the operator's website explicitly directs readers to a named or linked profile for location or schedule updates. URLs are preserved as published. No social platform, profile or post was opened, scraped or reproduced.
- **Weekday page:** the operator publishes a weekday selector for trucks without assigning calendar dates to those cells.
- **None found:** no usable location-publication instruction was established in the pages checked. Generic footer social icons, an empty Events heading, private-event availability and a storefront address do not qualify.

An operator can have more than one channel. The channel counts therefore overlap. An instruction establishes where to check, not that a truck will be present, a social account is active or a menu is available for a particular service.

## Links and unknowns

Every link contains its operator-website evidence IDs, a label, its purpose and any material scope limit. Some booking and ordering destinations are external platforms explicitly linked by the operator; this is recorded. Their transactions were not tested. Where a website publishes two different ordering routes, both remain visible with a note rather than guessing which is current.

Menu outlines, catering menus and storefront menus are labelled as such. A menu URL does not imply a current truck menu. Empty arrays or null values mean that the item was not established in the checked pages. Missing data are never converted to zero, a closed-business conclusion or a fabricated URL. A generic contact form is not automatically a booking channel.

DC, MD and VA tags require explicit service-region wording. An office, kitchen or restaurant address, telephone area code, a past festival or an unexpanded DMV label does not establish all three jurisdictions. A geography statement retains its original scope even when no filter tag can responsibly be assigned. Cuisine labels summarize the operator's own food descriptions; they are not dietary-suitability assurances.

## Dated public stops found in this edition

The two qualified Virginia stop records from the prior edition remain unchanged under `index.json.dated_public_stops_appendix.rows`, with their original dates and evidence. They are an edition appendix, not current tool output. The operator finder does not read this appendix. There is no events file, dated-stop display or expiry timer in this delivery.

## Files, reproducibility and licensing

`index.json` is the complete record, including field evidence and the dated appendix. `index.csv` is the operator-only tabular export; nested links are represented as documented by `CSV_SCHEMA.json`. `source-ledger.json` records source URLs, response hashes, retrieval times, access outcomes and relevant outbound links observed on operator websites. `hashes.txt` covers the asset files after final export.

Original factual annotations and this compilation are **CC BY 4.0**. Operator text, menus, photographs, logos and platform content retain their owners' rights. No permission to republish those materials is implied. This package distributes original annotations and links, not operator posts or menu copies.

## Limits that remain

The sample is not a complete regional register or a verification of active public service. Dynamic calendars may require a browser or fail to expose entries. Social destinations may move or require an account; they were not checked. Prices, collection availability, food availability, access conditions and travel times were not revalidated for the finder. Human source-review sign-off remains unsigned.