.plan.jsonld, following the W3C PROV provenance standard and the P-Plan vocabulary for plans. Each table row becomes a step, planned links between steps are recorded as named connections, and memos, image captions and inter-step text are included so an AI or human reader can compare what was planned against what actually happened. Rows without notes, or whose notes are trashed or archived, still appear as steps without note contents, and duplicate row names are not exported. After weeks of trial and error, you may want to hand the work over to someone, or ask an AI "did this go as planned?" But when the record is split into one note per step, handing over the notes one by one leaves the other side to rebuild the planned order of the steps and what passed between them. I have been there myself. I kept the record of each step as a Word file in a folder, while the plan as a whole mostly lived in my head. When I handed things over, the only way to pass on the connections was to explain them. In Graphium, the plan that used to live in your head can be written down as a table in a plan note. Then Export plan provenance in that note's ⋯ menu saves the provenance of the plan and its step notes together as a single file, <title .plan.jsonld . The export follows the W3C provenance standard PROV and a vocabulary for plans P-Plan . Each row of the table becomes a step of the plan, and the planned links you drew in the step graph go in as connections between steps, along with the names you gave them. What the notes actually passed to each other carries the same names. I thought that putting the plan and what really happened side by side in the same words would let anyone read, outside Graphium too, whether things went as planned. Memos, image captions and the text you wrote between steps are included as well, so an AI reading the file sees what you wrote, not only the structure of the labels. Rows with no note yet, or whose note is in the trash or the archive, still appear as steps, but without the contents of a note. A row whose name appears twice is not exported. Exporting a plan's provenance is covered in the "Labels & provenance" page of the manual. Exporting a whole plan came in v0.104.0 2026-10-29 . https://kumagallium.github.io/Graphium/manual/labels-and-provenance https://kumagallium.github.io/Graphium/manual/labels-and-provenance Graphium is open source on GitHub.

Hand a plan and all its step notes to a person or an AI as one file The open-source Graphium project released a v0.104.0 feature that exports a plan and all its step notes as a single file, .plan.jsonld, following the W3C PROV provenance standard and the P-Plan vocabulary for plans. Each table row becomes a step, planned links between steps are recorded as named connections, and memos, image captions and inter-step text are included so an AI or human reader can compare what was planned against what actually happened. Rows without notes, or whose notes are trashed or archived, still appear as steps without note contents, and duplicate row names are not exported. After weeks of trial and error, you may want to hand the work over to someone, or ask an AI "did this go as planned?" But when the record is split into one note per step, handing over the notes one by one leaves the other side to rebuild the planned order of the steps and what passed between them. I have been there myself. I kept the record of each step as a Word file in a folder, while the plan as a whole mostly lived in my head. When I handed things over, the only way to pass on the connections was to explain them. In Graphium, the plan that used to live in your head can be written down as a table in a plan note. Then Export plan provenance in that note's ⋯ menu saves the provenance of the plan and its step notes together as a single file, <title .plan.jsonld . The export follows the W3C provenance standard PROV and a vocabulary for plans P-Plan . Each row of the table becomes a step of the plan, and the planned links you drew in the step graph go in as connections between steps, along with the names you gave them. What the notes actually passed to each other carries the same names. I thought that putting the plan and what really happened side by side in the same words would let anyone read, outside Graphium too, whether things went as planned. Memos, image captions and the text you wrote between steps are included as well, so an AI reading the file sees what you wrote, not only the structure of the labels. Rows with no note yet, or whose note is in the trash or the archive, still appear as steps, but without the contents of a note. A row whose name appears twice is not exported. Exporting a plan's provenance is covered in the "Labels & provenance" page of the manual. Exporting a whole plan came in v0.104.0 2026-10-29 . https://kumagallium.github.io/Graphium/manual/labels-and-provenance https://kumagallium.github.io/Graphium/manual/labels-and-provenance Graphium is open source on GitHub.