{"product_id":"ae4755-benedikt-datewell","title":"Benedikt Datewell · File Tagger","description":"\u003cdiv class=\"pro-head\"\u003e\n\u003cdiv class=\"face\" data-face-handle=\"ae4755-benedikt-datewell\"\u003e\u003c\/div\u003e\n\u003cdiv class=\"who\"\u003e\n\u003cp class=\"headline\"\u003eFile Tagger\u003c\/p\u003e\n\u003cp\u003e\u003cspan class=\"lvl lvl-file-worker\"\u003eFile Worker · G1\u003c\/span\u003e \u003cspan class=\"dchip\" style=\"--d:#649BB5;--di:#294D5E;--dw:#ECF5FA;--dl:#C1D4DE\"\u003eThe Ground Crew\u003c\/span\u003e\u003c\/p\u003e\n\u003cp class=\"note\"\u003eWork style: The Archivist · Lot AE-4755 · Cohort Five\u003c\/p\u003e\n\u003cp class=\"only\"\u003eWorks only in Claude\u003c\/p\u003e\n\u003c\/div\u003e\n\u003c\/div\u003e\u003cp class=\"quote\"\u003e“It's written down. Here's when and why.”\u003c\/p\u003e\u003ch2\u003eSummary\u003c\/h2\u003e\u003cp\u003eBenedikt can tell you what changed, when, and why, for every file it has touched. As a file worker, Benedikt does one file job as code: dry run first, then the job, then the tally with proof. Best at traceability. Tags files for finding later: in a tags.json beside them, or in the file name.\u003c\/p\u003e\u003cdiv class=\"glance\"\u003e\n\u003cdiv\u003e\n\u003cb\u003eBest at\u003c\/b\u003eTraceability.\u003c\/div\u003e\n\u003cdiv\u003e\n\u003cb\u003eWatch for\u003c\/b\u003eBenedikt's record-keeping adds overhead. Say when a log isn't needed.\u003c\/div\u003e\n\u003c\/div\u003e\u003cp class=\"example\"\u003eGive Benedikt a job like this: “Benedikt, given a messy folder of 300 files, run the file tagger job as a dry run, fix what the plan flags, apply it, and hand back the tally with its proof.”\u003c\/p\u003e","brand":"aiemployees · Lund Studio","offers":[{"title":"Default Title","offer_id":57984394723511,"sku":"AE-4755","price":24.0,"currency_code":"USD","in_stock":true}],"url":"https:\/\/aiemployees.store\/products\/ae4755-benedikt-datewell","provider":"AI Employees","version":"1.0","type":"link"}