Trace where a block came from
folio_provenanceTrace a block to its source file, lines, last change, embedded data files, queries, and claim checks. Explain why a number or table reads as it does or if a figure still matches its data.
Instructions
Trace one block of a page to its origin: the file and lines it comes from, when it last changed, the data files and queries behind its embedded tables and values with when each changed, and each figure in it checked against its data. Use it to explain why a number or table reads as it does, or whether a figure still matches its data; take the block's id - and, for a block an include brings, its source - from folio_document's page. For every problem in the folder at once use folio_health. An id not on the page is an error. Answers {source, kind, lines: [first, last], changed: ISO time, included: {section} for an included block, data: [{reference, files: [{path, changed}], query, error}], claims: [{figure, reference, state: matching, contradicted or unchecked, live: the data's value, reason, deliberate: true when left unchecked by choice, as a range is}], conventions}. A list cut to fit one answer adds omitted, the entries each list left out, and narrow, how to ask for less.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | The page's path, relative to the served folder or absolute under it, such as notes/plan.md | |
| block | Yes | The block's id, 8 hex characters, as folio_document lists it | |
| source | No | The file the block's text comes from when an include brings it onto the page, as folio_document's page names it; omit for the page's own blocks |