gercyc gives workflows their own filing cabinet
Workflows in this fork can now carry their own persistent attached files, instead of treating documents as one-off inputs.
gercyc has built a net-new feature that lets each workflow hold onto a set of attached assets that stick around - a dedicated panel on the workflow page, a full set of controls to add and manage them, and storage behind the scenes. Think of it as giving every matter or process its own folder of reference documents that travels with it, rather than re-uploading the same files every time.
The work is wired into this fork's own database setup and ships with both English and Brazilian-Portuguese labels, so it's tied fairly tightly to gercyc's particular build. Anyone eyeing it for their own fork should look at it alongside the broader self-hosting changes, not as a standalone drop-in.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?