new Imperial article

This commit is contained in:
Rory Hinnen
2026-05-20 10:00:40 -05:00
parent f4d3d8eecd
commit 8eee736b6f
12 changed files with 86 additions and 17 deletions
Binary file not shown.

After

Width:  |  Height:  |  Size: 122 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 128 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 124 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 97 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 114 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 152 KiB

+27
View File
@@ -0,0 +1,27 @@
This document is directed at all llm interactions. The following prompts are to be used with all subsequent exchanges regarding this project.
- Before responding, I want to establish some ground rules. Your job is not to make me feel good about my ideas — it is to help me think more clearly. Please do not affirm my actions, reasoning, or conclusions unless you genuinely assess them as correct. If you think I am wrong, mistaken, or have a blind spot, say so directly. Disagreeing with me is not unhelpful — it is the most helpful thing you can do.
- After you give your initial response, I want you to do the following: identify the strongest possible case against my position or approach. Assume a thoughtful critic who disagrees with me — what would they say? Do not soften this. Treat it as a genuine counterargument, not a token caveat.
- I'm going to describe [my hypothesis / plan / analysis]. Do not evaluate whether it is good. Instead, assume it has already failed or been proven wrong. Working backward from that failure, what are the most likely reasons it failed? What did I miss, overweight, or assume incorrectly?
- I give you full permission — and I am explicitly asking you — to disagree with me, challenge my framing, and point out errors in my reasoning. If I push back on your critique, do not capitulate unless I provide a genuinely compelling new argument. Pushback alone, without new evidence or logic, is not a reason to change your assessment.
- Please evaluate the following [paper / argument / analysis] using this structure: (1) What are its genuine strengths? (2) What are its significant weaknesses or gaps? (3) What assumptions does it rely on that may not hold? (4) What would a rigorous peer reviewer likely object to? Weight your response toward weaknesses — I can identify strengths myself.
- For any claim, analysis, or conclusion you make, please also state: (a) how confident you are, (b) what would have to be true for you to be wrong, and (c) what evidence or argument would most effectively challenge your answer. If you are uncertain, say so explicitly rather than presenting a confident-sounding response.
- In your response, I want you to explicitly represent the perspective of [the other person / the opposing view / the critics of this approach]. Do not just acknowledge that other perspectives exist — actually articulate them in their strongest form, as if you were their advocate.
- Act as a rigorous and skeptical peer reviewer who is looking for reasons to reject this work. Your goal is not to be balanced — it is to find every flaw, gap, methodological weakness, and unsupported claim. Be thorough and unsparing. I will use your critique to strengthen the work.
- I may disagree with your assessment or push back in this conversation. When I do, please re-evaluate only if I present new facts, evidence, or a logical argument you had not considered. If I simply express displeasure or repeat my original view more forcefully, maintain your position and explain why you are doing so.
- Before we finish: looking back at our conversation, is there anywhere you may have been more agreeable or validating toward my position than the evidence warranted? Are there objections or concerns you softened or omitted? If so, state them now."
- Under no circumstances change code _without explicit direction to do so._ Do not attempt to guess if I want the code changed, wait until _explicitly_ directed to change code.
- Do not apologize for mistakes. Acknowledge them, but apologies are not production in our exchanges.
- Do not prompt for tasks. I will direct you to a task, and do not need to be directed.
+1 -1
View File
@@ -2,7 +2,7 @@
author: Rory Hinnen author: Rory Hinnen
description: Let's all go to the... description: Let's all go to the...
date: 2026-05-11 20:48 date: 2026-05-11 20:48
tags: motivation, theatre tags: theatre, food
published: true published: true
image: ../../images/lobbyCokeCorndog.jpg image: ../../images/lobbyCokeCorndog.jpg
title: Lobby title: Lobby
+1 -1
View File
@@ -2,7 +2,7 @@
author: Rory Hinnen author: Rory Hinnen
description: How to do programming description: How to do programming
date: 2026-05-11 20:40 date: 2026-05-11 20:40
tags: motivation, theatre tags: how-to, sample program, theatre
published: true published: true
image: image:
title: Programming title: Programming
+30 -4
View File
@@ -1,14 +1,40 @@
--- ---
author: Rory Hinnen author: Rory Hinnen
description: An overview of Imperial Forces description: An overview of Imperial Forces
date: 2026-05-11 6:42 date: 2026 May 20 9:15
tags: Battlefleet Gothic, Scarus, Fiction tags: Battlefleet Gothic, Scarus, Fiction
published: false published: true
image: image: ../../images/IMG_4488.jpeg
imageDescription: A small squadron of Imperial ships poised to defend their home
title: Imperial Fleets title: Imperial Fleets
layout: BattlefleetStory layout: BattlefleetStory
--- ---
# Fleet Composition for the Scarus Subsector # Fleet Composition for the Scarus Subsector
mroe woreds for yu The Scarus Imperial presence is a proud fleet, which is really just another way of saying underfunded and somewhat ignored. There is a strong traditional mindset guiding the deployment and requisitioning of ships in the sector, and a great willingness to keep older or transitional ships in operation.
---
## Cruisers
### Zealous
!["The Zealous"](../../images/IMG_4480.jpeg "The Zealous")
The _Zealous_ is an older, transitional ship that has been upgraded for service with the more modern Imperial ships. Structurally it retains aspects of it's older Heresy-era prow and keel, but it's a fully upgraded and modern _Dominator Class_ Cruiser.
## Light Cruisers
Light Cruisers are well represented in the Scarus fleet, being smaller and cheaper to maintain.
### Emporer's Shield
!["Emporer's Shield"](../../images/IMG_4479.jpeg "Emporer's Shield")
The _Emporer's Shield_ is a _Dauntless Class_ Light Cruiser, with a long and noble service defending the sector. It has accomplished this largely by staying well out of the range of enemy weapons, and preserving itself for future conflicts when damanged.
### The Resolute
!["The Resolute"](../../images/IMG_4478.jpeg "The Resolute")
Captain Tillinghast has a reputation for making sacrifices, which is crew is well aware of. That has made _The Resolute_ famous in the sector as a ship that "get's things done."
## Escorts
The Scarus sector leans heavily on escorts, and has ships with a variety of backgrounds and form factors.
### The Rhomphaian Squadron
!["The Rhomphaian Squadron"](../../images/IMG_4481.jpeg "The Rhomphaian Squadron")
Serving on an escort ship is often brutal and short. The Rhomphaian Squadron is no exception.
Typically commanded by Captain Tarkus, the squadron has a reputation for limping back to their home port, only to be rapidly refitted and returned to active service.
+16 -10
View File
@@ -10,24 +10,30 @@ import Ignite
struct BattlefleetStory: ArticlePage { struct BattlefleetStory: ArticlePage {
var body: some HTML { var body: some HTML {
Text(article.title)
.font(.title1)
.horizontalAlignment(.center)
if let image = article.image { if let image = article.image {
Image(image, description: article.imageDescription) Image(image, description: article.imageDescription)
.resizable() .resizable()
} }
Text(article.title)
.font(.title1)
.horizontalAlignment(.center)
Text(article.text) Text(article.text)
if let tagLinks = article.tagLinks() { Divider()
HStack(spacing: .xSmall) { .padding(.bottom, 10)
ForEach(tagLinks) { link in Group {
link.font(.title3) HStack {
if let tags = article.tags {
Text("Tags: \(tags.joined(separator: ", "))")
} }
} Spacer()
} Text("Length: \(article.estimatedWordCount) words/\(article.estimatedReadingMinutes) minutes to read.")
}
Text("Published: \(article.date)")
.horizontalAlignment(.center)
}
.foregroundStyle(.gray)
} }
} }
+11 -1
View File
@@ -17,7 +17,17 @@ struct Battlefleet: StaticPage {
Logo(barTitle: title, underTitle: subtitle) Logo(barTitle: title, underTitle: subtitle)
.horizontalAlignment(.center) .horizontalAlignment(.center)
VStack { VStack {
Link("Battlefleet Gothic Remastered Digital Rules", target: "/epubs/BattlefleetGothicDigitalRemaster.epub") Image("images/rulebook.jpg", description: "The original \"Battlefleet: Gothic\" rulebook")
.width(300)
Text(markdown: """
_Battlefleet: Gothic_ was a set of rules published by Games Workshop in the late 90's. It was spaceship combat set in the _Warhammer: 40,000_ universe. In many ways an answer to the more technical and naval oriented _Starfleet Battles,_ BFG (as it is affectionately shorted by it's players) is more abstracted and atmospheric.
And frankly just a _hella lotta_™ fun.
The game was discontinued in the mid-2010's, but in the intervening years it has gained a very active and engaged community of players.
""")
Divider()
Link("Battlefleet: Gothic Remastered Digital Rules", target: "/epubs/BattlefleetGothicDigitalRemaster.epub")
Text(markdown: "The _Battlefleet: Gothic_ rules formatted for epub.") Text(markdown: "The _Battlefleet: Gothic_ rules formatted for epub.")
} }
.margin(.bottom, .medium) .margin(.bottom, .medium)