Browsed by
Tag: architect of worlds

Special Status Report for Patrons (29 June 2023)

Special Status Report for Patrons (29 June 2023)

This one is specifically for my patrons (and regular blog readers who might be interested in my creative projects).

As I mentioned on 23 June, we’re currently fighting a flooded basement which has knocked out my primary living area and home office. I haven’t been entirely cut off from the Internet, obviously, but I’m spending 12-15 hour days just keeping up with my day job and doing pack-and-move work here. Not much time left over for creative work, so (e.g.) Architect of Worlds is pretty much on hold for now.

Architect didn’t get enough new layout done before the disaster struck to justify a new update. There will therefore be no free update for patrons at the end of this month.

I also may or may not generate a planning message for July at the beginning of the new month. Things are too much in flux for me to be able to plan anything with a straight face.

The primary effort right now is to prepare our basement for a crew who will be coming in, starting on 5 July, to do foundation repair and waterproofing work. To that end I’ve packed up just about the entirety of my library and moved it to storage. Over the next few days we’ll be policing up any remaining small items, and moving the larger pieces of furniture aside so the crew has access to get their work done. After the foundation work is finished, we’ll need to paint the new drywall, get all the carpeting replaced, and then move everything back into place. I expect all this to take up the bulk of the month of July. It might even overlap into the first week or so of August.

I’m not entirely cut off. We’re also working to ensure I have a small home-office space elsewhere in the house while the work is being done. If that works out, I may be able to get back to some creative work in a limited way, even while all the repair and rehab are being done. I’ll keep everyone posted as things progress.

Status Report (23 June 2023)

Status Report (23 June 2023)

Only a short note today, to report that I’m likely going to be getting little or no creative work done for at least a few days, possibly as much as a few weeks.

My living quarters and home office are in the finished basement of our home, and as of yesterday afternoon, that basement is being flooded. So far it’s not too bad – only a few of my possessions have been water-damaged, and the bulk of my library of books and tabletop games is safe for the moment. On the other hand, the bulk of the carpeting is water-logged and we’ve had to shift a lot of furniture around. As I sit at my workstation right now, the carpet under my feet is soggy and wet.

(No, the image above is eye-catching, but it’s not actually that bad. Even if it’s starting to feel that way.)

We have a specialist coming this afternoon to make an assessment and estimate what would be involved in repairs. I suspect we may need to move most of the furniture and items from my space into storage for at least a few days, cutting me off from my primary work machine and resources while repairs get done. In particular, if the flooding worsens, we may need to move everything to save my equipment and prevent significant losses to my library. In the worst-case scenario, it may be several weeks before things are back to normal.

All of which is to say that work on Architect of Worlds and other projects is at a standstill until I get my space back. I can’t even promise any free updates for this month, and I may miss my monthly book review for June. We’ll see how things go. I’ll post again as soon as I know more, and have some idea how long I’ll be offline.

Status Report (11 June 2023)

Status Report (11 June 2023)

Some quick notes on the state of Architect of Worlds.

While I was doing further layout, I realized two things. First, the extended examples at the end of each section of the main design sequence were a mess – I had let them get out of synch with each other and with the design rules while those evolved. Second, I wasn’t happy with some of the previous layout; in particular, I’ve decided that I would prefer to have every step in the design sequence start at the top of a page, allowing more space for interior art when the layout is finished.

I’m going to have to correct both of those items at some point, so I’ve decided to go back and do it now. I’ve been reworking the “Arcadia” extended example in particular, since that was the one that got into trouble. Once that’s done, which may be as early as today, I’m going to go back and start reworking the layout through the design sequence. That may lead to some repagination, and in particular I may end up having to move a lot of the tables around. I may take the opportunity to tweak the master page setup too.

All this may take me a few more days, during which I won’t be laying out any new material, but the book will look better and more coherent in the long run. It may impact my tentative milestones for June, though.

Planning for June 2023

Planning for June 2023

May was a big month at my day job, which left me short of spoons for creative work. I didn’t hit my objectives for Architect of Worlds, so that book is a bit behind its notional schedule. I did manage to redesign a major step in the design sequence and get about ten pages total laid out, so progress didn’t halt entirely. Meanwhile, I managed to post two book reviews last month.

I still have some research-and-revision work to do on the last few steps in the design sequence, although I did make a big chunk of progress on that in May as well. In particular, I think I see ways to simplify the math for measuring greenhouse effect due to carbon dioxide, and that should streamline a couple of steps as well as possibly improve the accuracy of the model. Meanwhile, Step Thirty-Two of the current draft sequence is kind of a mess, so I hope to get it cleaned up a bit before finishing the layout for that section of the book.

So here’s the plan for June:

  • Top Priority:
    • Architect of Worlds: Complete revisions for the mini-models for a world’s atmospheric greenhouse effect, specifically for Step Thirty of the design sequence.
    • Architect of Worlds: Extensively revise Step Thirty-Two of the design sequence (variations in local climate).
    • Architect of Worlds: Continue work to design and lay out the finished book. Plan to finish through page 132 (out of approximately 180), or the end of the Designing World Surface Conditions section. May continue past that point if time remains in the month.
  • Second Priority:
    • Danassos: Continue work on the new draft of Twice-Crowned.
    • Danassos: Rebuild the alternate-historical timeline.
    • Human Destiny: Continue compiling material for the eventual Atlas of the Human Protectorate.
    • Human Destiny: Produce a map of late 23rd-century Mars for the Atlas.

As far as releases for my patrons are concerned: I expect a free update of the growing Architect release draft, and that’s about it. As in May, I may write another chapter or two of Twice-Crowned, but I don’t expect to produce enough new material to justify a charged release.

As a side note, I’m getting close to a decision as to whether to set up an LLC to publish under, rather than publishing simply under my byline. That’s a straightforward process, but there are a lot of steps and some expense involved, so I’ve been considering it carefully. May have an announcement about that sometime this month.

Status Report (21 May 2023)

Status Report (21 May 2023)

Things are moving along, if not as quickly as I might have liked.

As of today, I’ve finished initial layout for Architect of Worlds through Step Twenty-Seven in the design sequence (world albedo). At this point I need to do a little research and possibly reworking of the mini-model for atmospheric greenhouse effect. Once that’s done, I think I’ll be able to finish editorial work on the next few steps in the design sequence, and get those laid out in the interim draft. Probably won’t be able to get all the way to the end this month, but we’ll see.

Meanwhile, I need to write up two book reviews and get those posted before the end of May.

Some of my time has been taken up by a Muse-inspired side trip. I’ve been binge-watching the entire Star Wars continuity – the current canon, not the pre-Disney “Legends” canon. Kind of kicking myself for not having picked up on that earlier. The theatrical films are, of course, something of a muddle. On the other hand, the animated shows and the Disney+ mini-series have been superb. The experience has been tickling my world-building brain something fierce.

The concept that’s taken up residence in my head involves a kind of “alternate history” of the Skywalker Saga, with the (overt) point of divergence that Qui-Gon Jinn survives the Battle of Theed and lives to take Anakin Skywalker on as his student. I’m also indulging in some rampant speculation about the motives that Sheev Palpatine might have had for his decades-long campaign to subvert and take over the Galactic Republic. I may end up with a pretty solid outline for a divergent Star Wars RPG campaign, although actually running it for players (or writing a fan-fiction series on the premise) is probably out of the question. I’ll probably write it up here as time permits, rather like the Space: 2049 material I’ve been playing with at odd moments.

Don’t worry. Architect and my other top-shelf projects aren’t going to be neglected. Much.

For my patrons, I think you can expect to see a free-update of the Architect partial draft, with as much new material as I’ve been able to edit and lay out in May. No charged release for this month.

Planning for May 2023

Planning for May 2023

I was able to stay more or less on track throughout the month of April. I didn’t quite reach my original objective for Architect of Worlds book design and layout, but I did get a substantial chunk of work finished. I also managed to get to the end of Part Two of Twice-Crowned. A lot of items were done without me having to rush down to the wire at the end of the month, too – for example, I got April’s book review published quite early. I do seem to have mastered the skill of sticking to the big projects well enough to continue making significant progress.

As I mentioned a few days ago, I’m planning to do some work on the actual content of Architect before I get back to layout, so that’s a high-priority item for the month of May. Otherwise the plan for this month is going to look a lot like the one for April:

  • Top Priority:
    • Architect of Worlds: Review and possibly revise the mini-model for a world’s internal heat budget, specifically for Step Twenty-Four of the design sequence.
    • Architect of Worlds: Review and possibly revise the mini-models for a world’s atmospheric greenhouse effect, specifically for Step Thirty of the design sequence.
    • Architect of Worlds: Continue work to design and lay out the finished book. Tentatively plan to finish through page 132 (out of approximately 180), or the end of the Designing World Surface Conditions section.
  • Second Priority:
    • Danassos: Continue work on the new draft of Twice-Crowned.
    • Danassos: Rebuild the alternate-historical timeline.
    • Human Destiny: Continue compiling material for the eventual Atlas of the Human Protectorate.
    • Human Destiny: Produce a map of late 23rd-century Mars for the Atlas.

As far as releases for my patrons are concerned: I expect a free update of the growing Architect release draft, and that’s about it. I may write another chapter or two of Twice-Crowned, but I don’t expect to produce enough new material to justify a charged release. Slow but persistent progress is the order of the day.

Status Report (27 April 2023)

Status Report (27 April 2023)

Small course correction, with respect to Architect of Worlds.

A few minutes ago, I sent this month’s incremental update of the book design to my patrons. That’s a few days early and about 12 pages short of the goal I set for myself at the beginning of April.

The reason is that I just reached Step Twenty-Four in the main design sequence. That’s the step in which you determine the current geophysical parameters for a world under development – status of the world’s lithosphere, whether or not it has active plate tectonics, that sort of thing. The issue is that there are a couple really thorny bits of math in that step, probably the ugliest formulae anywhere in the previous draft. I’m also not entirely confident in the accuracy of the mini-model for that step. So I’d like to pause the layout long enough to do a bit of research, maybe develop a new mini-model, and simplify the procedure so it’s not as ugly and ill-polished.

While I’m at it, I also have similar concerns about some of the later steps, especially where we figure out how much greenhouse effect a world gets from its atmosphere based on its composition. I’m actually very happy with the way that procedure fits together overall – it models the evolution of an Earthlike world’s atmosphere very elegantly. However, the actual mini-model for greenhouse effect is again both ugly and not one I’m 100% confident in. So that might get some attention too.

So I’m going to set aside layout work on Architect for at least a few days, while I go off and do some of that redevelopment. In the meantime, I’m just one chapter away from the point in Twice-Crowned at which I was thinking another charged release of the interim draft for my patrons might be appropriate. So the last few days of April, I’m going to spend mostly on getting that chapter written and polishing up the last chunk of new material. Patrons should look for a charged release there, probably sometime on Sunday if all goes according to plan.

I also have another “bonus” book review I want to publish this month, but that will have to wait until I’m sure I can get this chunk of Twice-Crowned whipped into shape on time. if that doesn’t work out, at least I have a review ready to go early in May.

An Insight into the Galilean Moons

An Insight into the Galilean Moons

Here’s a neat little bit of “new science” that I might be able to quickly build into Architect of Worlds while I continue editing and laying out the release draft.

The idea is that Jupiter, just after its formation, was probably much more luminous than it is today due to its heat of accretion. Its luminosity might have been as high as about 0.00001 times the current solar level. That doesn’t sound like much, but with the Galilean satellites (Io, Europa, Ganymede, Callisto) orbiting so close to the young, hot Jupiter, they would have undergone a period of extreme heating. It wouldn’t have lasted long – Jupiter would have cooled off and ceased to radiate so enthusiastically – but it seems to have been enough to drive off a lot of water ice and other volatiles.

Notice that Io, the closest to Jupiter, is almost free of water ice to this day. Which makes sense – in its first few million years, Io would have been getting over 30 times as much irradiation from Jupiter as it currently gets from the Sun. More than enough to melt and then boil water ices, and then drive the resulting water vapor into space. For Europa and Ganymede the effect wouldn’t have been as pronounced, which is why those moons still have plenty of ice today.

At present, the Architect of Worlds design sequence has a weird kludge in place to differentiate Io-like from Europa-like or Ganymede-like gas giant moons. It shouldn’t be too difficult to replace that with a rough estimate of a gas giant primary’s early luminosity, which (when taken with the moon’s orbital radius) will indicate how much irradiation the moon got early in its history. Particularly important for super-Jupiters, which we’ve already observed plenty of and for which the design sequence certainly allows.

I think I may also rearrange some text between Steps Sixteen (world density and surface gravity) and Seventeen (placing moons). Right now that’s the only place in the design sequence where you implicitly have to back up a step – after you place a moon in Seventeen, you may want to go back to Sixteen to determine its density and so on. Easy enough to move some of the pertinent text forward, so you can figure out a moon’s properties in the same step when you place it. That’ll also allow me to insert the new computation at a convenient place in the sequence.

A popular-science article on this result is here: Baby Jupiter glowed so brightly it might have desiccated its moon. The research paper involved, with references to other relevant work, is here: The effect of Jupiter’s early luminosity on the Galilean satellites.

Very Small “Habitable” Worlds?

Very Small “Habitable” Worlds?

This article was brought to my attention a while back: “How small is the smallest habitable exoplanet?” (EarthSky, October 2019). The basic takeaway was kind of eye-catching.

Apparently some modeling work had been done to try to find the boundary between “planet-like” and “comet-like” water-rich objects. The distinction (in this specific context) is that “planet-like” objects can have atmosphere and liquid surface water, whereas “comet-like” objects can’t – they either retain water ice on their surface, or they lose their water entirely. The models pointed in the direction of surprisingly small objects falling into the “planet-like” domain – rocky planets or moons with as little as 2.7% of Earth’s mass could be “habitable” in this sense.

Naturally, that led me to raise an eyebrow, given that the Architect of Worlds design sequence is decidedly not going to give us worlds that small with liquid surface water. One of the reasons I wrote Architect in the first place was as a reaction against early planet-design sequences, in games like Traveller, which sometimes gave us those really implausible cases of worlds as small as Luna with Earthlike atmospheres and oceans. Had I been operating under a false assumption all along?

So I tracked down the actual paper: “Atmospheric Evolution on Low-gravity Waterworlds” (Astrophysical Journal, August 2019). If I’m reading this right, this is one of those cases where the Architect model probably doesn’t need to be adjusted to fit new science.

What the paper seems to be saying is that even some of these very low-mass worlds might be able to retain an atmosphere and liquid surface water. It looks primarily at the possibility of a runaway greenhouse, and at the mechanism of hydrodynamic escape for water. It doesn’t seem to address the possibility of simple thermal or Jeans escape, and it doesn’t take photodissociation into account at all. So it’s only looking at some of the mechanisms for atmospheric or water loss . . . and even so, these low-gravity worlds aren’t going to retain atmosphere or water indefinitely. What the authors have shown is that under ideal conditions, some of these small worlds may be able to retain liquid-water oceans for a while – up to a billion years or so. Which is interesting, but it doesn’t tell us anything about a long-term stable state, much less the possibility of the evolution of a local biosphere.

Architect generally assumes that the planetary systems you design with it are stable on several-billion-year timescales. Planets and systems of moons aren’t going to be crashing into each other, planetary surface conditions aren’t going to be in a state of rapid change. Which means the Architect model isn’t designed to look at edge cases like these, which are only likely to appear in very young star systems.

To astronomers, “habitable” means “there can be liquid water right now.” Which can include worlds that are not going to be at all comfortable for humans without environment suits and sealed habitats. It can also include worlds, as here, where the “habitable” state is more or less transient.

So in this case I’m not seeing the need to adjust my design sequences as they stand. It occurs to me that it might be worthwhile to provide some material on system or planetary states that aren’t long-term stable, so the reader can place some outliers. Planets that are likely to collide sometime in the next few thousand years, say, or tiny worlds like these with a surprising amount of free water on hand. For the moment, I think that’s going to be delayed until I write a second edition of the book.

Planning for April 2023

Planning for April 2023

March was a surprisingly productive month. I blew right past my milestone for the layout and book design of Architect of Worlds. I believe I can predict now, with high confidence, that the bulk of the layout will be finished sometime in June. At that point I’ll still need to make one more editorial pass, create and arrange a bunch of filler art, probably clean up the cover and a few other illustrations, and create the credits page and the table of contents. I can’t imagine any of that will take more than a couple of months to finish. Very tentatively, let’s look to see Architect of Worlds released in its first edition late this summer.

I also managed to get a chapter or so written in Twice-Crowned. That looks like a good trend to maintain in the coming month. On the side, I’ve been tinkering with the alternate history for the Danassos setting. I had become dissatisfied with a few elements of the history about the time of the Twice-Crowned novel, so I’ve been going back in what little free time I have and working out some changes. That’s set me back from working with Notion so much – that will probably resume once I’m happy with the new structure.

Once again, this month’s planning message is going to look a lot like last month’s.

  • Top Priority:
    • Architect of Worlds: Continue work to design and lay out the finished book. Tentatively plan to finish through page 115 (out of approximately 180).
  • Second Priority:
    • Danassos: Continue work on the new draft of Twice-Crowned.
    • Danassos: Rebuild the alternate-historical timeline.
    • Human Destiny: Continue compiling material for the eventual Atlas of the Human Protectorate.
    • Human Destiny: Produce a map of late 23rd-century Mars for the Atlas.

I expect at least one free update for my patrons – the next partial interim draft of the Architect book design. I suspect there’s a good chance that I’ll also be able to issue a charged release in April: the next partial draft of Twice-Crowned, hopefully well past the mid-point of the planned story.