The stuff between the numbered rooms, in the same 1974 two-ink screen print:
the blast door from inside, the stair, the exchange, the laundry, washroom,
stores, water gallery, cloakroom, kitchen, chapel, workshop, library, barber's
corner, mushroom beds, play space, a family cabin, battery room, ventilation
gallery, haulage incline and the memorial garden. All twenty ride in the
adventure's plate list as 21-40.
Six were regenerated for daylight or the wrong century, and so_27 needed three
attempts: 'changing room' is this scenario's blocked phrase. Both lessons are
in the art sheet.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Generated on the first attempt once it was the only job in flight, which is
another mark against the banned-word story it was used to support.
One thing to know before it reaches a table: a martlet is the heraldic bird
drawn WITHOUT FEET, and this plate has feet, with claws. The prompt says "the
little bird drawn with no feet, which therefore has none" — and naming a
thing to exclude it puts it in, which is recorded in the vault from the CLEAN
GROUND art ("no birds, no sheep" produced livestock). Fixing it means
rewording the creature's own description positively, which is content, so it
is left for Tim rather than changed here.
moor_cat is the one that did not land, and it is now well characterised:
its job is ACCEPTED and STARTS — the bot posts — and Midjourney then DELETES
its own post. That is the image being flagged mid-generation rather than the
prompt being refused, which is why six attempts, three hypotheses and a
prompt bisection all came to nothing. It keeps its procedural portrait, which
since this evening is drawn as a quadruped with eight hit locations rather
than as a man.
~/bin/mj-blocked now distinguishes all three modes: nothing posted (refused
before starting), posted and deleted (image flagged), posted and still there
(genuinely running). The first version would have called the deleted case
"not blocked" and been wrong.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0b51d4e claimed the martlet's three stalls were caused by the word "bare" and
said it was diagnosed rather than guessed. It was guessed.
The evidence was one successful regeneration with that word replaced. Run
again afterwards with "bare" restored and nothing else changed, the same
prompt was accepted in seconds. The variable that actually differed was that
the successful run was the only job in flight — and the word was believed
because a memory note from 16 September already named it, which is a reason
to suspect a conclusion rather than to trust it.
Two further hypotheses tested and also dead: moor_cat's full prompt is
accepted immediately, so it is not blocked either; and four jobs fired two
seconds apart were all answered, so it is not a concurrency limit at that
scale. What made those two fail six times between them is not reproducible
now, and this commit does not claim to know.
The throw-instead-of-warn stays: for a genuinely banned word, a warning
printed into a log predicts a job that never arrives and never errors. The
armour wording stays too, because it reads better — not as a workaround.
~/bin/mj-blocked is the tool this needed from the start. It sends a prompt
and reports within two minutes whether the bot answered at all, because a
refusal is ephemeral and never reaches the channel, so silence there is the
only thing that separates a banned word from a slow one. Three sessions have
now spent 30-minute timeouts on this question.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diagnosed rather than guessed. The martlet failed three times over ninety
minutes while the gryphon succeeded in the same background run, so it was
neither the service nor the account nor the window. Regenerating it with the
single word "bare" replaced and nothing else changed brought it back
immediately.
It comes from armourWords at naturalArmour 0 — Midjourney reads it as nudity
— and thirteen creatures carried it, every one of them a creature with no
natural armour. That band says "thin-skinned, nothing between it and a blow"
now.
BANNED returned its hits as `warnings` for the caller to print. A warning in
a log nobody reads is precisely what let this stall three times, because the
failure it predicts is a job that never arrives and never fails, which looks
exactly like the service being slow. promptFor throws now, as it does for an
over-long negative list, and says why the refusal is invisible. All 204 specs
still build; a planted "corpse" is refused.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Eagle head and beak, wings fully drawn, lion hindquarters, four legs, on a
plinth — and drawn rather than plated. The first render had no wings and no
beak because the prompt read `species` where the shape lives in `bodyPlan`.
The second had the anatomy and came back as a mech, because the armour clause
opened with the word "armoured" and that is the word Midjourney draws.
Portrait and 2x2 token derived and the pack rebuilt. gryphon-fixed.webp — the
mech, kept while it was the only version with the right anatomy — is removed:
no spec referenced it, and a second picture of the same creature in the
shipped art is a thing for somebody to pick up by mistake.
Worth recording for the diagnosis of the other two: this succeeded in the
same background run where martlet and moor_cat each failed a third time. So
the failures are not the service, not the account and not the window. It is
those two prompts.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
LevelDB renumbers its files on every build, so this is filename churn around
unchanged content: 70 weapons, the 10 natural attacks still carrying
flags.ringbrp.plans. Committed so the tree is clean rather than left dirty
for the next person to wonder about.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The three sidebar buttons build actors through Actor.create, compendium reads
and a dialog, and check-behaviour says in its own header that it cannot reach
any of that. The derivations are covered by 450 forged combinations and 210
posting × tier pairs; the glue is covered by nothing, and no world was
running to exercise it.
So this is the shortest path from a launched world to knowing. Every expected
value in it was derived by running the code — drawKitFor for the kit rows,
forgeCreature at seed 7 for the forge rows — rather than written from memory.
It also says what a failure means: a wrong number points at the derivation
and should reproduce from the CLI, while a missing item or a dialog that does
not open points at the glue and will not.
One figure in the first draft — "476 guarded combinations" — was invented.
Replaced with the two the guards actually print. A verification document that
carries a made-up number is worse than none, because it is read as the
authority on what to expect.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
"When I create a new NPC or Threat they do not have a set of skills" was the
original report, and the kit fix did not cover all of it. A generated NPC
carried its posting's core plus two support — about eight rows — so a GM
asked for Listen or Dodge or Spot by a player had nothing on the sheet to
roll.
generateCharacter has called grantFullSkillList since it was written, and
build-packs gives all 62 to every packed creature, so the generated NPC was
the only actor in the game without them. It calls it now, in the same place
the PC path does: after the items, before stowOverload.
check-generator holds all three construction paths to it. A shared finishing
step that one of three callers omits is invisible from inside that caller,
which is why it is worth a check rather than a memory. Proved by removing the
call again.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three tools read spec.species to decide a creature's SHAPE and all three were
wrong the same way, because every creature with a non-human body carries
species "baseline" and says what it is in bodyPlan:
mj-queue drew a wingless gryphon
make-portraits drew a human silhouette for 48 creatures
bestiary published "26 of them are not human-shaped" when it is 74
Each was found by looking at the neighbour of the one before, which is not a
method — the fourth would have been found by a fourth accident. A line that
feeds a shape function from species without naming a resolved plan is the
whole defect, in one line, every time, so it is checkable.
Proved against the real thing rather than a planted one: checking out each
file's parent commit from history makes the guard report that file, at the
line the fix touched, and the current tree is clean.
The first version required the literal `bodyPlan` on the line and so reported
all three FIXED call sites, because the correct form resolves a local `plan`
once and then falls back to species on the next line — and that fallback is
right. A guard that calls the corrected code broken is exactly what
check-rules was reported for earlier tonight, one file over.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The document counted shape by `species`, which is vesh and cadence and
nothing else, so all 32 quadrupeds and all 16 winged creatures were counted
as people. It also printed each creature's hit-location count from the same
field, giving a person's 7 to a bull, a gryphon and every other body in the
book.
Third place tonight to read `species` where the shape lives in `bodyPlan`,
after mj-queue's anatomy clause — which drew a wingless gryphon — and
make-portraits' silhouette. Each was found by looking at the neighbour of the
one before it, and the third was the only one facing a reader.
The at-a-glance table marks quadrupeds Q and winged W beside the existing V
and C, because a two-ton quadruped and a man in a coat carried the same blank
and that table is the part that gets printed.
check-bestiary passes, which is worth stating precisely: it holds the
document against the statblocks, and both sides were reading the same wrong
field, so it was correct throughout and had nothing to say.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
portraitSvg read `spec.species` for both the silhouette and the hit-location
table. Every creature with a non-human body carries `species: "baseline"` and
says what it is in `bodyPlan`, so the guildhall gryphon's own generated
portrait described it as "baseline, 7 hit locations" and drew a human figure
for an eagle-lion with wings. 48 creatures were affected — 32 quadrupeds and
16 winged.
It is the same defect, in the same shape, as the anatomy clause in
mj-queue.mjs: that one read `species` where the shape lives in `bodyPlan`,
and drew a wingless gryphon. I fixed it there earlier tonight and did not
look one file over, in the other tool that draws a creature from its
statblock. R-264 settled this rule for the harness — `bodyPlan ?? species` —
and build-packs:294 writes it to the actor's speciesProfile.
Only two files change on disk, because 46 of the 48 already have hand-drawn
plates and are correctly skipped. Those two are martlet and moor_cat, whose
Midjourney art has now failed twice, so they are exactly the creatures
falling back on the generated figure: martlet is winged with 10 locations and
moor_cat quadruped with 8, where both were human before.
The other 139 rewrote byte-identically, which is what a deterministic
generator should do and is worth knowing.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
It opened "Status: plan only. Nothing below is built" while four of the five
phases had shipped, and its state table described a repo of 76 statblocks
with no simulator and no portraits — 204, six measuring guards and 47 plates
ago. A plan that misreports what exists sends the next reader to build it
again.
The table is kept rather than deleted because the design argues from it, with
a second column saying where each row landed. Part 5 is marked built and NOT
yet run in a world, which is the honest state.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Measuring the tier knob showed it works — one creature against the four
agents check-lethality freezes, deaths per fight climb 0.01, 0.04, 0.32,
0.91, 1.43 across the five tiers for a large brute, and monotonically for
hunters and flyers too.
It also showed the labels oversell. "Deadly" at tier 3 kills a third of an
agent and wipes the team three times in a thousand. A GM reaching for a word
like that is owed the figure behind it, and the forge's whole argument is
that its output can be interrogated — the tier list was the one part of it
that could not be. Each tier now carries a measured `worth` line, printed by
`forge list` and under the tier selector in the dialog.
check-forge measures the ladder and fails if it ever goes down, across three
roles and five tiers. Both the labels and the worth lines are claims about
behaviour that any change to the skill bands, the hide base or the
characteristic multiplier could falsify without touching a word. Proved by
weakening tier 4: three roles report the inversion by name.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A creature with no entry in the baseline was printed as a note and then
counted in the success line, which read "every one fighting exactly as
recorded" while N of them had no record to fight differently from. The claim
was false by exactly the number in the note above it, and a note is the part
a green build does not get read for.
It is the same shape this guard was already on the wrong side of once: before
the seam fix it measured 47 creatures and printed OK for 184.
Recording a new creature is one --update in the commit that adds it, which
this guard's own failure message has always instructed. Proved by planting a
creature with no baseline: it now stops the build and names it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The gryphon fix added six armour negatives and three weapon ones, which took
the prompt to eight --no terms. This project has a recorded case where ten or
more never returned a grid at all while the same prompt with four came back
in two minutes — and a job that never arrives is indistinguishable from a
moderation refusal, because those are ephemeral and never appear in the
channel either. It cost twenty minutes of wondering whether the account was
out of fast hours, and the note about it was written down precisely so it
would not be diagnosed from scratch a second time. I walked into it anyway.
Trimmed to three armour terms and one weapon term, which puts every prompt at
five. promptFor now throws above six and names the offending terms, so the
next person to reach for a long negative list is stopped at the tool rather
than by a half-hour stall. All 204 specs build under the cap.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
check-kits has asserted this for the 36 postings since it was written — "every
posting can use what it carries" is in its success line. Nothing asserted it
for the creatures, and 35 of them hold a weapon they have no skill for. The
hollow man has a dagger and no knife. The hulk haunt has a boarding axe and
no axe. One PREGEN carries a pistol she cannot fire.
It is not cosmetic. simulate.mjs sorts a combatant's arms by expected damage
and an unskilled weapon sits at the 1% floor, so it loses to the creature's
own fists every time: the statblock advertises a dagger and the thing
punches. That is R-310's defect written down rather than generated.
Recorded, not fixed. Giving each of the 35 the missing skill means choosing a
rating, and a rating is a balance decision that moves check-lethality's
numbers for every creature touched — that belongs to whoever owns the game.
The 35 are held at a ratchet that may shrink and may never grow, so no new
creature can be written holding something it cannot use.
Specs are expanded through the register first. A spec written as a job has no
skills of its own, and judging one unexpanded reports a Field Officer as
unable to fire the pistol her own posting issues her.
--update refused to create the record it needs on its first run, because with
no file on disk all 35 existing cases counted as new. The first recording is
the baseline; only later ones are held to the ratchet.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
CREATURE_FORGE_PLAN Part 5. A third button on the Actors sidebar, beside New
agent and New NPC. Pick what it does, how big it is and how bad it is; the
card underneath describes what those settings will actually produce, because
the argument for a derivation over a form is that it can be interrogated, and
choosing between "brute" and "sentinel" from two nouns is not interrogating
anything. The card is itself forged rather than written, so it cannot
describe a creature the derivation would not make.
generateCreature reads the catalogues out of the packs and calls the same
forgeCreature the CLI calls. Natural attacks carry their body-plan
declarations into flags.ringbrp.plans so the engine can read them.
The plan asks that the panel and the CLI cannot diverge, and importing one
derivation was most of that guarantee but not all of it: the two feed it from
DIFFERENT catalogues — content.mjs on one side, the built compendium on the
other. check-forge now builds the engine's view straight out of packs/weapons
and requires both to forge the same creature.
It found a divergence on its first run, in 40 of 90 pairs. The fallback took
the first usable natural attack from the caller's list, and that list arrives
in declaration order from content.mjs and in id order from the pack, so a
tiny vesh brute was punching for the CLI and constricting at the table. The
derivation may not depend on its caller's iteration order; it imposes its
own now.
Not yet verified in a running Foundry. The pure derivation is covered by 450
guarded combinations and the catalogue seam by the agreement check above, but
Actor.create, the pack reads and the dialog itself are the part
check-behaviour says outright it cannot reach. They need a world open, and
that has not happened yet.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
CREATURE_FORGE_PLAN Part 3. `new` prints a spec as source in the shape the
bestiary files are written in, `explain` prints the rule behind every value,
`measure` fights it against the party check-lethality freezes, and `list`
shows the knobs.
The derivation is forge.mjs at the ROOT, beside rules.mjs and postings.mjs
and under the same law: pure, no Foundry, no catalogues. Part 5 asks for an
in-Foundry panel that forges a variant at the table and says it must not
diverge from the CLI. One derivation in a module both import is the only way
to guarantee that rather than argue it.
Natural attacks now declare which body plans can make them, in the weapon
catalogue, for the same reason a weapon already names the skill that fires
it: the weapon is the thing that knows. Anatomy cannot answer it — a body
plan records that a creature has a head, not that the head has horns.
`explain` earned itself on the first run. A large brute derived with a
baseline body could not gore, trample or hoof, and the trace said so; the
finished statblock alone would have shipped bulls that bite. The role picks
the body now, a non-baseline species overrides it, and --body beats both.
check-forge (guard 26) derives all 450 combinations of role, size, tier and
species and puts each through the bestiary's own validate(). Three mutations
were planted in the forge to test it, and it caught one. Dropping the seed
was caught. Dropping the brawl grant was a genuine no-op, since every role
already lists brawl. Dropping the body-plan filter left all 450 rows green
while the success line read "armed with something its body can use" — the
guard read the location table and never used it. It checks each issued weapon
against the catalogue's own declaration now, and the same mutation produces
500 failures.
check-rules' inline-armour pattern matched any clamp containing the word, and
false-positived three times in one evening on counts that were never damage.
damageAfterArmour is a subtraction, so the pattern requires one. A guard that
makes people contort working code to keep it quiet is training them badly.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The illustrations were sitting in art/creatures/, where nothing looked for
them. build-packs resolves a creature's picture by stem under art/portraits/,
so none of the 47 reached the game.
tools/make-art.py (was make-tokens.py) now derives both from one plate:
art/portraits/<key>.webp and art/tokens/<key>.webp. Same drawing, so the
token cannot disagree with the portrait — the argument mj-queue already makes
for deriving prompts from statblocks.
Webp because every one of the 309 art files already here is one, at 160-220
KB. The raw Midjourney plates are 2.3 MB each; 47 of them would have put 93
MB into a 29 MB repository permanently, for pictures nothing renders at that
size. At quality 88 a plate is ~300 KB with the pencil hatching intact. The
plates stay on disk as working files and are gitignored.
The token lookup in build-packs was a hardcoded `.png`, so the first webp
token would have silently fallen back to the portrait and Foundry would have
gone back to cropping a 2:3 plate into a circle. Portraits and tokens now
share one resolver and one extension list.
146 of 147 npcs carry a portrait and 46 a derived token.
Also: the gryphon came back as a mech a second time. The first fix branched
the armour SIMILE on era while both arms still opened with the word
"armoured", and that word is what Midjourney draws — changing the reasoning
is not the same as changing the cause. No natural creature's prompt contains
"armour" now, and negativesFor() asks for plate, machinery and worn armour to
be left out, because a word choice is an argument and a --no is closer to a
guarantee.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
generateNPC read R.core, R.support and R.label. It never read R.kit, so the
role card's DRAWS FROM STORES promised a Containment officer nine items and
the actor arrived holding a utility knife with a flat naturalArmour standing
in for armour it was never issued.
postings.mjs now owns the decision — drawKitFor(role, tier, {classify}) plus
a draw table per tier — because the engine resolves kit keys against the
compendium and check-generator resolves them against content.mjs, and the two
cannot import each other. Classification comes from catalogue membership and
never from the key: climbing_kit is "Breaching charges" and prybar is "Entry
bar", so anything reading a key's spelling is wrong in that posting first.
The weapon↔skill pairing table is gone. Each weapon item already names the
skill that fires it, so the skill is granted from the weapon, and a generated
NPC cannot hold what it cannot use. THREATS.attacks is now creature-tiers
only; those two keep their natural attacks on top of what they drew.
Armour is an item. naturalArmour drops to 0 on the four human tiers, where
the number was standing in for the item, and stays on the two creature tiers,
where it stacks with drawn armour as locationArmourFor already intends.
check-generator (guard 25) was written first and observed failing on nine
counts against unchanged source. One of its assertions was itself wrong —
it read for the creature-tier restriction after the loop instead of before
it, and so reported the fixed code as broken; re-scoped, it passes on the fix
and still fails against git show HEAD:ringbrp.mjs.
Measured with the new tools/npc-cohort.mjs, 2000 runs, seed 11, against the
party check-lethality freezes. Apex · Containment 68.2% -> 88.5% wipe,
Anomalous · Containment 0.3% -> 19.2%, and Dangerous · Field Lead got weaker
because its posting carries one pistol where the tier used to hand it a
rifle. Full table and three incidental findings in R-310.
Two of those findings are guards, not content. check-rules failed on a
comment that quoted the pattern it hunts for, so comment-only lines are
skipped now. update-readme held the guard list as a hardcoded array whose own
comments recorded it going stale twice; it reads the check script instead,
and so does the count-word rewrite that was separately capped at sixteen.
Not changed, and flagged in R-310: breach_suit and riot_shield declare no
coverage, so they armour every location including the head. The location
counterplay NPC_KIT_PLAN.md relies on does not exist, and that is a balance
decision rather than a side effect of this one.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
collectSpecs() in tools/all-specs.mjs is the single place that decides
which specs exist. Nine modules were importing NPCS and PREGENS straight
from content.mjs instead, so each carried its own idea of the population
and measured a different subset of the game. check-lethality was the
clearest case: it scored 47 creatures and reported OK for all 184.
check-seam (guard 24, first in the suite) scans every module and fails if
anything but all-specs.mjs names NPCS or PREGENS in a content.mjs import.
The nine violators are re-pointed at the seam.
Re-recording check-focus's baseline against the full 184 raised it from
47 packs to 138 and surfaced one creature focus fire does not help: the
dun cow. Rather than re-record that away, the guard now requires the
advice section of BESTIARY.md to name every such exception, and
bestiary.mjs generates the sentence.
The first version of that check asked whether the name appeared anywhere
in BESTIARY.md, which every creature's own heading satisfies — deleting
the exception sentence still passed. It reads only the
"Shooting at something that moves" section now, and the mutation test
fails as it should.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bestiary.mjs built the document from NPCS, so it described 47 creatures of
147 while check-bestiary agreed with it — two things agreeing is not
verification when both read the same wrong source. It reads collectSpecs()
now: 184 creatures across 5 sections, every one with a measured lethality
figure, which only works because check-lethality was fixed first.
Three faults surfaced fixing it:
- a second NPCS reference in focusParagraph()
- which then broke on `rows`, because focusParagraph declares its own
local `rows` for focus-fire data and shadowed the creature list. Keyed
lookup now, so the shadowing cannot bite again.
- the document grouped on the raw role tag against a list of four, and
`if (!group.length) continue` DROPS an unlisted tag rather than
mis-filing it. Nine of the twelve tags were absent, so those creatures
would not have appeared at all. Twelve tags now map onto five sections,
with a new "Beasts and heraldry", and a completeness assertion counts
every creature into a section and fails if one is unplaced.
check-powers was the fifth consumer bypassing all-specs.mjs. It reconciled
its counts against BESTIARY while reading NPCS, so it called the document
wrong when the document was right.
Reading the real population then demanded 101 classifications. All 101 are
done and NOT ONE was wired. That is the right answer, not a shortfall:
the three available effects describe the creature — its own attack rating,
the damage it takes, whether it feels defence stacking — and essentially
every power is conditional on a place, a posture, a round count, a weapon
type, an attacker count, a named agent, or Coherence. R-275 records what
wiring one anyway costs: 25.1% to 75.2% on a single creature.
The near-misses are the evidence the reluctance was applied, not recited:
tangie's "HALF damage" is edged-only and ends in open flame; the_heron is
+30% or -20% depending on movement the harness does not have, so which
branch applies is undecidable; mirrorline's halving lands on an AGENT, not
on the creature, so wiring it would have protected the wrong combatant;
yale's defence waiver is capped at two attackers and its written counter is
a fourth agent, which defenceStacking:"ignores" cannot express.
Classifications live in four band files and are spread into POWERS last, so
a hand-written entry always wins a collision. 142 classified: 2 wired, 78
beyond the harness with a reason, 62 not fight rules.
All 23 guards pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
It imported NPCS directly, so once the bestiary moved into its own files it
measured 47 of 147 and printed OK. A guard blind to two thirds of what it
guards is not a guard, and this one failed silently — the worse kind.
Now reads collectSpecs(), the list check-creatures, make-portraits and
mj-queue already share. Scenario casts come in with the bestiary: they were
never measured, and they should have been, since the Act Three standoff
this repository publishes wipe rates for IS a scenario cast. 184 specs at
roughly 47ms each, about nine seconds.
Switched BEFORE re-recording, to prove the change moved nothing: the run
against the old baseline reported all 47 existing creatures fighting
exactly as recorded. The --update is then verifiably additive — 47 to 184,
137 added, 0 changed, 0 lost.
Still fail-open on arrival: an unbaselined creature is a note, not a
failure, so this printed "OK, 137 new" while 137 creatures were unguarded.
Left as the author wrote it rather than changed under a content drop, but
it is the same shape as the three classifier bugs in 00f6a1e and worth
closing.
First thing it found, invisible until now: march_stone is authored "it
kills perhaps one person a century" and measures 43.5% wipe, 2.72 of 4
down, over 22 rounds. naturalArmour 14 is the highest in the game — the
Apex tier is 7 — so the party cannot hurt it and it grinds them down. The
prose and the statblock describe different creatures.
All 23 guards pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three faults, all in how an actor reaches the table.
THE TOKEN WAS THE PORTRAIT. prototypeToken.texture pointed at the portrait
file, which is a 2:3 field-guide plate — full figure on plain ground.
Foundry draws a token square, so it was squeezing a tall plate into it and
showing a torso. tools/make-tokens.py now derives a 512px circular RGBA
token from the same illustration: not a second Midjourney pass, because
that would double the spend and still give a token that does not quite
match its own portrait. Sized by the subject's DIAGONAL, since these
creatures are tall and narrow and padding by the longest side wasted a
third of the circle. Padded, never cropped — cropping to a square clipped
the first gryphon's head off.
EVERY TOKEN WAS 1x1. A hearth hob, a carthorse and a SIZ 32 dun cow all
held one square. Footprint now comes from SIZ, cut at 21 and 30: 132 at
1x1, 14 at 2x2, 1 at 3x3.
THE 100 CREATURES WERE IN NO COMPENDIUM. build-packs reads NPCS directly
rather than collectSpecs(), so the bestiary validated, was drawn, had
prompts written, and did not exist in the game. The npcs pack held 47
actors; it holds 147 now.
That is the fourth consumer found bypassing all-specs.mjs, whose own header
calls one-definition-only "this repository's one standing law" —
bestiary.mjs and check-lethality.mjs still do. check-lethality is the one
that matters: it cannot see the new creatures, so it is measuring 47 of
147 while reporting OK.
All 23 guards pass. npm run build is red at update-readme for an unrelated
pre-existing reason: the README advertises a guard list that package.json
no longer matches.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three fail-open classifiers, each reading a field that is not where the
bestiary keeps the answer. Found by generating one creature before
spending the allowance on forty-eight; art/creatures/gryphon-u1.png is a
WINGLESS gryphon, from a spec whose bodyPlan is "winged".
1. anatomyWords() read `species`. Shape lives in `bodyPlan` — that is the
field selecting the hit-location table. 44 of the 100 new creatures are
species "baseline" with bodyPlan quadruped or winged, so every one fell
to the silent branch and asked for no shape at all.
2. isPersonSpec() ended `if (tag) return true` — an unrecognised role tag
means person. MONSTER_TAGS listed three tags; the bestiary uses twelve,
so 43 creatures were prompted as "portrait of X, waist-up portrait".
Now bodyPlan decides first, structurally, because a tag list is free
text that grows and bodyPlan is enforced by the engine.
3. ROLE_CLASS knew the same three tags, so HERALDRY fell through to
"carries nothing manufactured and armour >= 4 -> anomalous". Six
centuries of carved stone were classed as far-side machinery, and the
armour clause duly asked for a mech. ROLE_CLASS now carries all twelve,
and the heavy-armour wording follows era: machinery for future and
anomalous, "hide and scale thick as carved stone" for the rest.
Also in this commit: all 100 creatures re-pointed onto the natural attacks
added in 3feac39 — 41 of 100 changed, the rest keeping grasp or punch
because that is genuinely what they do. Three manoeuvres stay as prose and
say so explicitly: dun_cow's and bull_azure's charge, gryphon's stoop and
drop, tup's blind side. Portraits redrawn, since era decides their hue.
All 23 guards pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The catalogue had `punch` (1d3) and `grasp` (1d6+1 blunt) and nothing else
a creature owns. Every biter and gorer in the bestiary therefore carried a
grasping limb and stated its real damage in tactics prose, which
simulate.mjs cannot read. Two silent consequences: the measured damage was
the grasp's rather than the creature's, and because grasp is blunt, the
edged and piercing wound paths never fired for any animal in the game — a
boar's tusk, a wolf's bite and a gryphon's talon all resolved as blunt.
bite 1d6 piercing gore 1d8+1 piercing
claw 1d6 edged hoof 1d6+2 blunt
talon 1d6+1 piercing trample 1d10 blunt
beak 1d6+1 piercing constrict 1d6 blunt
All fam "brawl", like punch and grasp, so they need no new skill family and
arrive usable. Calibrated against the melee line already in the table:
dagger 1d4+2, baton 1d6+2, machete 1d8+1, prybar 1d10.
Reported independently by three of the four bestiary authors. All 23 guards
pass. Nothing uses these yet — the creatures are re-pointed next.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Folklore of the isles, water and the drowned, anomalous far-side, and
beasts and heraldry — 25 each, in four source files wired into
collectSpecs(). check-creatures passes at 204 specs across 13 sources and
the full 23-guard suite is green.
The population this was meant to fix:
non-human body plan 4 -> 48 (29 quadruped, 15 winged)
vesh / cadence 5/5 -> 13/13
creatures 47 -> 147
CREATURE_FORGE_PLAN.md called the unused location tables the reason to
build any of this; the quadruped and winged plans now carry a bestiary
rather than three dogs and a heraldic beast.
Art is procedural: 102 SVG portraits composed from each creature's own
body geometry, so a cadence portrait has five headless bodies because its
location table has five. The 17 hand-made portraits are untouched.
BESTIARY_ART.md carries 204 derived Midjourney prompts for the ones worth
illustrating properly later.
Known and unfixed, reported by three of the four authors independently:
WEAPONS has no bite, claw, gore, hoof or talon, so every creature that
kills with its mouth carries `grasp` and states its real damage in prose.
simulate.mjs measures the grasp. Next commit.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Anomalous and Apex now draw weapons, armour and gear from the posting on
top of the natural attacks they already carry. Their hide stays, and
locationArmourFor adds worn pieces to it, so Apex · Containment stands at
17 torso armour: 7 hide, 7 breaching suit, 3 riot shield raised. Mean
damage across the 61 weapons is 6.9 and the heaviest ordinary one means
9.0, so nothing but the Unmaker reliably breaks it.
Chosen deliberately with that number in hand. The spec records the
counterplay already in the rules — the shield only counts raised, and
exposedHideFor halves hide on a grounded creature outside the vital — and
obliges Phase 5 to simulate both tiers standing and grounded rather than
assert a lethality band.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
generateNPC reads R.core, R.support and R.label. It does not read R.kit,
which generateDialog prints as DRAWS FROM STORES and generateCharacter
issues. The card promises a marksman rifle and a breaching suit; the actor
gets a utility knife.
Design: the posting says what it carries, the tier says how much of it and
how good with it. Kit keys classify by which pack they resolve in rather
than by a second hand-written list. Attacks derive from the issued weapon's
own skillFamilyId/skillSpecialisationId, which retires the weapon-to-skill
pairing table. Armour becomes an equipped item and naturalArmour drops to 0
on the four human tiers, which moves the numbers and so gets measured.
check-generator.mjs is written first and observed failing.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A reload icon sits beside the ammo count in the readied-weapon strip and
the weapons table, for any weapon with a magazine. It tops the weapon up
from its reserve (rules.reloadFor, spot-checked), posts the new count and
the weapon's reload time to chat, and warns when the weapon is already
full or the reserve is empty.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The single Roll damage button becomes two, with person and paw icons. Each
rolls damage and then a hit location. A targeted token still uses its own
anatomy; with no target the blow is placed on the chosen body plan and
shown, with nothing applied. Both buttons disable after either is used.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Four new portraits (Joan Wetherlaw at last, Ruth Cotter, Nell Teague,
Mr Ogden) and eleven interior plates, one for each underground location
that had none, in the two-ink civil defence style. Bewley and Prosser
reuse their THROUGH TRAIN portraits. Journals now show 20 plates and 12
faces. The art sheet corrects the v1.0 diagnosis: Joan's prompt was
being refused, not the account out of hours.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
SO-H01 becomes the full Registry case brief: what the department knows
about Bellhouse, the 1974 return and the stamp, the orders, conduct,
access and the Stores issue. Nothing about the song, the children or
Centre's letters. STANDING_ORDER_HANDOUTS.html prints it on A4 with the
enclosed 1974 Seat return (SO-H02) and Mr Smith's mark.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The section now shows 13, 14, 15 and 18 on a third level with the
incline from the plant floor, instead of footnoting them as not drawn,
and the key runs 6-18 in number order in two columns. Sheet 6 moves the
incline to the plant's north end to match.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Five more blueprint sheets: the 1962 dormitories and laundry (240
berths), the canteen, kitchen, bakery and officers' cabins (20), and
three sheets of the Estate, 213 family dwellings on three coal roads
(737). With Edith and Kit Marlow that is the 999; the scenario now
shows the sum. Section map issue 3 adds 16-18, and sheet 6 is mirrored
so the pipe room lies south of the plant as the section draws it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Eight sheets laid out to match the section: north to the left, Level 1
lobby to sick bay, Level 2 creche to plant, an incline to the pit
galleries, and every corridor end naming the sheet it reaches. Rooms
now share walls (the corridor gap had doors opening onto rock); adds an
armoury, a pipe room beside the plant, and a Vigil hall sized for 999
standing. bellhouse-plans.mjs --check holds doors, swings, furniture,
lettering and reachability, and runs in npm run check.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Drawn by tools/bellhouse-plans.mjs from declared rooms: lobby, control
room, registry, sick bay, creche, vigil hall and plant, coal roads and
the Sump. 2800x2000 at 5 ft to the square, added to the Adventure and
keyed in the Locations table.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Cut the register mechanic, the census creature, the paperwork route and
half the clues. The under-twelves know Mr Smith's song from the nightly
creche speaker, so Act Three is a choice: burn the tape and take the
children into care, keep the families below, or cure them with a cut
tape first.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Tim's ruling. He comes from Outside and speaks for the powers that sleep
there, which the department has no heading for; the census in the Registry
is a Vesh working for him. The open question is marked decided.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The agents now cross into Bellhouse on a diplomatic brief to bring its people
home. A thousand people (118 of the 1974 intake, 881 born below) run the Seat
like a 1970s council, kept down by ninety-day renewals from "Centre", which
is Mr Smith, planted in THROUGH TRAIN. His experiment is procedural and
quiet: a bulletin response, a crèche lullaby, a shared dream, the children's
drawings, a steered establishment. Act One is the briefing, the moor and the
crossing into Enquiries. Act Two is the site, and the detention the Controller
orders on Centre's circular, measured and cited. Act Three is Annex D: at a
thousand the Seat broadcasts an Address that enrols whoever hears it, and the
table must silence it before or while they release the Seat under clause 4.
Same site, people and plates. Two cast actors (the wardens, Teague). New
handouts SO-H05 (Centre's circular) and SO-H06 (terms of engagement). The
section map's key is relabelled (issue 2). Status is honest: v0.7's five desk
passes tested a different plot, and this needs its own.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The man who told Vane what the chart had to say now has a name: a Mr Smith,
with the company's paper, whom the company never employed. Vane names him if
asked and cannot picture his face. A "do not resolve" line says who he is not
to be explained here: he is the thread into STANDING ORDER.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A second scenario gets pack-tables' arrangement: four configs (Teague plus
one, three or five wardens) against the declared six and the four-player
cut, 2000 runs at seed 11, cap 400, recorded to detention-baseline.json,
citeable as "detention", and --check added to npm run check.
standingorder joins all-specs' SCENARIOS, and simulate.mjs now reads that
list instead of keeping its own copy, so a new cast is fightable the day it
is registered. The lethality, focus and pack baselines are unchanged.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
New pack ringbrp.standingorder, in the Scenarios folder. It holds the GM
journal (13 pages, one per section), the three player handouts, nine plates
to show, six faces and the Bellhouse section map as a scene. No cast actors,
because nobody in the case has a stat block.
The GM pages are read from docs/scenarios/STANDING_ORDER.md at build time
rather than transcribed, so the compendium cannot drift from the document the
desk passes ran against. STATUS and Open questions are left out as authoring
notes; STATUS's "not obvious" list leads page 1.
Doc fixes found on the way: the Act Two heading still said ~55 min against a
75-minute budget; STATUS said four passes and "no desk playtest run" after
five; the runtime open question still called 45/55/50 unbacked.
figures-baseline: generator enrolled at 0; STANDING_ORDER.md leaves the
uncited list because it cites.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
cdbb2e3 added "When two people want opposite things" to the rules text but did
not rebuild packs/rules, so the compendium has been a section behind the
source since. Content-checked against HEAD: this is the only page that differs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A narrow verification pass rather than a session: does Act Two land where v0.6
budgets it now that a failed filed-clue roll costs a scene instead of ten
minutes? Seed 4471.
THE RETRY FIX WORKS AND DOES NOT DO WHAT v0.6 ASSUMED. Forced both filed clues
to fail — about one table in seven, since each is a 37% miss at these ratings.
Under the old rule that was twenty minutes and a party standing in Registry
waiting; under the new one Pennyfeather fetches each while they do something
else and it costs nothing, while the roll still means something. So the fix
removes up to twenty minutes of VARIANCE. It does not shorten the typical case,
and Act Two uncut is 75 minutes whether or not anybody fails a filed roll.
AND v0.6 CONTAINED AN ARITHMETIC CONTRADICTION I PUT THERE. The Runtime row
budgeted Act Two at 65 — pass 4's figure, measured with nineteen minutes of cuts
taken — while the Pacing Note two screens later said the correct number of cuts
to plan for is zero. Both cannot be true; it was a ten-minute overrun written in
on purpose. The three prior passes reconcile exactly (75 uncut, and pass 4's 66
is 75 − 19 + 10), so the number was never in doubt, only which configuration it
belonged to. I measured under one configuration, changed the configuration, and
kept the number.
Act Two is now budgeted at its uncut base of 75. Acts of 45 / 75 / 50 is 2h50 of
play, 3h00 wall with the break, in a 3h15 slot — fifteen minutes of real slack
rather than twenty-five claimed ones. The cuts stay optional, which keeps Kit
Marlow's scene, which pass 4 showed is the price of the likeliest ending.
The timing section now records that 75 is the uncut base three passes agree on,
and that the retry fix moved the worst case and not the typical one, so nobody
re-derives the same error the next time the slot moves.
All twenty-one guards pass. Five passes; what is left is human beings.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Decided rather than worked around. Four passes measured Act Two's floor at about
66 minutes against a budget that said 55; the alternative was twelve minutes out
of the sick bay, which is where Revelation 3's best route lives. The slot moved,
because 3h00 was an assumption and the sick bay is not.
2h50 of play in three acts of 45 / 65 / 50 plus the break, in a 3h15 slot. Act
Two is budgeted at the 66 pass 4 actually measured with every cut taken, not at
the 56 the retry fix predicts, because nothing has measured the fix. The
twenty-five minutes of slack are deliberate: the house standard says a scenario
landing to the minute with zero slack is a fail for a table of strangers, and
every figure came off a desk pass run by a GM who already knew the document.
THE CUTS ARE NO LONGER DEFAULTS, which is the real answer to pass 4's finding
rather than a workaround for it. They existed because Act Two had to lose twenty
minutes it did not have. At 3h15 the correct number to plan for is zero — and
that retires the trap where the cheapest default cut hollowed out the price of
the likeliest ending.
AND THE REBUDGET EXPOSED AN OLDER DEFECT. The Countdown put step 3 at +1h20 and
step 4 at +2h00, measured from the blast door — so under every budget this
scenario has ever had, both fired AFTER Act Two ended. Both are backstops for
Essential revelations: step 3 is the second road to the sum and step 4 is
Revelation 3's last resort. They were arriving too late to back anything up. The
whole table is re-timed inside the act at +15 / +35 / +45 / +60, the reference
point is stated, and Act One's Stealth roll moves step 2 within that window
instead of pushing Teague past the end of the act.
The act checkpoints were trailing their own acts too — the signing one left five
minutes for the decision. A checkpoint is a point you can still correct from, so
the sum is wanted at 1:40 with twenty minutes of Act Two left, and Act Three's
is ten minutes in. Running times are printed so they mean something.
All twenty-one guards pass. What is left is human beings.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The pass three passes had not run: an honest session at six players, no
contrarian choices and no forced branches, with the Pacing Note's cuts taken
exactly as written. Seed 6620. Nineteen minutes cut — pipe room folded, Kit
Marlow to the corridor, census dropped.
THE CUTS DID NOT CLOSE THE GAP, AND ONE RETRY UNDID MOST OF THEM. Act Two asks
for six rolls whose failure case was "ten minutes and a second attempt", roughly
two fail in an average session, and a single failed Research handed back ten of
the nineteen minutes that had just been cut. The Pacing Note's arithmetic was
sized against the act's length and never against its variance, so it could not
hold. A failed roll on a filed clue now costs a SCENE instead — Pennyfeather
fetches it while the party do something else — which keeps the roll meaningful
and costs nothing on the clock.
THE CHEAPEST CUT GUTS THE LIKELIEST ENDING. The Pacing Note priced moving Kit
Marlow to a corridor at "the drawings". This pass took that cut and then reached
the narrow row of ending 3 — the likeliest one, since it needs a single dossier
item — whose entire price is that the sixty-one stay unrecorded. Kit is the
sixty-one made into a person and her own entry says she must be a person before
she is a price. The cut is re-costed honestly, and the corridor version now has
to do her one job: she shows them a drawing and asks whether she got the blue
right.
The blanket Act One failure case named Joan for all seven clues, and Joan does
not go down the adit. Clues 6 and 7 now have their own: time, never access,
because the door has never been locked. Joan herself is at the farm AND walks up
with them, so the moor walk has somebody in it. And 13b came off the dice after
a 98 lost the reason the proper channel failed — the thematic centre of the case
— which is now written at the bottom of Pennyfeather's own sheet.
Act Two's floor is about 66 minutes against a budget of 55, measured across
three passes at 75 uncut, 70 uncut and 66 fully cut. The retry fix should
recover most of that and nothing has measured it. THE REMAINING QUESTION IS A
BUDGET DECISION AND IT IS TIM'S: move the slot to 3h15, or take twelve minutes
out of the sick bay and lose Revelation 3's best route. Written up in Open
questions and deliberately not decided here.
All twenty-one guards pass. Four passes, every content defect they found fixed.
What is left is human beings.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The cadence's third pass: a full session choosing contrarily at every fork,
forced to the one ending nothing had reached. Seed 3307. The party skipped the
scenario's best NPC, told the antagonist the truth before anyone else, refused
the hospitality, split so the wrong specialist was in every room, took a
resident to the surface, and cancelled.
BOTH OF PASS 1'S HEADLINE FIXES WORK, AND ONE WORKS BETTER THAN WRITTEN. The pen
held above the paper converted the ending from pass 2's ninety-second reflex
into a real argument about whether a narrow amendment they could no longer reach
beat a cancellation they could. And Pennyfeather's spoken cost landed on a party
who had failed the birth register, so the sixty-one arrived as new information at
the moment of decision — which is better than knowing in advance, and clue 14 is
demoted to Supporting on the strength of it.
THE SUM HAD ONE ROUTE AND NO FALLBACK. Pass 1 found the Revelation 3 fallback
circular and it was repaired with three roads; nobody then asked whether the
other essential revelations had the same shape. The contrarian split put Insight
40 in Registry instead of 63, one roll failed, and the party cancelled the
Standing Order having never learned why it was urgent. Worse, the clue asked for
a roll that Pennyfeather's own roster line contradicted — she hands the sheet to
anybody who asks her a straight question. The roster line wins: the sum is no
longer behind a roll at all, the Insight now buys what she did about it, and the
establishment return she posts at Countdown step 3 is a second road for a table
that never thinks to ask her anything. Fixing an instance is not fixing a class.
TWO OF THREE HOOKS ROUTED THE PARTY AROUND THE ACT'S ENGINE. Only one hook
involves the farm, and a professional team with a grid reference drives past it
— so Act One ran fifteen minutes short with nobody in it, and both its Essential
clues lost their stated failure case, which is Joan pointing at them. She is now
at the vent head, where the woman in her own entry would be anyway, and no route
into the act can miss her.
Also: the pen pause was staged only for a Teague who stood down and now prints
the hostile version; a photograph brought back down is answered; refusing the tea
is answered; and an uninformed cancellation is written as the ending it deserves
to be, since a party who do the right thing by accident is the best possible
close for a case about people doing the wrong thing correctly.
All twenty-one guards pass.
Three passes and none of them a normal table: GM chair with bad dice, a branch
stress, and a deliberately contrarian run. Pass 3 landed on the 150-minute budget
only because one act collapsed and the other spent the difference. No pass has
run Act Two with its cuts taken. That, and human beings, is what is left.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The house cadence's second pass is a stress re-run of the weakest act. Pass 1
resolved Act Three in eight minutes of fifty and left three of its four branches
untested, so this forces each in turn on seed 8143 — and runs the three creature
encounters through tools/playthrough.mjs, the same runFight the lethality and
focus baselines come from, against this scenario's own declared six rather than
the frozen four.
THE THREE DOSSIER SCENES CHANGED NOTHING. The party assembled one item of three
and rolled 62 against 63 — exactly the roll they would have made with all three,
because Borrowed Authority says items improve the credential and never the roll.
Correct as a rule, catastrophic as staging: the act's best three scenes had no
effect any player could see, and pass 1 could not find it because there the
amendment failed and the question never arose. The items now buy scope instead.
Same roll, three different worlds: a narrow amendment that stops the ash and
leaves the site sealed, a lifted seal, or records above ground for the sixty-one
so Kit Marlow can leave.
ALL THREE CREATURES ARE INVISIBLE TO THE DICE. STERILISATION ORDER, THE
CORRECTION and ENUMERATED are all classified outOfCombat in powers.mjs, so every
measured number is a measurement of the creature's arms and legs and of nothing
that makes it frightening. That is correct bookkeeping, not a defect in the
guard, and it means the GM's text carries the whole threat at the climax. It
did not. The overwriter now comes with four printed corrections specific to this
case, and with the fact that force does not work: measured, one of them cannot
meaningfully hurt anybody and five grind for forty rounds finishing nothing, so
the end of the world was landing as an inconclusive scuffle.
EXPOSURE wiped all six in fifteen rounds with five dead, without the
sterilisation blast firing at all. The warning was right and understated. It now
prints the six-round countdown that lived only in the bestiary entry, the
argue-down as a named Borrowed Authority stretch, and what a failure costs —
five rounds reaches the adit and does not reach the crèche.
The best ending was three sentences, less than the failure branch beneath it,
and now plays out properly: the tannoy, nobody cheering, Pennyfeather filing it,
and Joan sweeping a yard that stays swept.
The four-player cut was one sentence from disaster. Science (Biology) and
Medicine are the only skills that vanish with Okonkwo and Nkemdirim, the cut
note happened to reassign exactly those two clues, and check-rollable never saw
any of it because the cast declaration names six and the cut is prose. Both
clues are now written on Knowledge and Insight for every table size, so nothing
load-bearing depends on an unguarded sentence.
All twenty-one guards pass, and the document has entered check-figures' strict
regime now that it carries citations.
Still untested: ending 1, and with it Pennyfeather speaking the cost and the pen
held above the paper — pass 1's two headline fixes. Pass 3 is the player chair,
contrarian, and should cancel.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Eight plates and six of seven portraits are on disk. Joan Wetherlaw's portrait
stalled three times — twice on the bridge's full 1800s window and once on
deliberately reworded prompt text, which rules out both the prompt and
deduplication. The thirteen before it returned in about forty-five seconds and
everything after ~21:20 hung, which looks like fast GPU hours running out
mid-batch.
The sheet listed every stem as though it existed and named the plates by their
pre-conversion stems rather than the webp files actually committed. Both fixed,
with the retry instructions and the note that mj-gen exits 0 on a timeout, so
the file is the thing to check and not the exit code.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
