Wednesday, August 12, 2026 The Throne in Heaven Revelation 4:1 (NIV) “After this I looked, and there before me was a door standing open in heaven. And the voice I had first heard speaking to me like a trumpet said, ‘Come up here, and I will show you what must take place after this.’” Heavenly Father, Thank You for opening our eyes to Your mighty presence and the glory of Your throne. Help us to listen for Your voice and respond with faith and obedience. Lift our hearts higher as we fix our eyes on heaven and remain focused on the things that are eternal. Teach us to trust in Your perfect plan for our lives. In Jesus’ name we pray, Amen.

My File System Was a Disaster. Here's the One I'm Building to Replace It. I want to be upfront about something before I get into this: what follows is not a finished system I've been running for years and am now generously revealing to you. It's the system I'm actively building right now, because the old one finally broke under its own weight. Here's what broke it. I went looking for a cover concept file from an earlier book. It wasn't in the book folder. It was in a "Graphics" folder from eight months ago that also had three other books' covers in it, none labeled clearly enough to tell them apart at a glance. The marketing copy for that same book was in a completely different folder tree, because I'd started using a new tool partway through and never went back to reconcile the old stuff. Fifteen minutes of searching for one file I knew existed. That's the tax you pay for not deciding on a structure up front, and I'd been paying it quietly for a long time. So I sat down and asked the obvious question: what's actually going in these folders, and what's the smallest set of rules that keeps it findable six months from now when I've forgotten the details? The core idea: Projects is the top, then everything nests by type Books aren't the only thing I'm keeping track of. There are coding projects, there's a growing pile of AI prompts and skill files, there are short stories that don't need the full novel treatment, and there's a permanent junk drawer of half-formed ideas that aren't committed to anything yet. Trying to organize all of that around "books" was the first mistake, because a lot of my actual work isn't a book. So the true top level is just **Projects**, full stop. Not around the tool that made something, not around the date, not around whether it's "writing stuff" or "marketing stuff." Whatever kind of thing it is, fiction or code or a stray idea, it lives inside its own project folder, not scattered across whatever pile happened to be open when I made it.

Do we need to have a class on book covers in WCP? There are a couple ways to do it and I'm sure I'm not doing it the best way yet, but I'm glad to share what i know in a Q&A format. I just need to know a good day/time for the most folks to participate and we'll record it for the rest. I'm getting pretty good results from the ones I show you all with very little effort. I'm working on a way to give more/easier control over type by using layers, and image under the type. These are really low effort below. They all could use some touchups.

Stop Guessing at Your Comps — Reverse-Engineer Them Instead Topic: Using Book Reporter (CONAN) and Series Reporter (SONJA) to forensically analyze comp titles before you write a word of your own story The problem this solves Most of us pick comp titles the same way: we read a book we loved, we feel something, and we say "I want to write something like that." Then we sit down to plan our own story and realize "like that" was never actually specific. Was it the pacing? The trope execution? The voice? The way the series built across four books instead of one? Vibes aren't a blueprint. If you can't name exactly what a comp title is doing — structurally, at the sentence level, across its beats — you can't reliably reproduce what made it work, and you definitely can't improve on it. That's what Book Reporter and Series Reporter are for. They're the forensic layer of the Professional Writing System — the tools you run before Phase 1 (Story Development Room) to turn "I want something like this" into an actual architecture you can build from. The two tools, and how they're different Book Reporter (CONAN) analyzes one book. He reads it the way a mechanic pulls an engine — not to admire it, but to understand exactly what's load-bearing and what's cosmetic. He produces a Forensic Morphology Report: 15 layers covering structure, character architecture, prose voice, world-building, tropes, emotional design, and hooks, plus: A Beat Rhythm Map — a chapter-by-chapter tension chart that shows you exactly where the book accelerates, where it breathes, and where it stalls (dead zones, flagged by name) Genre Beat Benchmarks — where this book's inciting incident, midpoint, dark night, and climax land as percentages of total length, compared against genre norms A Prose Quality Score Card — eight dimensions scored 1–10, so "the writing is good" becomes "voice distinctiveness is an 8, but foreshadowing/payoff execution is a 4, and here's why" A Reconstruction Brief — the condensed DNA of the book (genre, structure, archetypes, thematic argument, world type, tropes) formatted to drop directly into Story Development Room, plus 2–3 original seed concepts that share the book's structural DNA without copying it

Tuesday, August 11, 2026 Revelation 2:7 (NIV) “Whoever has ears, let them hear what the Spirit says to the churches. To the one who is victorious, I will give the right to eat from the tree of life, which is in the paradise of God.” Heavenly Father, Open our ears to hear Your voice and our hearts to obey what Your Spirit is saying to us today. Help us stay faithful, endure with perseverance, and remain victorious through every trial. Thank You for the promise of eternal life and the blessing of the tree of life in Your paradise. Guide our steps and help us faithfully follow You each day. In Jesus’ name we pray, Amen.