The forms in which ESI will be produced are confirmed, ideally agreed during initial planning and before review so that review need not be repeated. The candidate forms are those part 1 describes: native files as created and maintained (often best for spreadsheets and small databases, cheap to produce but possibly needing the original or proprietary software to open, with care that conversion does not lose metadata); near-native forms for material that cannot be viewed without some conversion, such as e-mail extracted to individual files and large databases exported as delimited text, possibly with the schema, data dictionary, metadata or software, or as spreadsheets; image or near-paper forms rendered as non-editable files, where print settings can alter or omit data and expertise is needed; and hardcopy, which carries the same risk of loss; or a combination of these, as the parties agree.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.