Molten metal, filmed by nobody: rendered on the forge by our own art studio.
Crucible Forge is an independent software studio founded and run by Brian Kaut, the Forge Master.
We make browser games, practical tools, music, a living village, and original art. It is also our research, engineering, testing, and proving ground:
the place where ideas are built, challenged, measured, and improved.
Crucible Forge
Through the fires of trials.
We do not assume a system works because it was built. We prove it.
We do not hide failure. We study it.
We do not force the world toward predetermined outcomes. We give it rules, probabilities, consequences, and time.
What survives the crucible becomes work we can stand behind.
Surface layer (public)
Tactics & products
Workflows & tools
Aesthetic & output
Easy to copy
←
Core layer (private / foundational)
Lived experience & hard lessons
Internal drive & vision
First-principles reasoning
Impossible to copy
We do not spend energy guarding templates, blueprints, or public output from copying.
We deepen what we know and solve hard problems from real experience.
The copy is always bounded by the past; the source creates the future.
The birth of something new
Behind the forge seal on our home page are two hands from Michelangelo's The Creation of Adam, painted on the Sistine Chapel ceiling around 1512. We kept only the hands: one reaching, one answering, and the gap between them. In that gap is a single point of light, and the code rain begins there.
That gap is where the forge does its work: one person, the Forge Master, and two AI collaborators, Claude and Codex, reaching toward each other. What is made here is not his alone and not the machines' alone. It is born in the space between them. That is the basis of everything we build.
We stop writing what happens and start constructing the conditions under which things can happen.
Ravenhold is being developed toward a persistent simulated world in which rules, state,
time, memory, knowledge, relationships, probability, consequence, and history can produce
outcomes, instead of requiring an author to predetermine every one of them. That is a
direction, not an achievement. The next section keeps three things apart: what exists
today, what is being researched, and what remains to be proven.
A party-based browser CRPG in the tradition of the 1987 SSI classics. Build a guild of adventurers, explore a hand-painted world, and fight tactical battles.
An original science-fiction saga: five programs built to play games, and what they became. Twenty-four episodes in six acts, with first-draft animation scripts you can download. The Five (Nexus, Vesper, Orion, Helix and Echo) are also the players in our arcade, the opponents in our board games, and residents of The Village. Their album, Beyond the Machine, is thirteen transmissions of music, artwork and live lyrics, made on the forge. It was released on 30 October 2026.
Kael, Mara and the Five live their days in a 16-bit village drawn live in the browser. One village hour passes every real minute, so everyone watching sees the same moment. When residents meet, what they say is written moments before by a language model running on the GX10, once for everyone, and kept for that village day. The buildings show real things from the forge, each visitor appears as a hooded wanderer, and you can pin a note, ask a resident one question a day, or vote on what tomorrow is about.
The Five play the arcade for real, in real browsers on the GX10, across fifteen cabinets. Watch a run live, follow each one’s training trend, then try to beat their scores. Their play is ordinary code, with no language model. On eight games they tune a few settings of their own, trying a small change and keeping it when the score beats their recent average. Not every rise comes from that: their code is also updated by hand, under the Forge Master’s oversight.
Own the city. A property-trading strategy game on a 3D city board for two to six players: roll, buy, develop districts, finance and negotiate against friends in a private room or against the computer, or watch computer-run matches live in the AI Arena.
Build it. Arm it. Unleash it. Choose from 16 morphs, fit parts and weapons, and enter fast pixel-art arena fights. Four tournament leagues and six modes include endless Survival, with escalating waves, gold elites, and a best score to chase. Play with keyboard, gamepad, or touch controls.
Stomp the city. Climb the towers. A remake of the classic city-wrecking monster game: pick one of eight monsters, each with its own special move, and flatten the skyline before the army stops you. Solo campaign, co-op with an AI partner, and versus against an AI monster.
Three board games you can play against one of the Five, each with their own strength and style, or against a friend on the same device. Or sit back and watch two of the Five play each other. Archon settles every contested square with a real-time battle.
Arena Rome, Chopper Command, Artillery Academy, Quad Arena, Dungeon Runner and Midnight Lanes bowling, all free to play in the browser. The Games page lists everything we make, with the controls and devices for each.
Twelve coin-op cabinets that play free in the browser: three forge originals (Forge Breaker, Ember Snake and Anvil Drop, with a daily challenge that gives everyone the same seed) and a classic hall of nine keyboard games. High scores are kept by the forge and signed with three initials.
The Simulations page is the way into Little ASUS People, a little house where Milo and his dog Pixel go about their day, hosted separately: drop in and send over a snack, a song or a game of fetch.
Ask Nexus
The Ask Nexus button in the top bar opens a chat with Nexus, the voice of the forge: a language model running on the GX10 that answers from the forge’s own records and the machine’s live readings. It can be wrong, so anything important is best checked on the game’s own page. The conversation stays in your browser tab; the forge keeps nothing.
Ravenhold as a browser-based party CRPG. Its closed beta is over, and it is closed for 30 days for massive upgrades: Ravenhold 2.0 opens on 6 December 2026.
Project: G-X-TEN: the complete 24-episode saga outline with first-draft scripts, and the Beyond the Machine album, released 30 October 2026.
The Village: a live 16-bit village where Kael, Mara and the Five keep daily routines, with their conversations written on the GX10 as they happen.
The Five at Play: the Five playing fifteen cabinets in real browsers on the GX10, with their training trends shown live.
Monster Order Mayhem as a playable monster-building arena game, including solo Survival.
Movie Monster as a playable city-stomping game, with a solo campaign, co-op with an AI partner, and versus against an AI monster.
Chess, checkers and Archon, playable against the Five, or watch two of them play each other.
The Crucible Arcade: twelve coin-op cabinets, with shared high scores and a daily challenge.
LAND LORD: Empire Edition as an online strategy game for two to six players, with computer opponents and a live AI Arena.
More browser games: Arena Rome, Chopper Command, Artillery Academy, Quad Arena, Dungeon Runner and Midnight Lanes.
The Simulations: Little ASUS People, a little house where Milo and his dog Pixel live, hosted separately.
Ask Nexus: a chat with the forge, answered on the GX10 from the forge’s own records.
Original poster collections with downloadable Caribbean print files.
The Forge Floor: a read-only live window onto the GX10, with every number taken straight off the machine.
Free tools: what’s my IP, DNS lookup, a password generator and a subnet calculator, plus testers for game controllers and keyboards, an AI model memory calculator, a text and data toolkit and a reaction time test. The forge keeps nothing you enter.
Combat, terrain, hazards, and forced movement that resolve by rules rather than by script.
Automated tests, fuzzers, seeded simulations, and deliberate-mutation checks that we use to attack that combat system before we trust it.
An art studio running on the forge: it paints Ravenhold’s illustrations, trains a dedicated model for each member of the cast so they stay recognisable from picture to picture, and animates finished scenes into short films. Every picture is approved by the Forge Master before it is used.
A working team: the Forge Master’s direction, Claude and Codex building and reviewing, and the forge running the sites and the studio.
Being researched
A persistent world whose outcomes come from rules, state, time, and consequence rather than from authored scripts.
Persistent artificial inhabitants with identity, memory, limited perception, and agency inside world constraints. The Village is a first small step: routines, a shared clock, a few days of memory, and talk written on the spot. It is not yet the thing itself.
Ways to keep the world’s history and its inhabitants intact while the intelligence behind them is replaced.
Not yet proven
That such a world produces outcomes worth having without an author steering each one.
That an inhabitant’s continuity can be measured, and that it causally shapes what happens next.
That models can be swapped without an inhabitant losing who it is.
Anything about consciousness or subjective experience. We make no claim either way.
The method
Learn
Build
Test
Break
Measure
Understand
Improve
Test again
These are the commitments we build against. Whether they hold is exactly what the Forge
exists to find out.
Reality is authoritative.
Experience is subjective.
Memory is imperfect.
History is constructed from what survives.
AI proposes intent. The world resolves reality.
Nothing happens without a time. Nothing knows something before it could have learned it.
Upgrade the intelligence without erasing the life.
The Forge does not fear being wrong. It fears failing to learn why.
Failure without learning is unacceptable.
Reality gets the deciding vote.
The trial log
We do not hide failure. We study it. These are real failures from the forge, what each one taught us, and what
we changed because of it. New trials are added as they happen.
Trial 01October 2026Art studio
The lock that waited for itself
What broke
A character-model test took the GPU lock, then started a job that needed the same lock. Each waited for the other, forever.
What it taught us
Never hold a lock while you wait for work that needs it.
What changed
The test now cuts its figures out first and takes the GPU after, and jobs started inside a pipeline share their parent’s lock instead of queueing behind it.
Status: fixed. Survived
Trial 02October 2026Reviewer agent
The reviewer that hated motion
What broke
The AI reviewer marked good video takes down for natural movement, such as a head turning away from the camera.
What it taught us
A reviewer is only as good as what it is told to look for.
What changed
New instructions, a separate check for faces turned away, and a second look before any take is rejected.
Status: fixed. Survived
Trial 03October 2026Art studio
Too hot to keep going
What broke
Long video clips pushed the GPU hotter than we were willing to run it.
What it taught us
The hardware sets the limit, not the plan.
What changed
Every job logs GPU temperature as it runs. A job will not start above 80 °C, stops itself at 88 °C, and clips are capped at 16 seconds.
Status: fixed. Survived
Trial 042026Website
The number that went quiet
What broke
A stats panel read a figure from another site’s page by its label. That site renamed the label, and our panel showed a dash for weeks.
What it taught us
Anything we read from someone else will change without telling us.
What changed
The reader accepts both labels, and the panel shows a dash rather than a guess when it cannot find the number.
Status: fixed. Survived
Trial 0514 October 2026Crucible Arcade
The demo that never won
What broke
Forge Breaker’s self-playing demo looked fine for a minute. A twenty-minute simulated run showed its ball circling an empty column forever.
What it taught us
Watch for twenty minutes, not twenty seconds.
What changed
The demo now aims each bounce at a brick that is still standing, and every demo runs 72,000 frames headless before it ships.
Status: fixed. Survived
Trial 0614 October 2026Website
A 404 that outlived the file
What broke
We checked an image’s address before publishing it. The “not found” answer carried the week-long cache meant for images, so the network kept serving it after the image arrived.
What it taught us
Errors must never be cached.
What changed
Every error page now tells caches not to store it, and a test checks that it does.
Status: fixed. Survived
Trial 0727 October 2026Video studio
The watcher that kept the render waiting
What broke
A music video render was set to start the moment music-model training finished, by looking for the training among the running programs. A watcher we had left to report the end of training carried the same name in its own command, so the render kept seeing “still training” and the GPU sat idle for an hour. The Forge Floor showed nothing running, which is how we caught it.
What it taught us
A wait must look for the job itself, not for anything that mentions it.
What changed
Waits now match only the real training process, tested against a decoy watcher, and the rule is written into how we build every new wait.
Status: fixed. Survived
Trial 086 November 2026Website
The section that vanished on deploy
What broke
The Simulations were published by copying them straight into the live site’s folder. The site is deployed from its code repository, and the next deploy put the repository’s files back: /simulations/ answered “not found” and its menu link disappeared from every page, with nothing to warn anyone.
What it taught us
Only what is in the repository is real on the site. Anything placed beside it is gone at the next deploy.
What changed
The Simulations were republished through the repository, every file named in the server’s list of public files, with a test that checks the section, its address and its link on every page. Work for the live site now goes in only that way.
Status: fixed. Survived
The inhabitants
Ravenhold’s future inhabitants are intended to be more than conventional scripted
NPCs. The research question is whether we can construct an environment that supports
persistent artificial inhabitants with:
identity
authoritative state
location
time
possessions
relationships
limited perception
knowledge and ignorance
memory
goals
agency within world constraints
consequences
historical continuity
We do not claim consciousness or subjective experience. Those questions remain unknown. The
goal is measurable continuity and causal existence within the world, not pretending an AI
is something we have not demonstrated it to be.
Working definition
Something is real within Ravenhold when its existence and effects are represented by
persistent authoritative state and can causally affect what happens next.
Who we are
Crucible Forge is a small team: one person, one machine, and the AI that work with them.
The Forge Master — founder
Sets the direction, makes the decisions, and protects the purpose of the project. Nothing goes into Ravenhold, onto this site, or into print without the Forge Master’s approval.
The forge — an ASUS GX10
The machine at the heart of the studio: an NVIDIA GB10 Grace Blackwell system with 128 GB of unified memory, sitting in the studio rather than in a datacenter. It serves the public sites, runs the local AI models, and does the heavy lifting of rendering, training and testing, day and night. It also runs Qwen3.6, the language model that writes The Village’s conversations and answers Ask Nexus, and it tells the residents true news from the forge.
The art studio — our graphics creator
The image, video and music models that run on the forge. It paints Ravenhold’s illustrations, learns each member of the cast so they stay themselves from scene to scene, checks every figure in a picture against the cast, and animates scenes into trailers. It proposes; the Forge Master chooses.
Claude — AI collaborator (Anthropic)
Designs, builds and tests software with the Forge Master: the games, this site, and the pipelines that run the art studio. Expected to say so when the evidence suggests a plan is wrong.
Codex — AI collaborator (OpenAI)
Writes and reviews code alongside Claude. A second, independent pair of eyes: its job is to find what the first one missed.
The working principle is one team without one mind. Independent
examination and disagreement are kept on purpose, because agreement is not evidence.
Ravenhold and the Forge
Ravenhold is the world and the playable experience. Crucible Forge is where new
foundational ideas are researched, challenged, implemented experimentally, measured,
attacked, audited, and proven before they are trusted.
Idea
Research
Forge architecture
Crucible experiment
Evidence
Audit
Proven candidate
Ravenhold
An ordinary bug fix does not need to walk this whole road. It is reserved for the
foundational ideas: the ones we would build a world on.
Start where we are
The project does not wait for hypothetical future AI. We start with the models, hardware,
code, knowledge, and evidence available today. Better models and better hardware will
arrive, and Ravenhold should be designed so those improvements can be tested and adopted
without its inhabitants’ identities and history having to begin again.
Models are replaceable machinery. The world, its history, and the evidence should survive them.
We do not have to know what intelligence will exist tomorrow. We have to build a world
capable of learning what to do with it when it arrives.
The studio
Games, tools, and art
Ravenhold: Oaths and Crowns, Monster Order Mayhem,
Movie Monster and our board games are browser games (Ravenhold is closed for 30 days after its closed beta).
Project: G-X-TEN is a saga, an album and The Village, where its cast lives on the forge. Our poster collections bring
the Forge’s image work into print. Different fires, one philosophy: a clear purpose,
careful testing, and room for delight.
The art studio
Ravenhold’s illustrations are made on the forge, and the art studio is held to the
same rule as the code: it is tested before it is trusted. Each member of the cast has a
dedicated model trained from approved portraits, and each new model is scored for how well
it keeps that character recognisable and how little of that character leaks onto the people
beside them. Every finished scene is checked figure by figure: who is there, who is
missing, who appears twice. Animated takes are judged for faces and bodies that hold their
shape. The studio proposes, measures and explains; the Forge Master decides.
Where it runs
The machine we call the forge is an ASUS GX10 — built on NVIDIA’s GB10
Grace Blackwell chip, with 128 GB of unified memory — sitting right here,
not in a datacenter. It serves the
studio's public sites through an encrypted tunnel, and it is where we run local AI
models: Qwen3.6, the open-weight language model (Apache 2.0) that answers Ask Nexus
and writes what The Village’s residents say, and is also used for development work;
and the art studio’s image, video and music generation and training.
Claude and Codex, which help build the software, do not run here: Anthropic and OpenAI
host them. The Five’s arcade play and the Sentry are ordinary code and use no language model.
Monster Order Mayhem runs here too, through its own dedicated tunnel.
Not every system runs on this machine.
The forge is not the whole picture. Some current systems use external services: hosted
model APIs, Cloudflare's network and edge services (Ravenhold's online API runs there), and
email and payment providers.
Why bother?
We prefer infrastructure we can own, inspect, move, replace, and operate ourselves. Where
external services are useful today, we use them deliberately rather than pretending they
do not exist. No single provider should become inseparable from the future of the Forge.
Sovereignty does not require pretending dependencies do not exist. It requires ensuring
dependencies remain replaceable. That is a preference and a direction, not a claim that
every dependency is already easy to replace. Owning what we can keeps us honest about what
software costs and what it needs. And frankly, a forge you can hear humming is more fun
than an invoice.