Cooking Robot Procurement: Separating Log Records from Provenance Claims

Procurement teams evaluating robotic cooking systems often encounter two different kinds of technical documentation that look alike but serve distinct purposes. One is the runtime logging stream generated by the machine's control software. The other is a structured provenance record describing how a food item or a data object came to exist. For buyers on cookingrobot.net, the practical task is to separate a published fact, its date, scope and source from editorial inference. This article explains how the two supplied official references describe logging and provenance, and how a procurement reviewer can use them without overreading either document.

What the ROS 2 Logging Reference Actually States

The official ROS 2 Jazzy documentation on logging, available at the ROS 2 Jazzy logging source, describes the logging subsystem in a robotics framework. The document is part of the ROS 2 documentation set for the Jazzy distribution. Its scope is the delivery of logging messages from nodes in a ROS 2 graph to targets such as the console, disk files and the /rosout topic. The source states that severity levels are DEBUG, INFO, WARN, ERROR and FATAL in ascending order, and that a logger processes messages at or above a chosen level. It also documents logger name hierarchies, per-node configuration and environment variables such as ROS_LOG_DIR and ROS_HOME. That is the published fact: a description of a software logging mechanism, its configuration surface and its severity model. It does not itself assert anything about food safety, recipe execution or commercial kitchen compliance.

Date, Scope and Source Boundaries in the Logging Document

The reference is a source file in the ROS 2 documentation repository for the Jazzy branch. The date of the content is tied to that documentation branch rather than to a product launch by any cooking-robot vendor. The scope covers client libraries in C++ and Python and the shared underlying configuration, not the mechanical behavior of a stir-fry module or a conveyor. When a procurement file quotes "the machine logs at INFO level," the quoted material should name this document and branch as the source, state that the scope is the logging subsystem, and mark any further step—such as "therefore the fry cycle was validated"—as inference by the reviewer. The logging reference tells a buyer what messages can appear and where they go; it does not tell the buyer that those messages prove a cooking outcome.

The PROV Primer and the Meaning of Provenance

The second supplied reference, the PROV Model Primer, was published by the W3C as a Working Group Note on 30 April 2013. Its stated purpose is to introduce the PROV data model for provenance interchange on the web. The document defines provenance as the origins of digital objects and describes core concepts including entities, activities, usage, generation, agents, responsibility, roles, derivation, revision, plans and time. The primer says provenance records can be used to understand how data was collected, determine ownership, judge trust, verify that a process complied with requirements, and reproduce how something was generated. The date and scope are explicit: a 2013 W3C Note about a general data model, not a specification written for kitchen robotics. A procurement reviewer citing it should record 30 April 2013 and the note status as the published frame, then separately label any application to food production as an editorial adaptation.

Entities and Activities Versus Log Lines in a Kitchen Cell

In PROV terms, an entity is a thing such as a data item or physical object, while an activity is something that occurs over time and uses or generates entities. The primer's example set includes how records describe influence and change. For a robotic cooking cell, a tray of prepared ingredients could be treated as an entity and the heating cycle as an activity in a provenance-style model built by the buyer. The ROS 2 log, by contrast, may contain timestamped INFO or WARN lines about the node that drives the heater. These are not the same artifact. The log is a stream of software messages whose format and routing are described by the ROS 2 reference; the provenance record is a structured account of what acted on what, when and under whose responsibility, as described by the PROV primer. A useful procurement question is which of the two the vendor actually supplies, and in what form.

Using Both References Without Inventing Vendor Claims

A reviewer might see a cooking-robot brochure saying the unit keeps "full traceability." The two official sources do not substantiate that marketing sentence by themselves. The ROS 2 document shows that a node can emit DEBUG through FATAL messages to console, disk or /rosout, and that logger levels can be set per node. The PROV primer shows a general model for describing entities, activities and agents. Combining them to say a specific robot produced a PROV-conformant record of every recipe step is a hypothesis, not a published fact from either source. Suppose a buyer writes in an evaluation memo: "Because the ROS 2 logger writes to disk and PROV describes activities, the unit therefore meets our allergen-separation record requirement." That is a hypothetical example and should be labelled as such, because neither supplied document states anything about allergens or about that unit's record format. The honest version separates the mechanism described in each source from the buyer's own compliance conclusion.

Putting the Distinction Into Procurement Files

For teams maintaining acceptance records, the useful method is a two-column note. In one column, write the sourced fact: which document, which date or branch, which scope and which passage. For example, the ROS 2 Jazzy logging source says severity levels are five named values and that targets can be individually enabled per node. The PROV primer, dated 30 April 2013, defines entities, activities, agents and the listed uses of provenance. In the other column, write the inference: what the procurement team concludes about a specific machine, and what evidence beyond those documents would be needed. Internal reviewers on this site can cross-check related device categories through the type 14 listing, the type 25 listing and the type 17 listing to keep terminology consistent across evaluations. The outcome is not a longer file but a clearer one, where a log line about a heating node is never silently promoted into a provenance claim about a served meal.