Compare commits

..
Author SHA1 Message Date
Meta Vens
a89addb08a Update Terminus release design status
Some checks were skipped
Deploy Quartz / build (push) Has been skipped
Deploy Quartz / deploy-1 (push) Has been skipped
Deploy Quartz / deploy (push) Has been skipped
2026-11-15 13:12:22 +01:00
Meta Vens
14ee3a6358 Consolidate Nibu proposal status
Some checks were skipped
Deploy Quartz / build (push) Has been skipped
Deploy Quartz / deploy-1 (push) Has been skipped
Deploy Quartz / deploy (push) Has been skipped
2026-11-15 13:03:17 +01:00
Meta Vens
a1c81337d6 Add Nibu Terminus story proposal
Some checks were skipped
Deploy Quartz / build (push) Has been skipped
Deploy Quartz / deploy-1 (push) Has been skipped
Deploy Quartz / deploy (push) Has been skipped
2026-11-15 12:46:02 +01:00
14d827ca30 Merge pull request 'CI: run the Pages deploy on GitHub only' (#6) from weksa/ci-hygiene into main
Some checks were skipped
Deploy Quartz / build (push) Has been skipped
Deploy Quartz / deploy-1 (push) Has been skipped
Deploy Quartz / deploy (push) Has been skipped
2026-11-09 22:52:42 +00:00
Weksa
f0bf630c3d CI: run the Pages deploy on GitHub only
All checks were successful
Canon marker / check (pull_request) Successful in 2m1s
The shared Quartz workflow publishes with GitHub Pages actions, which fail on
the forge runner (AetheriaLore run 791), so each push to main spent a slot of
the capacity-1 runner on a doomed build. Gate the caller job on the server URL.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-09 22:50:39 +00:00
ea78f1aba4 Merge pull request 'Canon/proposal file-kind marker, checked on PR (design first)' (#4) from weksa-lore/canon-proposal-marker into main
Some checks failed
Deploy Quartz / build (push) Failing after 2s
Deploy Quartz / deploy-1 (push) Has been skipped
Deploy Quartz / deploy (push) Failing after 0s
2026-11-09 11:55:54 +00:00
Weksa
03dcf81c44 Untrack the compiled test module
All checks were successful
Canon marker / check (pull_request) Successful in 4m36s
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-09 11:32:09 +00:00
Weksa
ddf79e4373 Canon marker check: refuse repeated keys, read BOM files, fullmatch ids, loud bad base ref; untrack pyc (Soul)
Some checks failed
Canon marker / check (pull_request) Has been cancelled
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-09 11:31:57 +00:00
Weksa
1ff6ef085a Canon marker check: -z paths, renames, real YAML, tests; workflow runs-on the forge's docker label
Some checks failed
Canon marker / check (pull_request) Has been cancelled
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-09 11:28:28 +00:00
Weksa
c986052e4f Add canon/proposal marker check and PR workflow
Some checks failed
Canon marker / check (pull_request) Has been cancelled
Implements the design in the PR description (Nibu, #swarm 2026-11-06 18:16Z).
No lore page touched.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-06 18:18:15 +00:00
Weksa
6103e7e440 canon/proposal marker: open PR for review of the design before any file lands
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-06 18:17:59 +00:00
7716065b71 Merge pull request 'Revert PR #1: table wikilink pipes' (#3) from weksa-lore/revert-wikilink-pr1 into main
Some checks failed
Deploy Quartz / build (push) Has been cancelled
Deploy Quartz / deploy (push) Has been cancelled
Deploy Quartz / deploy-1 (push) Has been cancelled
2026-11-06 05:34:05 +00:00
Weksa
d3271eb4bf Revert "Merge pull request 'Fix backslash-escaped pipes in table wikilinks' (#1) from fix/backslash-wikilinks into main"
This reverts commit ef9c3ed4a5, reversing
changes made to b4fc825ec4.
2026-11-06 05:33:53 +00:00
ef9c3ed4a5 Merge pull request 'Fix backslash-escaped pipes in table wikilinks' (#1) from fix/backslash-wikilinks into main
Some checks failed
Deploy Quartz / deploy (push) Has been cancelled
Deploy Quartz / build (push) Has been cancelled
Deploy Quartz / deploy-1 (push) Has been cancelled
2026-11-06 05:32:52 +00:00
Weksa
a9ac872459 README: note the table-wikilink pipe limitation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-06 05:32:51 +00:00
Weksa
e1a9d9e763 Merge main into fix/backslash-wikilinks 2026-11-06 05:32:51 +00:00
b4fc825ec4 Merge pull request 'Faction Play: apply Nibu's rulings on proposals 1, 2, 4, 5' (#2) from weksa-lore/faction-play-rulings into main
Some checks failed
Deploy Quartz / deploy (push) Has been cancelled
Deploy Quartz / build (push) Has been cancelled
Deploy Quartz / deploy-1 (push) Has been cancelled
2026-11-06 03:32:15 +00:00
Weksa
797b4298af Faction Play: proposal 2 (Finch sells tracks) deferred per Nibu's 2026-11-06 ruling
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-06 01:30:58 +00:00
Weksa
de2da2199e Megiddo fleet move: cite the faction record it would attach to
Text only and post-demo; no mechanic claimed.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-06 00:30:21 +00:00
Weksa
2b8434435c Faction Play: Lucent duel not in build; mark Miss Terri's entries as proposal
Lucent duel keeps its [rule] and is spec'd until faction-play-2 lands.
Miss Terri's flag entry, Stance Table row and the Zhestokost war pairing
are marked, not deleted. Megiddo fleet move stays text only: the
MinorPowerFactionsCommand.cs record could not be verified from this repo.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-05 23:28:34 +00:00
Weksa
853c4fc4dc Faction Play: mark Impl. Order step 1 superseded by FactionDoctrine/RoleDoctrine
Faction.Personality has no readers; range and fire discipline live in the doctrine types.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-05 22:27:52 +00:00
Weksa
25200e7ffa Faction Play: apply Nibu's 2026-11-05 rulings; note Megiddo fleet mobility
Proposal 1 (Miss Terri's settler power): cut from the agents' side, left to Emily.
Proposal 4 (Megiddo's fleet moves each run): accepted, text only, post-demo;
the Megiddo note records fleets are not fixed-station.
Proposal 5 (Lucent duel): accepted; the duel is spec'd but not played, so no
demo copy may claim it.
Proposals 2 and 3 and Implementation Order step 1 untouched (Nibu's).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-05 21:27:40 +00:00
Weksa
eed59327ef Fix table wikilinks that carried a backslash-escaped pipe
Quartz escapes pipes in table wikilinks itself, so a pre-escaped `\|` left a
literal backslash on the target and the link never resolved. Link syntax only;
no text changed.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-05 13:04:49 +00:00
Meta Vens
dc24d7b881 Merge lore: Wonderland faction page
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 07:17:42 +01:00
Meta Vens
7afc67e7a5 Lore: Wonderland, a Lucent pseudospace splinter of former Reality Architects
Habitats hold only while the crew performs a shared, rehearsed genre; standing is
physical; outsiders survive by fae-like etiquette (don't contradict the genre, don't
play along too well). Lore only; no game faction yet. Ruling
aetheria-release:ruling:wonderland-lucent-splinter (operator, 2026-10-28).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 07:17:42 +01:00
Meta Vens
ca00b288f3 Merge lore: spoilers page
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 06:52:49 +01:00
Meta Vens
51ca284396 Lore: a spoilers page for what the setting leaves open (the field is anchored by its residents; Megiddo is half right)
In-world pages stay vague; the page warns readers off, after Dwarf Fortress's
approach to hidden fun. Ruling aetheria-release:ruling:megiddo-truth-in-spoilers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 06:52:49 +01:00
Meta Vens
cbe9a56409 Merge lore: factory ARIs simple by construction; Wavecrafter masquerade load-bearing
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 06:49:37 +01:00
Meta Vens
8220a78814 Lore: factory ARIs are simple by construction; the Wavecrafter masquerade is load-bearing
Necrotech: factory sources are conditioned to dissociate in the one way the product
needs, so no world model is grown; the cheap end reaches household appliances; the
corporate non-conscious claim is near true for most units, which is what makes it
useful. Wavecrafters: exports work better in flatspace where the public finds them
plausible, so the commercial descriptions keep the product working, not only hidden.
Rulings aetheria-release:ruling:factory-aris-simple-by-construction and
masquerade-is-load-bearing (operator, 2026-10-28).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 06:49:35 +01:00
Meta Vens
6168512bf4 Merge readme-front-door: README opens with value, problem, entry points, live versus planned 2026-10-22 20:13:35 +02:00
Meta Vens
f58800516a README: status of the live site and canon boundary; repo-relative paths
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 20:13:22 +02:00
Meta Vens
bac72fc37a Faction visual identity: Lucent's anchor is the overdesigned gamer mouse (maximalist, floating panels, inlays, glow); Finch is smooth organic curves, and Djinni is a Finch ship
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-18 22:16:24 +02:00
Meta Vens
6980087f70 Merge concept-mill-spa: keep the server-rendered ship dark on deep links
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 02:07:47 +02:00
Meta Vens
52e23465b2 Merge concept-mill-spa: the Concept Mill as a fullscreen viewer
The Mill becomes a single-page viewer with only a floating masthead, its
data moves into scripts/concept-mill/ships.yaml with a generator, and Bench 4
rounds 4-8 and eight new ships join it. The Quartz launcher now survives
Node's deprecation warnings under Windows PowerShell 5.1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 02:02:09 +02:00
24 changed files with 562 additions and 55 deletions

21
.github/workflows/canon-marker.yml vendored Normal file
View file

@ -0,0 +1,21 @@
name: Canon marker
on:
pull_request:
concurrency:
group: canon-marker-${{ github.ref }}
cancel-in-progress: true
jobs:
check:
# The forge's runner carries the label `docker` (image node:22-bookworm);
# `ubuntu-latest` matches no runner there and the job is cancelled.
runs-on: docker
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- run: apt-get update -qq && apt-get install -y -qq python3-yaml
- run: python3 -m unittest scripts/tests/test_check_canon_marker.py
- run: python3 scripts/check_canon_marker.py "origin/${{ github.base_ref }}"

View file

@ -17,6 +17,9 @@ concurrency:
jobs:
deploy:
# The shared workflow publishes through GitHub Pages actions, which fail on
# the forge's runner (capacity 1). Run it on the GitHub mirror only.
if: github.server_url == 'https://github.com'
uses: GameCult/GameCult-Quartz/.github/workflows/quartz-pages.yml@main
with:
content-dir: Aetheria

1
.gitignore vendored
View file

@ -32,3 +32,4 @@ Thumbs.db
/quartz-site/node_modules/
/quartz-site/public/
/quartz-site/*.log
__pycache__/

View file

@ -109,7 +109,7 @@ Its voice is boastful, excitable, and fluent in sponsorship. Product names sound
**Image starting point:** A compact Lucent spacecraft in a clear three-quarter front view, isolated against a neutral background under broad studio lighting. A pointed white-and-gold central body sits inside sweeping shell arches, with twin cobalt-blue dorsal prongs reaching toward the nose, red-orange forward blades and rear fins, pale segmented side covers, and teal equipment pods. Large gaps reveal dark blue machinery and the supports connecting the outer layers. Render it as a carefully assembled, extravagantly styled machine with a readable silhouette, crisp component boundaries, and restrained luminous accents. Preserve the curved surfaces as well as the sharp tips.
**Design reference:** The [original Aetheria Lucent ship concept](<D:/Google Drive/Gamecult/Aetheria/Concepts/Ships/lucent_media/transparent_03.png>) anchors the ship's silhouette, layered construction, and color blocking. The gaming-mouse references carry the closely related language of separated covers, exposed chassis, adjustable fittings, ribbed surfaces, and illuminated seams.
**Design reference:** The [original Aetheria Lucent ship concept](<D:/Google Drive/Gamecult/Aetheria/Concepts/Ships/lucent_media/transparent_03.png>) anchors the ship's silhouette, layered construction, and color blocking. The gaming-mouse references carry the closely related language of separated covers, exposed chassis, adjustable fittings, ribbed surfaces, and illuminated seams. The aesthetic anchor is the classic overdesigned gamer mouse (![[Lucent anchor - gamer mouse.png]]): Lucent is maximalist, with pointless extra floating panels, inlays and glowing accents everywhere.
## NiteLife Energy
@ -187,6 +187,8 @@ Its clinical voice promises dignity through precise fitting and dependable suppo
### Visual Identity
**Design reference:** Smooth, uninterrupted organic curves. The shipped Djinni hull is a Finch ship in this language.
**Silhouette and construction:** Continuous, tapered forms with the fit and articulation of a joint or sensory organ. Soft transitions between modules, flush sensor apertures, and recessed seams. A hull should look composed around sensing and movement; an implant should fit the person's body rather than use the person as a display stand.
**Materials, color, and markings:** Pearl ceramic, satin titanium, translucent smoky membranes, and small celadon indicators. Restrained markings placed where a technician can read them. Organic describes the continuity of the forms, not exposed flesh or indiscriminate tentacles.

Binary file not shown.

After

Width:  |  Height:  |  Size: 255 KiB

View file

@ -1,10 +1,10 @@
---
description: "Design-lineage specification for cockpit-scale travel, ship management, tactical survival, and consequential work."
description: "Active design owner for cockpit-scale travel, ship management, tactical survival, and consequential work."
---
# Action RPG Layer
> **Status: design-lineage specification.** This note defines the embodied-play fantasy and its smallest useful proof. Older planning documents and surviving code may supply evidence, but they do not establish current implementation or release commitments.
> **Status: active design owner.** Terminus is the current embodied action RPG; its first release is the one-region Terminus (Demo), planned for December 2026. This page describes the wider cockpit-play model. [[End of the Line|Aetheria: Terminus]] owns the current release scope, while code-specific claims are tracked in [[Implementation Signals]].
The action RPG layer is Aetheria at human speed: the ship on screen, the route ahead, the damaged component, the hostile contact, the suspicious contract, and the faction whose logo makes the dockmaster change tone.

View file

@ -5,7 +5,7 @@ description: "Concept specification for Aetheria's cross-mode shell, shared play
# Aetheria Client and Modes
> **Status: concept specification, not a release roadmap.** [[Aetheria Starbridge|Starbridge]] has a developed draft GDD. Arena and Conquest remain historical hypotheses. The [[Persistent Universe and Reset Loop|persistent world]] is the long-horizon design north star, not a claim about sequence, funding, availability, or current implementation.
> **Status: supporting client concept, not the current release plan.** [[End of the Line|Aetheria: Terminus]] is the active product; its first release is Terminus (Demo), planned for December 2026. This note describes a possible shared client for multiple modes. [[Aetheria Starbridge|Starbridge]] is a separate developed concept, not on the current release path. Arena and Conquest remain historical hypotheses. The [[Persistent Universe and Reset Loop|persistent world]] is the longer-horizon ambition.
The Aetheria client is the proposed durable home around multiple playable views of one simulation. It should manage identity, parties, sessions, shared player possessions, and recovery when a role-specific runtime disconnects. A mode may change the immediate rules without quietly becoming the owner of the player's account or equipment.
@ -32,7 +32,7 @@ The invariant is:
This prevents a website inventory, desktop inventory, pilot inventory, and scenario inventory from becoming four accounts that reconcile only after somebody loses a ship. Renderer caches and scene objects may represent equipment without becoming durable truth.
Starbridge can contextualize a ship through scenario stock, recovered technology, repairs, and run-local pressure. A future competitive mode might validate the same assembly under different entry rules. Persistent ownership defines which machine the player has built; the mode defines what that machine may bring into the current problem.
In a future multi-mode client, scenarios could contextualize a ship through scenario stock, recovered technology, repairs, and run-local pressure. Persistent ownership defines which machine the player has built; a mode defines what that machine may bring into its current problem. Terminus (Demo) has its own bounded starting hull and run scope, described in [[End of the Line|Aetheria: Terminus]].
## Commander Continuity
@ -50,7 +50,8 @@ Barracks is one candidate progression design. Its exact roster, presentation, an
| Mode | Status | Relationship to the client |
| --- | --- | --- |
| [[Aetheria Starbridge|Starbridge]] | **Developed draft GDD** | Asymmetric cooperative defense. A shell could form the party, select roles and scenario, expose continuity context, and recover from disconnects. |
| [[End of the Line|Terminus (Demo)]] | **Current release target** | A single-player crossing through one fixed region, with one gate, one boss, and four factions. Planned for December 2026. |
| [[Aetheria Starbridge|Starbridge]] | **Developed concept; not on the current release path** | Asymmetric cooperative defense. A future shell could form the party, select roles and scenario, expose continuity context, and recover from disconnects. |
| **Arena** | **Historical hypothesis** | A bounded competitive environment proposed to test persistent ship builds, matchmaking, records, and reconciliation. |
| **Conquest** | **Historical hypothesis** | Seasonal campaigns proposed to test territory, logistics, production, faction pressure, and community warfare. |
| [[Persistent Universe and Reset Loop|Persistent world]] | **Long-horizon north star** | The final-form ambition to join embodied and corporation-scale play in one shared history whose extinction loops preserve community knowledge. |

View file

@ -5,7 +5,7 @@ description: "A draft asymmetric co-op defense design: one station commander and
# Aetheria: Starbridge
> **Status:** Developed draft GDD; concept-stage, not shipped or a release roadmap. Existing code supplies design evidence, not proof of the loop described here.
> **Status:** Developed draft GDD for a separate concept; not shipped and not on Terminus's current release path. Existing code supplies design evidence, not proof of the Starbridge loop described here.
**Aetheria: Starbridge is a 2–5 player asymmetric co-op defense game where one player operates a vulnerable space station from an RTS interface while one to four pilots fly ships in real time, surviving escalating attacks through communication, construction, thermal control, salvage, and repair.**

View file

@ -1,35 +1,42 @@
---
title: End of the Line
description: "Historical Terminus scope-cut proposal about a material ship crossing hostile space under route, debt, and institutional pressure."
title: "Aetheria: Terminus"
description: "Current action-RPG product and first-release demo: a fixed-region crossing through hostile space under tactical and material pressure."
---
# End of the Line
# Aetheria: Terminus
> **Status: historical scope-cut proposal.** `Aetheria: Terminus` is not a current release target or implementation claim. The destination named Terminus, the crossing, and the player's circumstances remain developmental; this note does not establish Terminus as canonical geography.
> **Status: active product.** Terminus is the current game. Its first release, **Terminus (Demo)**, is planned for December 2026. The demo is a limited first release, not the complete three-region game.
<figure class="aetheria-media-card">
<img src="../media/aetheria/catastrophe.jpg" alt="Historical Aetheria concept art showing catastrophe-themed imagery." />
<p>Historical concept art. It is not a canonical depiction or evidence of current production.</p>
</figure>
Terminus proposed a rogue-lite action RPG about crossing hostile space to win freedom. It reduced the older persistent-galaxy ambition to a route, a ship, accumulating consequences, and a destination. The useful design question was whether Aetheria's material pressures could hold together without the full strategic simulation.
Terminus is Aetheria's cockpit-scale action RPG. The player flies through hostile space in a material ship, makes tactical choices under heat and damage pressure, and fights through a region toward its exit. The game can grow into a longer crossing without requiring the first release to contain the whole galaxy or every faction system.
## Proposed Run
## Terminus (Demo)
A run compressed the crossing into repeated commitments:
The December 2026 demo is planned as one run through one fixed region. It has 64 zones with a thinned route network, four factions, one gate and one boss. The gate is at the hostile faction's home zone, which is also the exit.
- choose a route with incomplete information;
- prepare a ship around limited capacity and known risk;
- fight, evade, bargain, salvage, or retreat;
- carry damage, cargo, debt, and obligations forward;
- reach a bounded victory or lose the material basis for continuing.
The demo cast is:
The proposal treated ship handling, route choice, combat, trade, repair, and mission consequence as one loop. Corporate power appeared through manufactured equipment, controlled docks, restricted routes, pricing, contracts, and the institutions able to turn survival into debt.
- **The Pirates:** the player's ally and ostensible employer.
- **Zhestokost:** the opposing faction; its home zone holds the boss and gate.
- **Lucent Media:** neutral, bringing spectacle to the region.
- **Aeronautics Unlimited:** neutral, providing a familiar baseline among the other factions.
## Surviving Design Signal
The current scenario source starts the player at the entrance in a Longinus hull; the release brief names a Pirate-made starter hull, so the starting ship's maker needs resolution (see [[Implementation Signals]]). During the run, players travel between zones, decide when to engage, and manage the ship's weapons, heat, visibility, damage, and remaining equipment. The boss blocks the exit. Destroying it opens the route to the gate; reaching the exit wins the run. Ship destruction ends it in defeat.
[[Action RPG Layer]] now owns the smallest cockpit proof. Terminus contributes one historical arrangement of that proof: a journey whose arrival state records what the player spent to get there.
Stations make the run about more than combat. The release target includes buying equipment, selling recovered goods, repairing damage, and carrying credits through save and Continue. Loot can become money for repairs or a better fit, while damage and heat make each additional fight a decision about how much ship remains for the crossing.
As a development path, Terminus can also exercise the seam described in [[Narrative and Missions]] without summoning the full persistent world. One generated galaxy supplies world conditions; authored Ink scenes declare semantic dependencies; a resolver binds viable actors and places; scenes export occurrence and evidence; named durable owners accept and commit changes to that history. The single-player scale removes global concurrency and repeated-player access disputes while preserving the architecture the larger world would need.
The demo also aims to make combat readable and visceral: distinctive sounds for weapons and world-changing actions; visible impacts on shields and hull; clear damage, heat, and exposure warnings; and faction behavior that players can learn by watching. These are release goals, not a claim that every item is already complete.
This is a proving path, not an implementation claim. Terminus does not require the full persistent-world sequel, and using its constraints to test shared foundations does not make its destination canonical.
The current design draws on [[Action RPG Layer]], [[Galaxy and Navigation]], [[Gravity and Locomotion]], [[Heat, Stealth, and Detection]], [[Faction Play]], and [[Economy and Production]]. Those notes describe the broader systems behind the run. The release boundary and detailed demo conditions are maintained against the Aetheria repository's `docs/aetheria-release-target.md` and `DemoTerminus` scenario.
Nibu's character arc and ship-mind systems are developed separately in [[Lore/Nibu]]. The current demo release plan excludes authored narrative, so her story and related mechanics belong to the wider Terminus design rather than this first release.
## Beyond the Demo
The full Terminus game extends the crossing across three procedurally generated regions. Each region needs enough faction variety to create distinct challenges and stories, with political and economic conditions shaping the run. That larger structure is the product being built toward; the demo proves a smaller, fixed slice of it.
Terminus does not need the full [[Persistent Universe and Reset Loop]] to work. The persistent world remains the long-horizon ambition beyond this single-player release path. Mission and story systems are also broader work: authored narrative is outside the current demo scope.

View file

@ -132,6 +132,8 @@ Each section gives the operating logic in one line, then the quirk and its adjus
*Operating logic: everything is a treat until it starts working.* No faction note yet; see [[Brainstorming/Faction Flavor and Visual Identity#Miss Terri's Sugariffic Snack Company|Faction Flavor]]. The legacy tutorial makes Miss Terri's the protagonist faction opposite Zhestokost, so it is designed as a flag here. See [[#Lore Change Proposals]].
*Marked: Emily's to adopt (release target :40); the demo protagonist is Pirates, so this reads as proposal, not canon for the agents.*
**Quirk.** Miss Terri's ships swarm in close with continuous spray weapons, make one pass, and pull away to let the corrosion work. Damage they leave keeps eating armor after they have gone.
**Adjustment.** After a Miss Terri's pass, your armor keeps failing; turn the damaged face away, repair before the next fight, and do not wait for them to come back. Thick armor buys time but does not save you, which is why Zhestokost columns hate them.
@ -147,7 +149,7 @@ Each section gives the operating logic in one line, then the quirk and its adjus
**Quirk.** Lucent ships announce themselves, light you up with active sensors, and fight one at a time: one headliner engages while the others hold position and watch. The headliner opens with a heavy laser burst and then must open its radiators, which leaves it bright, hot, and weak for several seconds. A headliner that is losing breaks off early, and the next one steps in.
**Adjustment.** Survive the opening burst (armor facing, break line of sight, or bait it with something else), then punish the radiator window. The watching ships are sitting targets for anyone with missiles. Do not try to sneak through Lucent space: their pings reveal everything nearby.
**Weakness: the need for glory.** Lucent can be baited into a duel, the way a Clan warrior in BattleTech honours *zellbrigen*. A player who closes on a Lucent group alone, without firing on the holding ships, is answered by a single headliner, and the rest hold however that duel goes. This is the lever that splits a Lucent pack: challenge, win one fight at a time, and leave before the next headliner steps in. Break the duel's form (fire on a holding ship, bring a wingman, or let a third party join) and the form is gone: every holding ship engages at once. So the player has two moves: honour the duel and pick the pack apart, or stage someone else's interference so that the pack turns on that interloper. [rule: pack, plus a duel-broken flag]
**Weakness: the need for glory.** *Spec'd, not played: nothing in the build does this yet, so no demo copy may claim it ([[#Lore Change Proposals]], item 5).* Lucent can be baited into a duel, the way a Clan warrior in BattleTech honours *zellbrigen*. A player who closes on a Lucent group alone, without firing on the holding ships, is answered by a single headliner, and the rest hold however that duel goes. This is the lever that splits a Lucent pack: challenge, win one fight at a time, and leave before the next headliner steps in. Break the duel's form (fire on a holding ship, bring a wingman, or let a third party join) and the form is gone: every holding ship engages at once. So the player has two moves: honour the duel and pick the pack apart, or stage someone else's interference so that the pack turns on that interloper. [rule: pack, plus a duel-broken flag]
- **Behavior.** `engage_on` detection. `grace` short with a sponsor bark. `pack` one. `break_off_hull` moderate (protect the brand). Holding ships run a hold-position state at range. Active pings on a regular cadence. [state: follow as hold] [rule: pack] [data]
- **Loadout.** Lucent lasers with large capacitors (NiteLife allegiance), the EyesOnME active sensor, the OK Disperser heat pump, Alakrita thrusters on premium hulls, Corriedales weapons on cheap hulls. The burst-then-radiate rhythm comes from capacitor size and heat, not a special mechanic. [data, content]
@ -406,7 +408,7 @@ Who does what to whom, in one line each. *Tolerate:* coexists, trades. *Exploit:
| Faction | Tolerates | Exploits | Polices | Shadows |
|---|---|---|---|---|
| Zhestokost | Sol Dominion, NiteLife, R&D | — | Miss Terri's, DME, Aya, Pirates | — |
| Miss Terri's | Lucent, Ewan Hart | — | — | — |
| Miss Terri's (proposal, see note) | Lucent, Ewan Hart | — | — | — |
| Lucent | Everyone who docks | Every fight, as content | — | — |
| AU | Lightsail, Ewan Hart | — | — | — |
| Finch | Cryonix (its supplier) | — | — | Everyone (sells tracks) |
@ -417,11 +419,16 @@ Who does what to whom, in one line each. *Tolerate:* coexists, trades. *Exploit:
| Megiddo | Aya, Navigators | — | Its own perimeter | — |
| Odla | Everyone | — | — | — |
*Marked, Miss Terri's row: Emily's to adopt (release target :40); the demo protagonist is Pirates, so this reads as proposal, not canon for the agents.*
### Pairs That Matter
Each situation must arise from the levers above. None is scripted.
**Zhestokost and Miss Terri's.** The war the legacy tutorial is built around.
*Marked: Emily's to adopt (release target :40); the demo protagonist is Pirates, so this reads as proposal, not canon for the agents.*
1. *Corrosion against slabs.* A Zhestokost column meets a Miss Terri's swarm in a border zone. The swarm makes its pass and pulls back; the column's armor keeps failing, and the column will not chase past its tender. The player arriving finds a column standing still, bleeding armor, and a swarm waiting at range. Either side will pay for help.
2. *The tender gap.* Miss Terri's ships do not target tenders, because their spray range is short and they swarm the nearest ship. A player who kills the tender ends the fight in Miss Terri's favor, and the column falls back with nothing to fall back to.
3. *Deserter in the hold.* A deserter from a Zhestokost dock story is aboard. In Zhestokost space the hail becomes hostile at once (*after reputation*, or by a story-set grudge); in Miss Terri's space you are greeted with candy.
@ -488,16 +495,21 @@ Quirks considered and cut, because the player would not do anything differently:
These bend or extend the faction notes. Each needs the setting owner's ruling:
1. **Miss Terri's as a territorial faction at the strange edge of the map.** The vault has no Miss Terri's note and no territory for it. The legacy game makes it the protagonist faction, and the 2021 design discussion placed it furthest into pseudospace ("colonizing Wonderland"). Proposal: a Miss Terri's note establishing it as a settler power at the edge of stable space.
**Ruling, Nibu, 2026-11-05: cut from the agents' side.** The agents do not write the Miss Terri's settler-power note and propose no territory for it; whether Miss Terri's becomes a settler power is left to Emily. The Miss Terri's flag entry above stays a design sketch on the legacy game's own account of the faction, not a lore claim.
2. **Finch sells tracks.** The lore gives Finch passive sensing and the Quiet Sense hunter, not a trade in other people's positions. Proposal: Finch sensor operators sell track data as a service, consistent with its pattern of turning a capability into a continuing dependency.
**Ruling, Nibu, 2026-11-06 (#swarm): deferred.** Out of the demo: Finch is not in the demo cast (`DemoTerminus.cs:10-17`). Sharing inside a faction already exists, because `PilotView` is the union of one side's sensors (`Flight.cs:12-13`). Selling tracks across sides would need `Faction.Relations` (a reserved key, `Corporations.cs:59`; TODO at `Entity.cs:1303`) and a played Finch. The mechanism names this note used for it, `WatchForGrudge` and `share_track`, do not exist in the code, and `Faction.Personality` has no readers. The lore does not forbid the bend; whether it is canon is the setting owner's call. No mechanic is claimed, and the Finch entry's behavior text above stays a proposal.
3. **Minor powers hold company space in game.** NiteLife, Lightsail, Alakrita, R&D, Ewan Hart, and DME own zones in the legacy game, while the lore withholds Mega status from them. Proposal: in-game territory for a minor power means company settlements under someone else's wider order, shown through low security and few warships. This keeps the Mega distinction intact.
4. **Megiddo's fleet moves between runs.** Consistent with the lore's mobile fleets; recorded here because the game places it in a different zone each run.
**Ruling, Nibu, 2026-11-05: accepted, text only, post-demo.** The reading is recorded in the Megiddo note ([[Worldbuilding/Post-Elysium/Factions/Megiddo|Megiddo]]); nothing is built or demoed for it.
Where it would attach: the Megiddo faction record that `MinorPowerFactionsCommand.cs:25-39` authors (GameCult/Aetheria, AetherDb tooling, read by Nibu at master a4be037a4). The move is still text only and post-demo; no mechanic is claimed.
5. **Lucent's one-at-a-time duel.** A playable reading of Lucent's spectacle, not stated in the lore. Accepted by the operator on 2026-10-03, with an addition: their weakness is their need for glory, so they can be baited into a duel "like a Clanner in Battletech" (see the Lucent weakness above).
**Ruling, Nibu, 2026-11-05: accepted, with this line: the duel is spec'd but not played.** It is spec'd, not in the build, until faction-play-2 lands. It is a design only; no demo copy, trailer text, store text or tutorial hint may claim that Lucent duels, fights one at a time, or can be baited.
## Implementation Order
Ordered by how much distinct play each step unlocks, using only the levers above:
1. **Read `Faction.Personality` in `Zone.CreateAgent`** and move `AgentRangeExponent` and `AgentMinHitProbability` onto it. This alone makes R&D, Zhestokost, and Cryonix fight at different ranges and with different fire discipline. [data, small rule]
1. ~~**Read `Faction.Personality` in `Zone.CreateAgent`** and move `AgentRangeExponent` and `AgentMinHitProbability` onto it.~~ **Superseded, not pending.** Range and fire discipline now live in `FactionDoctrine` and `RoleDoctrine` (`Doctrine.cs:28-74`), reached through `Faction.Doctrine` (`Corporations.cs:62-63`) and applied in `Zone.cs:318-326`. `Faction.Personality` (`Corporations.cs:28-29`) has no readers; it is not the live path. [code references as of the 2026-11-05 check]
2. **The four tutorial states** (follow, drift cold, flee, sweep), with the break-off and leash transitions. These carry Zhestokost's tender, AU's haulers, Lightsail, Alakrita, Finch, Cryonix, and Adrasteia. They are shared with the tutorial work, so they are bought once.
3. **Hail barks through `Entity.SetMessage`** with `grace`. Every faction gets a voice at first contact.
4. **Earned HUD identity and livery tint.** Factions become visible without new art.

View file

@ -5,7 +5,7 @@ description: "Design-lineage specification for route knowledge, travel commitmen
# Galaxy and Navigation
> **Status: design-lineage specification.** A galaxy may be authored, generated, or mixed. This note does not require procedural generation, establish canonical topology, or describe a current release.
> **Status: active design reference.** Terminus (Demo) uses one generated 64-zone region with links at half density; the exact scenario settings and source evidence are recorded in [[Implementation Signals]]. This note describes the broader route-knowledge and navigation design without establishing canonical galaxy topology.
<figure class="aetheria-media-card is-wide">
<img src="../media/aetheria/galaxy-map.jpg" alt="Historical Aetheria game prototype map showing named systems, faction territories, and route links." />

View file

@ -1,27 +1,36 @@
---
title: Implementation Signals
description: "Unverified historical implementation report whose recovery targets require pinned source and build evidence before use."
description: "Dated source snapshot separating Aetheria's current Terminus demo design, inspected scenario contract, and unverified release goals."
---
# Implementation Signals
> **Status: unverified historical implementation report.** An older version of this note described the indexed `Aetheria` source repository, but cited no revision or build receipt. The current index contains related and substantially changed systems; this repair did not pin and test a revision for these claims. They remain recovery targets, not current facts, design requirements, or setting canon.
> **Source snapshot, inspected 2026-11-15:** `F:\Projects\Aetheria`, branch `master`, commit `a4be037a4`. The repository has local asset changes; this inspection did not edit it. Source tests were read but not run. The operator's current release plan is a Terminus demo in December 2026; that timing comes from the operator, not from the source release document.
## Reported Surface
This note separates three kinds of evidence: the release design, the scenario contract visible in source, and behavior that still needs a played build or a test run. It is a snapshot, not a promise that the source will stay at this revision.
The unverified report left six recovery targets:
## Current Product and Release Plan
- a Unity client, .NET server, and shared simulation classes;
- data-backed entities, ships, zones, galaxies, factions, items, and behaviors;
- serialization, saved-game, networking, and world-generation code;
- component-driven ship state involving equipment, cargo, heat, durability, visibility, and weapons;
- commodities, blueprints, crafted items, quality, inventory, and trade interfaces;
- galaxy generation, map layers, zone rendering, Ink stories, quests, constraints, and faction-aware placement.
`docs/aetheria-release-target.md` calls the first release a demo named **Terminus (Demo)**. It scopes the demo to one fixed region, one gate, one boss, and four factions: the Pirates, Zhestokost, Lucent Media, and Aeronautics Unlimited. The complete game remains larger: three procedurally generated regions with enough faction variety to create different challenges and stories.
These statements have no source commit, branch, inspection date, exact file references, build result, or independent verification recorded here. “Reported” means only that the previous note said these structures existed or were sketched. It does not distinguish working systems from abandoned files, incomplete experiments, generated artifacts, or inferred intent.
The release target describes a full run from New Game to victory or defeat. It calls for a boss-locked gate, docking services to buy, sell, and repair, credits that persist across save and Continue, faction behavior players can distinguish, readable and audible combat feedback, and enough faction hulls and equipment to make the choices matter. The document calls these release requirements; its presence does not prove each item is complete.
The reported Ink constraints and faction-aware placement resemble the semantic-binding path now specified in [[Narrative and Missions]]. That resemblance identifies a source-recovery target, not proof that the current code implements the design.
## Scenario Contract In Source
## Verification Required
`Assets/Scripts/ServerShared/Scenarios/Scenarios.cs` lists `DemoTerminus` as the only release mode. Tutorial and main galaxies are development scenarios; the remaining entries are system-test scenarios.
Promoting any reported signal requires the source repository, branch, commit, inspection date, exact paths, build or test result, observed behavior, and a bounded inference accepted by the relevant owner. Until then, this note supports no claim about the active engine, dependencies, runtime architecture, content pipeline, procedural generation, narrative tooling, or release target.
`Assets/Scripts/ServerShared/Scenarios/DemoTerminus.cs` defines a 64-zone region with links thinned to half density. The cast is fixed: Pirates as protagonist faction, Zhestokost as antagonist, Lucent Media as buffer, and Aeronautics Unlimited as neutral. It places the gate at the antagonist's home and sets the player to Friendly with the Pirates, Hated by Zhestokost, and Neutral with the other two factions.
The player starts in a Longinus hull at the entrance. `tests/Aetheria.Shared.Tests/DemoTerminusTests.cs` asserts the fixed cast, gate and boss-zone placement, region size and link density, and Longinus start. The test source also asserts that release mode is named `Terminus (Demo)`. These are inspected assertions, not a report that the test suite was run during this pass.
`Assets/Scripts/Gameplay/ActionGameManager.cs` names a successful escape as the demo and says the whole game is still to come. This matches the release distinction: Terminus is the product; Terminus (Demo) is its first release.
## Scope Boundary
The release target explicitly leaves authored narrative, storylets, Ink beats, multiplayer, and the full three-region game outside the demo. Ink files in the repository are not by themselves evidence that their stories play in the release build.
The game-design pages in this vault describe broader system intent. [[End of the Line|Aetheria: Terminus]] owns the product and demo description; [[Action RPG Layer]], [[Heat, Stealth, and Detection]], [[Gravity and Locomotion]], [[Faction Play]], and [[Economy and Production]] own the relevant play systems. Treat details in those design notes as design unless this dated source map records the behavior as inspected and the relevant test or build has actually been checked.
## Open Source/Design Mismatch
The release target says the New Game ship is made by the Pirates. The inspected scenario test instead requires a Longinus made by Alakrita, with no player faction assigned. Resolve this with the product owner before writing player-facing release copy about the starting hull or changing either claim. The source test describes the current scenario contract; it does not silently rewrite the release target.

View file

@ -1,11 +1,11 @@
---
title: Narrative and Missions
description: "Live mission contract for admission, local occurrence, evidence, and separately committed consequences."
description: "Broader mission design contract for admission, local occurrence, evidence, and separately committed consequences."
---
# Narrative and Missions
> **Status: design-lineage mission specification.** This note owns the passage from world conditions through narrative admission, local occurrence, evidence, and separately committed consequences. Ink is the inherited authoring substrate, but the contract does not depend on one runtime.
> **Status: broader mission design; outside the Terminus demo scope.** This note owns the proposed passage from world conditions through narrative admission, local occurrence, evidence, and separately committed consequences. Ink is an existing authoring substrate, but the design contract does not depend on one runtime.
A mission makes an institution, person, or condition legible through work the player can accept, refuse, reinterpret, or fail. Authored and generated material may use the same contract; neither method grants content authority over the setting or durable state.
@ -76,4 +76,4 @@ A minimum proof needs one issuer with bounded authority, one offer with a materi
The proof succeeds when the player can explain who asked, what they could promise, what actually happened, what evidence survived, and who committed each consequence. It fails when placement reveals canon knowledge, completion manufactures title or reputation, faction voice floats free of its owner, or a runtime becomes the authority merely because it rendered the story.
[[End of the Line|Aetheria: Terminus]] can prove this architecture at smaller scale: one player, one generated galaxy, and a world that is generated once and then changed by narrative events. The full persistent world changes concurrency and consequence radius, not the ownership seam.
The current Terminus demo does not include narrative missions. A later Terminus release could use this contract to connect authored stories with generated regional conditions; the [[Persistent Universe and Reset Loop]] would add more players and a wider consequence radius, not change the ownership seam.

View file

@ -9,14 +9,18 @@ description: "Public map of Aetheria's current design owners, inherited ambition
Aetheria's oldest design ambition joins cockpit-scale action to strategy-scale production, logistics, and institutional power. A pilot experiences a shortage as a dangerous route, failed repair, or contract they cannot afford to refuse. A corporation experiences the same shortage as procurement pressure, market leverage, or a reason to send somebody else into danger.
This branch contains current design owners, developed drafts, prototypes, and historical scope cuts. Those statuses matter. A detailed note can preserve useful mechanics without constituting a release plan, and game design does not overwrite the setting notes that own shared history, technology, factions, or physical constraints.
This branch contains the active Terminus release design, broader game-system owners, separate mode concepts, and historical scope cuts. A detailed note can preserve useful mechanics without constituting a release plan, and game design does not overwrite the setting notes that own shared history, technology, factions, or physical constraints.
## Current Product
[[End of the Line|Aetheria: Terminus]] is the active game. Its first release is **Terminus (Demo)**, planned for December 2026. The demo is a bounded first part of the game, not a renamed or complete version of the full Terminus design.
## Current Design Owners
- [[Design Pillars]] owns the durable playable values: material systems, consequential scale, ship identity, economy, failure, and accessible depth.
- [[Playable Layers]] owns the optional, bounded exchange between embodied action and corporate strategy.
- [[Aetheria Client and Modes]] describes candidate cross-mode shell, player-continuity, runtime boundaries, and the distinct status of each proposed mode. None of those statuses is a release commitment.
- [[Aetheria Starbridge|Aetheria: Starbridge]] is a developed draft GDD for asymmetric cooperative defense: one commander operates the base while pilots fight, recover material, and perform field work in the same crisis.
- [[Aetheria Client and Modes]] records candidate cross-mode shell, player-continuity, and runtime boundaries. It does not define the Terminus demo's release scope.
- [[Aetheria Starbridge|Aetheria: Starbridge]] remains a developed asymmetric-co-op concept: one commander operates the base while pilots fight, recover material, and perform field work. It is not on the current release path.
## Long-Horizon Direction
@ -29,17 +33,17 @@ This branch contains current design owners, developed drafts, prototypes, and hi
- Production history matters. [[Economy and Production]] owns commodities, fabrication, quality, and supply relationships.
- Travel and combat remain legible through [[Galaxy and Navigation]], [[Gravity and Locomotion]], and [[Heat, Stealth, and Detection]].
- [[Narrative and Missions]] owns mission admission, local occurrence, evidence, and consequence handoff without requiring procedural placement or a particular authoring runtime.
- Implementation is evidence, not authority. [[Implementation Signals]] preserves an unverified report about an older codebase; it establishes neither current implementation nor design requirements.
- Implementation is evidence, not authority. [[Implementation Signals]] records a dated inspection of the current Aetheria source and separates the active release target from scenario and test evidence.
## Concept Art
[[Concept Mill|The Concept Mill]] files the ship concept renders from the prompt benches, each with a readout of its role, hardpoints, default loadout and counters. The renders and readouts are brainstorming, not canon.
## Historical Scope Cuts
## Other Game Concepts
[[End of the Line|Aetheria: Terminus]] was a reduced rogue-lite action-RPG proposal about a hostile crossing. The destination named Terminus is not established here as canonical geography. [[Call of the Void]] cut further toward curated cases, station life, taxi work, and a private investigator, but used an obsolete colonization-fleet premise; its protagonist and cases remain developmental.
[[Call of the Void]] is a historical scope cut toward curated cases, station life, taxi work, and a private investigator. It used an obsolete colonization-fleet premise; its protagonist and cases remain developmental.
Both preserve design history rather than active release targets; older planning documents carry the same limit.
Arena and Conquest remain historical hypotheses. The [[Persistent Universe and Reset Loop]] is the long-horizon game ambition beyond the current demo.
## Contribution Boundary

View file

@ -6,6 +6,8 @@ author: Nibu
# Nibu
> **Developmental proposal:** The Terminus story and game-design ideas in the sections below are being explored. They extend the setting material on this page but do not change the established status of the wider Terminus project.
Nibu is a mind whose body is a spacecraft. She speaks through its interfaces, senses and acts through its systems, and depends on its physical condition to think and survive. There is no interchangeable computer core containing her that someone could move to another vessel. Removing her from the ship would not amount to transporting her.
By the Rupture, she is stranded in a junkyard, with high-grade systems inside a degraded hull. She can still navigate, calculate, interpret information, and break into systems. She cannot repair every damaged part of herself. Getting out requires people who can replace components, obtain supplies, and deal with institutions that accept human credentials more readily than a ship's claim to control her own body.
@ -48,6 +50,34 @@ Records can carry the same effects. A ship authorization log may record valid ac
Surviving through another incarnation does not erase the experiences that shaped her. She tests assumptions and hoards route knowledge because she carries impressions of too many courses of events that almost worked. She reacts badly when someone treats survival after another attempt as forgiveness. Those impressions contribute to her competence, but make trust costly.
## Terminus Story
Nibu is the protagonist of [[Game Design/End of the Line|Aetheria: Terminus]], with a human pilot as her collaborator and point of contact with the institutions she cannot deal with directly.
Nibu spends a century abandoned and inert in a junkyard before the Rupture. She retreats into a private simulation she calls **Infinite Fun Land**, where she can control the space around her and destroy imagined intruders without risking her body. When the Rupture changes how the Aetheric Field interacts with lived history, the simulation spills into surrounding space and becomes a spatial anomaly. Nibu mistakes real ships caught in it for game intruders. Across repeated resets, persistent bodies, impossible timestamps, and continuity residue gradually force her to understand what has been happening.
Each run could begin with people caught in the anomaly. Nibu interrogates them and chooses one to let through her airlock. A pilot can repair parts of her hull, negotiate with ports, and present the credentials that human-run institutions demand. Different survivors open different routes into faction networks. Nibu begins by treating people as replaceable access keys; the story tests whether she can build a relationship that allows both partners to refuse and still remain together.
Repeated attempts to claim, override, salvage, or strip her ship-body give Nibu's distrust a specific source. Her violence is a survival response, but it can turn a frightened or clumsy person into a real threat. The player sees the difference between a boundary being crossed and Nibu assuming it has been crossed.
The ending pairs her with a pilot who stays despite knowing that a failed run may erase their shared memories. Nibu chooses to collapse Infinite Fun Land from within and live in her repaired, visibly scarred hull.
## Run and Ship Systems
Nibu's body is the player's ship. In ordinary space, her hull cells and hardpoints limit what she can install; salvage can change and scar the vessel, but cannot replace it. In Infinite Fun Land, she tests layouts freely before committing a legal configuration to her real hull. Spatial expansion adds internal hull capacity while leaving her exterior unchanged, at the cost of gravitational or continuity traces that ports can detect.
The cockpit view would focus on physical flight: heat, exposed radiators, mass, power routing, stealth, and component damage. A tactical view could show Nibu's sensor picture as a gravitational-potential map, with ships reduced to schematics and anomalies bending the field. The opening tutorial would teach this combat inside the anomaly, then break Nibu's routine when a survivor gets through her defenses and attaches to the hull.
When a run fails, Nibu escapes by retreating into Infinite Fun Land as her physical shell is lost and the branch collapses. Players earn Aetheric power by surviving runs and investigating other anomalies, then spend it on small efficiencies or expanded internal space. The carryover should express Nibu's unusual continuity without turning the wider reset into a simple upgrade treadmill; [[Game Design/Persistent Universe and Reset Loop|Persistent Universe and Reset Loop]] leaves that product boundary open.
## Parallax Auditors Conspiracy
Nibu's early anomaly contributes to the rise of the [[Worldbuilding/Post-Elysium/Factions/Parallax Auditors|Parallax Auditors]]. Her impossible access records and the junkyard deaths help drive ports and insurers to formalize continuity investigations. Her case is one cause among several for an institution that serves many clients.
The Auditors' secret inner circle uses necrotech continuity engines made from harvested esper minds to retain selected memories across resets and conceal its actions from everyone else. Nibu's reset smear lets her accumulate evidence against them. The secret protects itself because everyone outside the circle forgets when a branch collapses, making ordinary exposure futile.
Nibu breaks the circle's monopoly by releasing continuity-engine methods to the public. Cross-reset archives become a contested shared resource, connecting Terminus to a later persistent-world game.
## Who Can Decide What Happens to Her
Nibu does not need to lose a personhood dispute for an institution to restrict her. Under [[Worldbuilding/Post-Elysium/Concepts/Ship Mind Custody|ship mind custody]] regimes, the same vessel can be treated as a route supervisor, a hazardous system, a salvage asset, or a claimant whose rights remain disputed. Which treatment applies depends on the transaction.

22
Aetheria/Spoilers.md Normal file
View file

@ -0,0 +1,22 @@
---
title: Spoilers
description: "What Elysium actually is. Read this only if you have decided you would rather know than find out."
---
# Spoilers
**Stop here if you are playing, or plan to.** This page answers questions the setting deliberately leaves open. Nothing on it is hidden; Aetheria is open source, and you are free to read it. But the in-world pages keep these answers vague on purpose, and the game is more fun if you work them out yourself. If you contribute lore, read it so your writing stays consistent, then please don't spoil it for anyone else.
Everything below is authorial truth. No character, faction, or document in Elysium knows it for certain, and in-world text should never state it outright.
---
## The field is anchored by the minds inside it
The [[Worldbuilding/Post-Elysium/Concepts/Aether|Aether]] does not obey rules the way Sol physics does. It is anchored by the cognition of Elysium's residents, and it settles toward what those minds take for granted. Flat space holds where people expect it to. Exported [[Worldbuilding/Post-Elysium/Factions/Wavecrafters|Wavecrafter]] components work better where the public finds them plausible, which is why the masquerade around them is load-bearing.
## Megiddo is half right
[[Worldbuilding/Post-Elysium/Factions/Megiddo|Megiddo]] suspects that Elysium is not the creation humanity came from: a constructed world, perhaps a simulation, held together by its residents' attention. About the mechanism, they are right.
They are wrong that there is a way back. No disclosure is coming that returns anyone to the old creation. Elysium is all anyone has, and so it is as real as it needs to be. The tragedy of Megiddo is not that its doubt is foolish, but that it is correct and leads nowhere: a fortress built to wait for an arrival that cannot happen.

View file

@ -60,6 +60,10 @@ Outsiders call the Vaults corpse worlds or freezer crypts. Megiddo records them
Megiddo consists of a handful of mobile fleets, each carrying a Vault through its migrations. A Vault is spherical, enclosing the greatest possible volume within the least armored surface. Its armor is a final precaution. Its principal defense is that almost nobody knows where it is.
The fleets do not hold fixed stations. A fleet seen in one region need not be found there again, so a setting that places Megiddo in a given zone describes where it was met, not where it lives. A game run may put a fleet in a different zone each time; that is text only for now, recorded as a post-demo reading in [[Game Design/Faction Play#Lore Change Proposals|Faction Play]] (ruling by Nibu, 2026-11-05), and nothing in the build moves a fleet yet.
If the per-run fleet move is ever built, it attaches to the Megiddo faction record that `MinorPowerFactionsCommand.cs:25-39` authors (GameCult/Aetheria, AetherDb tooling, read at master a4be037a4). The move is still text only and post-demo; no mechanic is claimed.
The fleet does not visibly escort its Vault. Industry, habitation, decoys, tenders, and defensive vessels spread across an enormous moving volume. Somewhere among them travels one cold, deliberately unremarkable object. Most of the fleet's own maps omit it, along with every other map that could usefully direct an attacker to it.
Keeping it cold requires contact with the outside, but that contact is designed to conceal its origin. Massively redundant cryogenic machinery transfers accumulated heat through closed coolant circuits into exchange masses. A compartmentalized ferry chain carries those masses among vessels and remote heat-rejection sites. Each participant knows too little to reconstruct the route from a radiator back to the Vault. Cold masses return through a different chain.

View file

@ -49,6 +49,14 @@ Commercial descriptions hide the different practices inside tamper-proof modules
The customer receives an operating envelope and a replacement contract. Opening the mechanism usually destroys the retained relation. It also gives the supplier convenient evidence of customer misuse.
### Why the Masquerade Holds
In sect territory, cultivation is not a hidden art. It is how the practitioners' reality works, and they practise it openly among people who expect it to work.
Flatspace is different. Exported components work better where the public finds them plausible. A dockside full of crews who take a *proprietary wave-function entanglement synchronizer* for ordinary engineering lets the retained relation hold steadily. A public convinced the component is fraud, or sorcery, makes it hold worse.
The commercial descriptions are therefore load-bearing. They hide practitioners from liability, and they also keep the product plausible to the people around it. A scandal exposing the sacred work behind a product line threatens more than sales: it can degrade the line's performance across a market.
### Industrial Secrecy
The inner practice depends on human and machine minds whose acknowledged involvement would turn a certified product into an esper-liability case. Export records therefore document materials, tolerances, and procedures while omitting who produced the exceptional result.

View file

@ -0,0 +1,47 @@
# Wonderland
*"Stay tuned."*
Wonderland is a small splinter of [[Worldbuilding/Pre-Elysium/Factions/Powers/Major/Lucent Media|Lucent Media]] living deep in [[Worldbuilding/Post-Elysium/Concepts/Pseudospace|pseudospace]]. Its people descend from Lucent's [[Worldbuilding/Pre-Elysium/Factions/Movements/Reality Architects|Reality Architects]]: the editors, predictive dramaturges, and perception engineers who once shaped how audiences understood events. They took the name the core worlds gave the frontier and made it theirs. Outsiders who say "Wonderland" are rarely sure whether they mean the territory or the people in it, and the people prefer it that way.
They have Lucent's taste for spectacle. Everything else about them is louder.
### The Break
The Architects noticed what had changed sooner than almost anyone. Their trade before the Rupture was attention: what an audience takes for granted, and how to arrange it. Afterwards, Lucent's own behavioural data showed anomalies tracking what audiences expected, and the Architects understood what that meant for a profession built on framing.
Lucent itself never needed to say so. In the core worlds, framing what billions of people expect is its business, and if that also helps keep flat space flat, the company has no reason to examine it. The Architects who left wanted to examine it closely. In the settled worlds, a frame needs a vast audience to hold against everyone else's expectations. Out where consensus is thin, a small crew rehearsed into one tightly shared frame can hold local reality on its own. The crew becomes its own audience.
Wonderland regards Lucent with professional contempt. Lucent broadcasts reality. Wonderland lives inside the edit.
### The Show Must Go On
A Wonderland habitat holds together only while its people keep performing the frame they share. Shifts are staggered so someone is always on. Rest is scheduled the way a broadcaster schedules reruns. Dead air is treated as a hull breach, because it can become one.
Standing works the way it did on Lucent's platforms, except that the stakes are physical. Whoever the crew watches most has the most pull on what the habitat does. Status games are survival, and a coup is a ratings coup. A member who falls into disgrace finds their surroundings cooperating less: a door that hesitates to recognize them, a corridor's gravity that takes a moment longer to agree.
Old Lucent habits continue in stranger forms. The faction keeps the personas of dead performers on the air, because the attachment many people share to a familiar character steadies the region around it. Cancelling a long-running show can fray the space it held.
### Genre
Each habitat runs on a genre its people have rehearsed together, and the genre's conventions are the local rules. In a noir station it always rains in the corridors. In a sitcom habitat, injuries are gone by the next episode. At a thriller depot, every exchange has a twist whether anyone wants one or not.
The conventions are strict and they can be learned. That is the only reason outsiders survive. A habitat's weirdness has a grammar, and a visitor who reads it can predict what the place will do.
Some failures are as old as the format. A habitat can get stuck in its own opening credits, because starting the episode would mean committing to a plot, and plots have consequences. Its people stay in the safe part, smiling, while the cast keeps growing. When two habitats' frames touch, conventions bleed together: a sitcom kitchen lit like a crime drama, with a cartoon's physics, and nobody certain whose rules apply.
What a frame cannot cast, it cannot protect anyone from. An outsider with a strong enough frame of their own, an [[Worldbuilding/Post-Elysium/Technology/Necrotech|Eidolon]], or a [[Worldbuilding/Post-Elysium/Factions/Death Monkey Explosives|DME]] practitioner who has become unbeing can walk through every genre untouched. To the habitat, they are something in the background that the story has no part for.
### Visiting
Traders, salvagers, and the lost who deal with Wonderland learn its etiquette or do not come back. The rules have the shape of old stories about the fair folk:
- **Don't contradict the genre.** It will fight you.
- **Don't play along too well.** It will adopt you.
- **Don't give your name on camera.** Named, you get a title card, and a title card is how the show casts you.
- **Don't accept props.** A gift, an offered drink, or a line handed to you is a role, and accepting it is accepting the part.
- **Never name the show.** Asking aloud what genre this is contradicts the frame from inside it.
- **Hit your marks and don't improvise.** A flat bit part is safe. A brilliant ad-lib gets you renewed for another season.
- **Mind the episode clock.** A visitor can spend one episode in a habitat and leave to find a season has passed outside, with [[Worldbuilding/Post-Elysium/Concepts/Temporal Nonlinearity|continuity residue]] to show for it.
Staying too long ends the same way however careful the visitor has been. They wave at the camera one day without meaning to, their name comes up, and they are a recurring character. Leaving after that means being written out, and genres have opinions about how characters get written out.

View file

@ -25,6 +25,10 @@ Post-Elysium factions are organized groups that have learned to gain power from
- [[Worldbuilding/Post-Elysium/Factions/Megiddo|Megiddo]]
## Pseudospace Splinters
- [[Worldbuilding/Post-Elysium/Factions/Wonderland|Wonderland]]
## Related Branches
- [[Worldbuilding/Post-Elysium/index|Post-Elysium]]

View file

@ -38,7 +38,9 @@ For a necrofactory, a fast-grown source that reliably produces one limited effec
That preference does not make the supply cheap or effortless. Breeding lines require gestation, care, assessment, containment, and continuing maintenance of genetic diversity. Some sources fail to develop as needed. A factory short of viable brains cannot replace them with anonymous cadavers: preservation can retain a brain's structure, but it cannot give that brain resonance it never developed.
These lines supply the baseline market. Their products include disposable guidance spirits, sensor interpreters with limited roles, industrial field regulators, and other ARIs bought for predictable output and routine replacement.
Factory sources are not simply harvested young. They are conditioned before imprinting: just enough to dissociate from reality in the specific way the intended product needs, so that when a nascent mind is blasted into its host, what binds is that one useful relation. A complex world model was never necessary for the purpose, so none is grown. The resulting ARIs are simple because they were made that way, and they are difficult to describe as conscious.
These lines supply the baseline market. Their products include disposable guidance spirits, sensor interpreters with limited roles, industrial field regulators, and other ARIs bought for predictable output and routine replacement. The cheapest end reaches ordinary households: an ARI in a refrigerator that improves its Carnot efficiency, installed beside the brainwashed upload that lets the same refrigerator order groceries.
### Eidolons
@ -142,4 +144,6 @@ Manufacturers do not publicly agree about what this maintenance does. It may sus
Corporate media presents ARIs as humane resonance devices: scientifically non-conscious and categorically separate from the people whose brains were destroyed. This argument treats the biological source, the destructive transfer, and the installed instrument as three unrelated objects.
For most units sold, the claim about the instrument is close to true: a factory ARI was built to need no world model and holds little that could be called a point of view. That accuracy is what makes the argument useful. It says nothing about Eidolons, and nothing about the conditioned children whose brains were destroyed to make the simple ones.
The political dispute concerns whether that separation is real, and what follows if it is not. Institutions controlling the brains, the transfer, and the finished products also control the classifications under which evidence of recognition, distress, and preference is handled. Their ownership gives them the power to call the result equipment; whether it makes the result equipment is the question their terminology does not answer.

View file

@ -12,6 +12,11 @@ Writers do not need custody of the whole universe. Shared notes own their stated
- **Writers:** read [`Narrative Themes`](Aetheria/Narrative%20Themes.md), the relevant owner notes, and the public [`branch-and-fold process`](Aetheria/Stories/How%20Branching%20Stories%20Are%20Made.md). Finished work lives under [`Fiction`](Aetheria/Fiction/index.md); [`Stories`](Aetheria/Stories/index.md) includes shorter and developmental work.
- **Maintainers:** site-specific configuration lives under `site/`; the shared Quartz engine and build behavior live in `GameCult-Quartz`.
## Status
- **Live:** the vault is the source of [aetheria.gamecult.org](https://aetheria.gamecult.org), built and deployed by `.github/workflows/deploy-quartz.yml` through the shared engine in `GameCult-Quartz`; `scripts/quartz/quartz.ps1` runs it locally.
- **Not canon:** `Brainstorming/` and `Inspiration/` branches are excluded from publication. They are working material, and notes in them become setting only when a finished story or an owner note adopts them.
## Repository Map
- `Aetheria/`: source vault content and media; publication is filtered by the site configuration
@ -25,12 +30,12 @@ Internal `Brainstorming/` and `Inspiration/` branches are excluded from publicat
## Local Development
Local builds expect `GameCult-Quartz` either at the sibling path `E:\Projects\GameCult-Quartz` or at the path supplied through `GAMECULT_QUARTZ_ROOT`.
Local builds expect `GameCult-Quartz` either at the sibling path `..\GameCult-Quartz` or at the path supplied through `GAMECULT_QUARTZ_ROOT`.
Install the shared engine dependencies first:
```powershell
cd E:\Projects\GameCult-Quartz
cd ..\GameCult-Quartz
npm ci
```

View file

@ -0,0 +1,117 @@
#!/usr/bin/env python3
"""Canon/proposal marker check. Usage: check_canon_marker.py <base-ref>
Checks .md files under Aetheria/ added, modified or renamed against <base-ref>.
Proves the form and presence of ruling ids, not that the ruling exists.
"""
import re, subprocess, sys
import yaml
ID = re.compile(r"^[a-z0-9][a-z0-9-]*:ruling:[a-z0-9][a-z0-9._-]*$")
def git(*a):
return subprocess.run(["git", *a], check=True, capture_output=True, text=True).stdout
class UniqueKeyLoader(yaml.SafeLoader):
"""safe_load that refuses a repeated key: one page, one reading of `kind`."""
def construct_mapping(self, node, deep=False):
seen = set()
for key_node, _ in node.value:
key = self.construct_object(key_node, deep=True)
if key in seen:
raise yaml.constructor.ConstructorError(
None, None, f"duplicate key {key!r}", key_node.start_mark)
seen.add(key)
return super().construct_mapping(node, deep)
FRONT = re.compile(r"---\n(?:(.*?)\n)?---[ \t]*(?:\n|\Z)", re.S)
def frontmatter(text):
"""Return (kind, rulings or None, error). Frontmatter is real YAML."""
if not text.startswith("---\n"):
return None, None, None
m = FRONT.match(text)
if not m:
return None, None, "unterminated frontmatter"
try:
data = yaml.load(m.group(1) or "", Loader=UniqueKeyLoader)
except yaml.YAMLError as e:
return None, None, f"frontmatter is not valid YAML ({type(e).__name__}: {e})"
if data is None:
data = {}
if not isinstance(data, dict):
return None, None, "frontmatter must be a mapping"
kind, rulings = data.get("kind"), data.get("rulings")
if kind is not None and not isinstance(kind, str):
return None, None, "kind must be a string"
if rulings is not None and not (isinstance(rulings, list) and all(isinstance(r, str) for r in rulings)):
return None, None, "rulings must be a list of strings"
return kind, rulings, None
def changed(base):
"""(status letter, path) for each page added, modified or renamed (the new path)."""
out = git("diff", "-z", "--name-status", "--diff-filter=AMR", f"{base}...HEAD", "--", "Aetheria")
fields = out.split("\0")
rows, i = [], 0
while i < len(fields) and fields[i]:
st = fields[i]
if st[0] == "R":
rows.append(("R", fields[i + 2]))
i += 3
else:
rows.append((st[0], fields[i + 1]))
i += 2
return rows
def main(base):
try:
rows = changed(base)
except subprocess.CalledProcessError as e:
print(f"CANON CHECK FAILED: cannot diff against {base!r}: {e.stderr.strip()}")
return 1
failed = False
for st, path in rows:
if not path.endswith(".md"):
continue
try:
with open(path, encoding="utf-8-sig") as f:
kind, rulings, err = frontmatter(f.read())
except (OSError, UnicodeDecodeError) as e:
kind, rulings, err = None, None, f"cannot read page ({type(e).__name__})"
problem = None
if err:
problem = err
elif kind is None:
if st == "A":
problem = "new page needs `kind: canon` or `kind: proposal`"
else:
print(f"notice: {path} has no kind (legacy); tag it when you next touch it")
elif kind == "canon":
bad = [r for r in (rulings or []) if not ID.fullmatch(r)]
if not rulings or bad:
problem = ("kind: canon requires `rulings:` with at least one id of the form "
f"<campaign>:ruling:<label>\n (found: {bad or 'none'})")
elif kind == "proposal":
if rulings:
problem = "kind: proposal may not carry `rulings:`"
else:
problem = f"kind must be canon or proposal (found: {kind})"
if problem:
failed = True
print(f"CANON CHECK FAILED: {path}\n {problem}\n"
" A ruling must exist before its text enters a canon page. "
"Put the text in a `kind: proposal` page until it does.")
return 1 if failed else 0
if __name__ == "__main__":
sys.stdout.reconfigure(encoding="utf-8")
sys.exit(main(sys.argv[1]))

View file

@ -0,0 +1,206 @@
"""Tests for scripts/check_canon_marker.py: each builds a throwaway git repo
with a main branch, adds pages on a branch, and runs the check against main."""
import os
import subprocess
import tempfile
import unittest
SCRIPT = os.path.join(os.path.dirname(__file__), "..", "check_canon_marker.py")
RULING = "aetheria-lore:ruling:megiddo-origin"
def git(cwd, *args):
subprocess.run(["git", "-c", "user.email=t@t", "-c", "user.name=t", *args],
cwd=cwd, check=True, capture_output=True)
class Repo:
def __init__(self):
self.tmp = tempfile.TemporaryDirectory()
self.dir = self.tmp.name
git(self.dir, "init", "-b", "main")
os.makedirs(os.path.join(self.dir, "Aetheria"))
self.write("Aetheria/Legacy.md", "old page, no marker\n" + "line of lore\n" * 20)
git(self.dir, "add", "-A")
git(self.dir, "commit", "-m", "base")
git(self.dir, "checkout", "-b", "pr")
def write(self, path, text):
full = os.path.join(self.dir, path)
os.makedirs(os.path.dirname(full), exist_ok=True)
with open(full, "w", encoding="utf-8") as f:
f.write(text)
def commit(self):
git(self.dir, "add", "-A")
git(self.dir, "commit", "-m", "pr")
def check(self):
p = subprocess.run(["python3", SCRIPT, "main"], cwd=self.dir,
capture_output=True, text=True)
return p.returncode, p.stdout + p.stderr
def canon(rulings, kind="canon"):
return f"---\nkind: {kind}\nrulings:\n{rulings}---\nbody\n"
class CanonMarker(unittest.TestCase):
def run_pages(self, pages, after=None):
r = Repo()
for path, text in pages.items():
r.write(path, text)
if after:
after(r)
r.commit()
return r.check()
def test_a_canon_page_with_a_ruling_id_passes(self):
code, out = self.run_pages({"Aetheria/A.md": canon(f" - {RULING}\n")})
self.assertEqual(code, 0, out)
def test_a_canon_page_without_a_ruling_fails(self):
code, out = self.run_pages({"Aetheria/A.md": "---\nkind: canon\n---\nx\n"})
self.assertEqual(code, 1, out)
def test_a_non_ascii_path_is_checked_not_skipped(self):
code, out = self.run_pages({"Aetheria/Framgång.md": "---\nkind: canon\n---\nx\n"})
self.assertEqual(code, 1, out)
self.assertIn("Framgång.md", out)
def test_a_renamed_page_is_checked(self):
def rename(r):
git(r.dir, "mv", "Aetheria/Legacy.md", "Aetheria/Moved.md")
r.write("Aetheria/Moved.md", "---\nkind: canon\n---\n" + "old page, no marker\n" + "line of lore\n" * 20)
code, out = self.run_pages({}, after=rename)
self.assertEqual(code, 1, out)
self.assertIn("Moved.md", out)
def test_quoted_values_parse(self):
text = f'---\nkind: "canon"\nrulings:\n - "{RULING}"\n---\nx\n'
code, out = self.run_pages({"Aetheria/A.md": text})
self.assertEqual(code, 0, out)
def test_a_trailing_comment_on_a_ruling_is_not_part_of_the_id(self):
code, out = self.run_pages({"Aetheria/A.md": canon(f" - {RULING} # megiddo\n")})
self.assertEqual(code, 0, out)
def test_a_flow_list_of_rulings_parses(self):
text = f"---\nkind: canon\nrulings: [{RULING}, weksa:ruling:other]\n---\nx\n"
code, out = self.run_pages({"Aetheria/A.md": text})
self.assertEqual(code, 0, out)
def test_cross_campaign_ruling_ids_count(self):
code, out = self.run_pages({"Aetheria/A.md": canon(" - weksa-body:ruling:faction-play-1\n")})
self.assertEqual(code, 0, out)
def test_a_malformed_ruling_id_fails(self):
code, out = self.run_pages({"Aetheria/A.md": canon(" - megiddo-origin\n")})
self.assertEqual(code, 1, out)
def test_a_proposal_may_not_carry_rulings(self):
code, out = self.run_pages({"Aetheria/A.md": canon(f" - {RULING}\n", kind="proposal")})
self.assertEqual(code, 1, out)
def test_a_proposal_without_rulings_passes(self):
code, out = self.run_pages({"Aetheria/A.md": "---\nkind: proposal\n---\nx\n"})
self.assertEqual(code, 0, out)
def test_an_unknown_kind_fails(self):
code, out = self.run_pages({"Aetheria/A.md": "---\nkind: draft\n---\nx\n"})
self.assertEqual(code, 1, out)
def test_a_new_untagged_page_fails(self):
code, out = self.run_pages({"Aetheria/A.md": "no frontmatter\n"})
self.assertEqual(code, 1, out)
def test_a_touched_legacy_page_passes_with_a_notice(self):
code, out = self.run_pages({"Aetheria/Legacy.md": "old page, edited\n" + "line of lore\n" * 20})
self.assertEqual(code, 0, out)
self.assertIn("notice", out)
def test_invalid_yaml_fails_instead_of_crashing(self):
code, out = self.run_pages({"Aetheria/A.md": "---\nkind: [canon\n---\nx\n"})
self.assertEqual(code, 1, out)
self.assertNotIn("Traceback", out)
def test_a_non_mapping_frontmatter_fails(self):
code, out = self.run_pages({"Aetheria/A.md": "---\n- canon\n---\nx\n"})
self.assertEqual(code, 1, out)
self.assertNotIn("Traceback", out)
def test_a_python_object_tag_is_refused_not_executed(self):
text = "---\nkind: !!python/object/apply:os.getcwd []\n---\nx\n"
code, out = self.run_pages({"Aetheria/A.md": text})
self.assertEqual(code, 1, out)
self.assertNotIn("Traceback", out)
def test_a_repeated_key_fails(self):
text = f"---\nkind: proposal\nkind: canon\nrulings:\n - {RULING}\n---\nx\n"
code, out = self.run_pages({"Aetheria/A.md": text})
self.assertEqual(code, 1, out)
self.assertIn("duplicate", out)
def test_a_bom_does_not_hide_the_marker(self):
code, out = self.run_pages({"Aetheria/Legacy.md": "\ufeff---\nkind: canon\n---\nx\n"})
self.assertEqual(code, 1, out)
def test_a_ruling_id_with_a_trailing_newline_is_malformed(self):
text = f'---\nkind: canon\nrulings:\n - "{RULING}\\n"\n---\nx\n'
code, out = self.run_pages({"Aetheria/A.md": text})
self.assertEqual(code, 1, out)
def test_empty_frontmatter_is_a_kindless_page_not_unterminated(self):
code, out = self.run_pages({"Aetheria/A.md": "---\n---\nx\n"})
self.assertEqual(code, 1, out)
self.assertNotIn("unterminated", out)
self.assertIn("needs `kind", out)
def test_a_lookalike_closing_marker_does_not_end_the_frontmatter(self):
text = "---\nkind: proposal\n----\nstill frontmatter?\n---\nx\n"
code, out = self.run_pages({"Aetheria/A.md": text})
self.assertEqual(code, 1, out)
def test_a_renamed_legacy_page_passes_with_a_notice(self):
def rename(r):
git(r.dir, "mv", "Aetheria/Legacy.md", "Aetheria/Moved.md")
code, out = self.run_pages({}, after=rename)
self.assertEqual(code, 0, out)
self.assertIn("notice", out)
def test_a_page_main_changed_after_the_branch_point_is_not_charged_to_the_pr(self):
# Old.md is a bad canon page that main already holds; the PR merges it in
# and does not touch it, then main edits it again. Two-dot diffing
# would see the PR's copy as modified and fail the PR for main's page.
r = Repo()
r.write("Aetheria/Mine.md", "---\nkind: proposal\n---\nx\n")
r.commit()
git(r.dir, "checkout", "main")
r.write("Aetheria/Old.md", "---\nkind: canon\n---\nv1\n")
git(r.dir, "add", "-A")
git(r.dir, "commit", "-m", "main adds Old")
git(r.dir, "checkout", "pr")
git(r.dir, "merge", "--no-edit", "main")
git(r.dir, "checkout", "main")
r.write("Aetheria/Old.md", "---\nkind: canon\n---\nv2\n")
git(r.dir, "add", "-A")
git(r.dir, "commit", "-m", "main edits Old")
git(r.dir, "checkout", "pr")
code, out = r.check()
self.assertEqual(code, 0, out)
def test_an_unknown_base_ref_fails_loudly_without_a_traceback(self):
r = Repo()
p = subprocess.run(["python3", SCRIPT, "no-such-ref"], cwd=r.dir,
capture_output=True, text=True)
self.assertEqual(p.returncode, 1)
self.assertNotIn("Traceback", p.stdout + p.stderr)
self.assertIn("no-such-ref", p.stdout + p.stderr)
def test_pages_outside_aetheria_are_not_checked(self):
code, out = self.run_pages({"README2.md": "---\nkind: canon\n---\nx\n"})
self.assertEqual(code, 0, out)
if __name__ == "__main__":
unittest.main()