Origin
Hygenie exists because the gap between a workspace full of files and a workspace organized around its actual structure is too wide to cross by judgment alone. People know their files are disorganized. They also know that most file-organization tools are too aggressive, too presumptuous, and too willing to act on AI confidence that turns out to be misplaced. The result is that the disorganization persists, because the cost of an over-eager tool is higher than the cost of clutter. Hygenie was built to be the conservative option. It proposes. It does not execute without review. It refuses to override the user's existing structural decisions. It treats every file as innocent until classified, and every classification as advisory until confirmed.
Design
Two modes serve two different cadences. Maintain mode handles routine cleanup — new loose files routed into the existing project structure, README-driven where READMEs exist, falling back to extension-based category routing otherwise. Deep mode handles initial setup or annual restructuring — files clustered into project folders from scratch, summarized, classified, planned, reviewed, iterated against natural-language feedback, executed only on explicit user command. Both modes operate through a plan-review-iterate-execute workflow. Files do not move silently. AI proposes; user disposes.
Structure
Defense‑in‑depth runs six gates on every operation. Pre-routing rules catch obvious cases before the AI is consulted. AI clustering proposes structure. Soft validators warn on anomalies. Hard validators block on policy violations. Post-processors apply downstream corrections. Forced KEEP IN PLACE rules name six categories of protected paths the AI cannot override regardless of what it thinks should happen. Sensitivity classification runs alongside, sorting every file into one of six categories — PII, financial, medical, legal, business, or none — surfaced inline in the plan, in the sensitivity summary section, and in the conditional sensitivity section of every folder README. Conservative-by-default routing means that low-confidence destinations default to CATEGORY_FOLDER or Inbox rather than to a guess. File contents stay on the user's machine; only summaries reach the model.
Defense
The defensibility claim is structural conservatism, end to end. Six gates per operation means that no single layer of judgment is load-bearing. AI confidence in the clustering stage does not translate into action in the execution stage without surviving the validators and the protected-path rules.
Sensitivity classification is informational at the file level and behavioral at the validator level — sensitive content routed to a non-protected destination triggers a soft validator that holds for review. The KEEP IN PLACE rules are not heuristics; they are protected categories that block regardless of any other signal. The plan-review-iterate cycle ensures that the user's natural-language instructions are folded back into the next planning pass before execution. The system is not aggressive because aggression in this domain produces irrecoverable damage to user trust. It is conservative because conservatism is the structural property that makes the tool usable at all.
Status
Active. Browser-based PWA built around the File System Access API. Six-gate operation pipeline operational. Six-category sensitivity classifier integrated into plan output, README generation, and validator chain. Maintain and Deep modes shipped.
