... provenance record of an unreviewed process, which is a different kind of liability. Comment from Dev Grover(@grover___dev): @lyshen   @praveen62  Agreed, that s where provenance gets difficult. It s not enough to know where a number originally came from. You also need to understand how it was reused, transformed, summarized, and approved across the workflow. To me, the bigger challenge is preserving the reasoning and decision context around the output, so the final report can still ... ... tables, summaries, and rewritten explanations, provenance stops being only where did this output come from? and becomes can we still trace how this specific fact transformed across representations? I think trustworthy lineage eventually needs to preserve not only the original

... Approval push with full proposed-action payload, resolvable in place. Needs-input push that labels simple-vs-complex so you know whether to answer or open. Completed silent list. That's four different treatments, and you basically specced them. That's exactly the shape Pushary is built around, so genuine last question: for needs-input, how would you want it to decide simple-vs