33: GLOW for Files - transcript
Jessica: The QUILL Cast, episode thirty-three. I'm Jessica. Yesterday GLOW reviewed what's in your editor; today it grades the files you're about to send: Word, PowerPoint, Excel, PDF, EPUB.
Liam: I'm Liam. The two new commands, same menu, Tools, GLOW: Audit File and Fix File. These run the shared GLOW engine, a deeper analysis machine that understands structured document formats from the inside.
Jessica: Audit File first. Pick a file on disk, and the parse runs in the background, your editor never freezes, part-four muscle memory, background work never blocks. Back comes a report with a score out of one hundred, a letter grade, and every finding listed with the same rule-severity-suggestion anatomy you learned yesterday.
Liam: The grade changes behavior, and that's why it exists. Fix twelve findings is a chore; get the B to an A is a game. And before you send that report to your boss or that handout to your class, one Audit File is the pre-flight check: you know what you're shipping, with a number attached.
Jessica: Now Fix File, which owns my favorite safety property in the entire product: it is physically incapable of damaging your original. It always writes the repaired version as a new copy beside the source, report dot docx becomes report dash accessible dot docx, it confirms that destination with you before running, and when it finishes, it opens the post-fix audit so you can verify the improvement, new score, new grade. The original file is never touched. Not never usually. Never structurally.
Liam: Run the loop out loud once: audit the docx, sixty-eight, C. Fix File, confirm the destination, listen to it work. Post-fix audit: ninety-one, A minus, three findings left, all judgment calls for a human. Open the accessible copy, handle those three yourself, send. That's institutional-grade document remediation, from a keyboard, by ear.
Jessica: About the engine underneath, because trust needs specifics. The structured-file analysis comes from the shared GLOW engine, an optional component QUILL installs with its glow extra, and when it's absent, QUILL degrades honestly, an engine-not-installed report, never a crash or a mystery.
Liam: The engine updates on its own schedule, and the update path is a small trust masterpiece: Help, Check for GLOW Updates runs only when you ask, the download is confirmed separately from the check, the manifest is cryptographically signed, every component is checksum-verified, and a failed install rolls back automatically to the bundled engine. Episode two's download trust model, at maximum strength.
Jessica: Privacy posture, stated plainly: the entire default GLOW workflow, both episodes' worth, runs on your machine. The engine has optional networked helpers, AI alt-text generation, personal-data redaction, language processing, and they are structurally off: unreachable until you explicitly consent, per action. The audit of your confidential report stays as private as the report.
Liam: The workflow this unlocks for organizations deserves naming: one person with QUILL can be the accessibility gate for a whole team's documents. Files in, graded and repaired copies out, findings lists as teaching material for the authors. What used to require enterprise remediation software is now File, Audit, Fix.
Jessica: Homework. One: run Audit File on any Word document and receive your first grade, with humility, we all start humbled. Two: Fix File it, verify the original is byte-for-byte untouched, and compare the before and after scores. Three: run Check for GLOW Updates once, just to hear the consent choreography.
Liam: Next episode: the format where structure meets paper, braille, and production-grade embosser proofreading.
Jessica: I'm Jessica.
Liam: I'm Liam. Grade it before they read it.