«Friday Ride» helps users plan a short, car-free trip. Its value lies in unifying schedules, city activities, and a complete budget into one actionable plan. The project maintains the concept of a first assignment. Here, the editorial architecture has been developed: data sources, processing order, and guidelines for future automated services.

The general institutional schedule does not always specify individual visit details. For instance, the Stables website lists separate weekends for certain exhibitions and technical closures on the last Friday of the month from 10:00 AM to 1:30 PM. Therefore, the editor checks the required exhibition and date, and adds exceptions to the standard schedule.

One itinerary is linked to multiple pieces of information: flights, seating availability, costs, and weather. Each piece of information stores its own reference link and verification time. This allows the return ticket price to be updated without losing the trip’s itinerary, and allows users to see which publications are using the changed record. The seat availability field is stored separately from the price field.

The schematic includes six automated modules. The assembler brings the data to a common format, the calculation module suggests options, and the AI prepares the text. The bot responds to a personal request, the publisher sends the approved edition, and the monitor tracks changes. Fact-checking and the decision to publish remain with the editor. Manually entered data undergoes the same structural checks as API responses.

Status applies to a specific version of the entry. If the price or train time changes after verification, the confirmation for that version becomes invalid. Source conflicts are resolved by an editor: they preserve both entries, clarify details with the carrier or organizer, and document the reason for the chosen resolution. Automation will not select a convenient figure merely because it fits the budget.

Example of normalization: a duration of 5,400 seconds becomes 90 minutes; the original value and source are retained. The values «no spots available, ” „source unavailable, ” and „availability unverified“ carry distinct statuses. None of these constitute approval for publication. Access keys are stored outside of the AI input data and response logs.

Each budget item includes a total amount, a quantity, a designation («per person / per group»), and a basis—either a verified price or an editorial estimate. Room and board costs are not multiplied again by the number of occupants. If a mandatory item is unknown, the system returns an incomplete budget along with a list of missing data. Estimated food and contingency expenses are visible to the reader as a guideline.

The editor receives two parts of the result: the publication text and an internal «approval—source» table. The reader receives the publication with the necessary links. The automated verification compares the numbers, addresses, and dates in the draft with the original records; discrepancies return the text for revision. Illustrations do not serve as factual confirmation.

Example response when data is insufficient: «I found a program for the trip to Tula, but the price for the return ticket has not been confirmed yet. I cannot give you the full amount right now. You can check the tickets with the carrier or choose a different route.» The response maintains the request conditions and explains the next step. Selection does not mean purchasing or reserving tickets.

The Friday edition is scheduled for 12:00 Moscow time. Sending to each channel is accounted for separately. For VKontakte, the editor receives the same approved text and layouts for manual placement. If the data cannot be updated, the route is not sent automatically: the editor selects different material or reschedules the edition.

Example correction: «Updated at 3:40 PM: The museum canceled the session. The program was reduced to a walk and coffee stop, and the entrance fee was removed from the budget.» This entry appears after editor approval. If the cancellation makes the trip unfeasible, the route is removed from the selection, and the published post receives a prominent warning.