Coverage roadmap: what autumn brings to each door

Roadmaps earn trust by being concrete and revisable at once, so below stands what this desk intends to add during autumn, filed under the door each piece will land behind. Dates attach to seasons, not weekdays; pieces appear when finished rather than bribed onto schedules nobody keeps honestly.

Storage Basics gains three explainers

Planned additions cover APFS volumes and how shared space confuses single-drive arithmetic; Spotlight indexing storms and why rebuilding one shrinks apparent growth temporarily; and network home folders for households running more than one Mac against a common store. Each follows the plain-measurement habit codified in the first basics entry.

Cleanup Guides deepen cache and archive work

A browser-by-browser cache atlas replaces forum folklore with per-engine boundaries matching the etiquette set in the safety guide; a mail-storage diet walks offline attachment behavior end to end; and an export-and-archive pattern shows moving finished projects cold without orphaning references, extending relocation care into deep storage.

Tools and hardware doors get field reports

The analyzer comparison in its criteria-first form gains a companion field report format: same drive, same week, walked by different instruments, receipts logged on the shared worksheet. Hardware coverage adds docked-versus-portable duty guides and a straightforward NAS primer for household backups positioned alongside direct-attach options already surveyed.

How the roadmap bends without breaking

Two forces reorder plans here: operating-system behavior that invalidates a draft, and reader mail surfacing a question ahead of its scheduled piece. Both outrank the calendar. A planned explainer drafted against beta software ships only once behavior stabilizes on release builds, and a question asked three times in one week skips its queue entirely. Readers holding such questions should not wait for autumn either; the support mailbox counts every message toward that skip threshold, per the response duties declared in the editorial policy.

The kit grows two sheets

Field kit revisions arrive when method changes, and two are queued: a household inventory sheet aggregating multiple machines beneath one roof, and a before-you-buy card summarizing capacity arithmetic including the purgeable haircut taught in its explainer. Revision lines dated plainly will live atop each file from the kit page, no silent swaps.

What deliberately stays outside the map

Scope holds a negative space too, worth publishing alongside intentions. No enterprise storage management, no data recovery theater for mechanically failed drives, no Windows coverage except where switchers need translation, and no security-adjacent scare content whatever its traffic reputation. Frontiers documented here echo the boundaries declared in the masthead's own description, because a roadmap that erases its borders invites everything.

Ground rules unchanged

Nothing above constitutes sponsorship; unsigned pitches travel to the support address like any other mail, handled per published disclosure terms. When autumn items ship, the feed registers them through channels listed at Follow the desk, and this note gains an addendum rather than a rewrite, preserving the original record intact. Plans in pencil, accountability in ink: that ratio has served every honest desk before this one and should serve it here through the season ahead.

One metric this desk will not chase

Publication counts tempt small sites toward padding, so refuse them out loud: no piece ships to justify a schedule, no door inflates with stubs to look stocked, and no worksheet gets versioned for the appearance of motion. Autumn succeeds if its few additions each survive a year of their own advice, which readers judge better than any counter. The roadmap stays pencil as promised; addenda will note bent plans beside kept ones, both honestly dated, because a record that only records wins is marketing wearing a notebook's clothes.

A last word on steering any of it: the roadmap bends fastest toward documented need. Three messages asking the same question outrank a penciled plan; one broken-link report outranks everything; and disagreement backed by measurements beats agreement backed by politeness wherever this desk weighs contributions. None of that requires more effort than mailing the support address, whose queue treats roadmaps, corrections and compliments identically, reading all three before autumn decides what ships next under these doors.