The Crucible · by IntelliBotique

In goes the idea. Out comes the product you own.

Old crucibles told you if the gold was real. This one does it for what you built: it asks five plain questions first, then proves the result against six gates before it reaches you. Then it is yours, to own outright or let the forge keep running.

Built on a Pickaxe? Smelter is the Crucible, shaped for Pickaxe makers

The Wolf, IntelliBotique's signet The Wolf · on it
IntelliBotique · Nevada City · est. 2023 Send the wolf. Get it handled.
Before a line of code

Five questions, asked first.

Most software gets built before anyone checks whether it should exist. The Crucible works the other way round. It interrogates the idea in plain language and tells you what it found, including the parts you would rather it did not. A bad answer here costs you an afternoon. The same answer after launch costs you a year.

i

Real problem?

Is somebody actually stuck on this, or does it merely sound useful when you say it out loud? The forge goes looking for evidence instead of taking your word for it.

ii

Pays for itself?

What it costs to run, what somebody would plausibly pay, and whether those two numbers survive being put next to each other.

iii

Legally clear?

The claims it would make, the data it would touch, the promises it quietly implies. Named in your language, early, while changing them is still cheap. Not legal advice.

iv

Buildable?

Can this be built as described, at this scope, with what exists today. Scope that cannot be built gets said out loud before it gets estimated.

v

Release-safe?

Whether it could go in front of real people without costing you your reputation. The last question asked before anything gets signed.

the signed plan
problem  what it solves
for  who it solves it for
scope  what it will do
non-goals  what it will not
risks  what you chose to carry
you sign itchange a field, sign again

Nothing gets built until you sign that plan. It is the whole agreement in one page: what this is, who it is for, what it will not try to do, and which risks you decided to accept anyway. Change a signed field later and it comes back for your signature.

For 3,000 years, the crucible was where you found out if the gold was real. Now it's where you find out if the product is.

Bring what you built. The crucible tells the truth, then hands you the deed.

Most people with an idea never find out if it's any good. Trying costs too much, and everyone who could tell you the truth has something to sell you. I carried mine for years. So I built a fire. The first thing it tested was itself, and it tests everything the same way: harder than fair, then honest about what it finds. It doesn't care who you are, whether you can code, or who you know. If your idea holds, you own what comes out. You've been carrying one around a while. This is where you find out. Josh Wolf · IntelliBotique

The part nobody shows you

Six gates, on your side.

Anyone can show you a demo that looks finished. A Crucible build proves itself first: six gates stand between the fire and your hands, each one there to protect what you are about to own. A red gate pauses delivery and tells you plainly what it found. What happens next is your call, not ours.

Build integrity

It compiles. An unresolved import is a product that will not start on the machine you put it on.

Build checks

Duplicate modules, unsafe cookies, missing security headers, dead code. The dull failures that reach production most often.

Accessibility

WCAG 2.2 AA. Shipping a product that some of your users cannot operate is a decision, so it is treated as one.

Build and run

It gets built and started for real, not inspected and assumed. A product that only compiles is not a product.

Design craft

Whether it looks like something a person made on purpose, rather than the default output of a machine.

Delivery assay

The finished build, measured against the plan you signed. Every check reported as measured, and anything it could not measure disclosed rather than counted as a pass.

And you stay in charge: any gate can be signed past, knowingly. Decide the risk is worth carrying, put your name to it, and the build is yours; the decision rides in the papers that travel with it, so it is never lost and never fudged. The gates inform your call. They never take it from you.

How it works

Shape it, forge it, prove it.

i

Shape it

Describe what you want to exist. The five checks run against it and come back with plain verdicts and the questions they could not answer on their own. You answer those, or you decide to carry them as known risk. It is a conversation, and it is short.

ii

Sign the plan

What survives becomes a signed plan: the problem, the scope, the non-goals, the risks you accepted. You sign it. That is the thing the build is measured against later, which is why it exists at all.

iii

Forge it

The forge builds it in front of you, step by step, on the screen. It burns its own hosted key, not yours. Nothing you type here is an API credential.

iv

Prove it, then keep it

Six gates run, and the assay measures the finished build against your signed plan. If it passes, you choose your door: take the whole thing and own it, or let the forge keep running it. If a gate goes red, the screen tells you which and why, in words, and the next move is yours: fix and refire, or sign and take it.

What you end up holding

The source, the papers, the keys.

Whichever door you take, the thing at the end is real software. Not an embed, not a share link, not a folder that needs a rebuild before it will start.

The source

Every file, in the open. Change a line, add a feature, or hand it to a developer who will. It is the real product, not a screenshot of one.

The papers

A README that explains what got built and why, a DEPLOY file a person can follow, and the assay certificate saying what was measured and what was not.

The keys

It runs where you say: your laptop, a rented server, the cloud account with your name on the invoice. Once it is yours it answers to you, not to us.

After the firing

Two ways to keep it.

Take it home, or leave it in the fire. Equal doors, honestly priced, and nothing hides behind either one.

Take it and keep it limited window

When your build passes, a window opens to buy the whole product: full source, papers, and deploy steps in one ZIP. Run it anywhere, on your own key. Yours to keep, fork, or grow, with no tether back to us. [Window length and price: to be set.]

Let the forge run it hosted

Your build stays live with the people who forged it: hosted, managed, kept warm. No servers, no deploys, no ops. It is there before the window opens and long after it closes. [Hosted plan: to be set.]

Two doors, both real, neither one a trick. The buy-to-own window is time-limited on purpose; the hosted door never expires. Pick the one that fits how you work, or take both and sleep well either way.

Doors on the forge

Already built it somewhere else?

Most firings start from an idea. Yours would start from evidence: a thing that is already live and working on someone else's platform. That is a different starting point, and it has its own door.

Built on a Pickaxe? Smelter is your door

Smelter is this same forge, set up for Pickaxe makers: bring the one you already made and the firing starts from it, not from a blank page. Concrete prices, a firing in minutes. Go to Smelter.

Built on something else? Tell us what

Smelter is the first door cut into this forge, not the last. Which platform you built on decides which door gets cut next, so the waitlist asks. Join it below and say what you made.

Worth knowing before you choose: every build faces the same six gates on the way out, whichever door it came in. And a build forged without the five checks says so plainly, in a file that travels inside the ZIP. The forge writes down what it did, and what it did not.

Straight talk about the keys

The firing runs on ours. The product runs on yours.

The firing: our key

The forge burns the Crucible's own hosted key. You don't bring one, you don't paste one, and nothing you type here is an API credential.

The product: your key

The AI features in the build you take home expect an Anthropic (Claude) key in the environment where you deploy it. Yours, on your invoice, under your control. The ZIP itself ships with no key inside.

Yours to keep

The build is a real download you own: the source, the papers, the deploy. What you do with it next is your call.

No dark patterns, no fake countdown, no fine print doing the arguing. The Wolf and the Machine do the job, say so plainly, and get out of your way.

The forge is hot

Fire the Crucible.

Bring the idea. The checks run, you sign what survives, and the build starts in front of you.

Bring what you want to exist

You do not need a spec, a deck, or the right words for it. A clear description of the problem is enough to start the checks. Invitation-only for now: join the waitlist, sign in when your place opens, and bring it in.

Recommended

Start from the idea

Answer the five checks in plain language and sign the plan that survives them.

Or start from what you built

Already have it running somewhere? Bring it as it stands and the firing starts from there.

Tip: bring what you know about who it is for and what they are stuck on. That is what the checks work from. Coming from Pickaxe? Smelter walks you through it.

Plain answers

A few real questions.

What if the checks say my idea is bad?
Then you found out on an afternoon instead of after the build. The checks return plain verdicts and the reasoning behind them; they do not veto you. You can answer what they raised, narrow the scope until it holds, or carry a weak answer as a named risk and go anyway. What you cannot do is not be told.
Do I need a spec written before I start?
No. That is what the shaping is for. Bring a description of the problem and who has it. The signed plan is the output of the conversation, not a prerequisite for having it.
What is the signed plan actually for?
It is what the finished build gets measured against. Without it there is no fixed answer to "is this the thing we agreed on", and the assay has nothing to certify. It is also why changing a signed field brings it back for signature: the measurement is only worth something if the target stopped moving.
What happens if a gate goes red?
Delivery pauses and the screen names the gate and the reason in plain words. Then you choose: fix it and fire again, or sign to take the build as it stands, risk known and carried under your name in the papers. Nothing ever quietly ships as though it passed, and nothing is ever kept from you either.
Do I need a developer?
To run it as written, usually not; the DEPLOY file walks through it. To change it heavily, a developer helps, and now they can, because they have the source rather than a login.
Do I bring an API key?
No. The firing runs on the Crucible's own hosted key. The download ships with no key inside; when you deploy the build you add your own and it answers to you.
How is this different from asking an AI to build it?
An assistant will build what you asked for. The Crucible asks first whether it should be built, writes the answer down as something you sign, then builds it and proves it against six gates measured against that plan before it reaches you. The building is the least interesting part.
Can I do both, own it and host it?
Yes. Hosting it with us and buying the download during the window are not exclusive. Host it for convenience, own the source for control, or both.
What if I already built the thing?
Then bring it: the forge starts from what you built instead of from a blank page. Whichever road the firing takes, the papers in the ZIP say what was checked. A build with a signed plan carries its assay certificate; a build forged without the five checks says so in writing. Built on a Pickaxe, specifically? Smelter is that door.
Who is behind it?
IntelliBotique, a small practice in Nevada City, California. The Crucible is built through its own gated pipeline, which is the only endorsement of it worth anything.
You had the idea

Find out if it holds.

Five plain questions, a plan you sign, and a product that has to pass its gates before it reaches you. Owned outright, hosted by the forge, or both.

the forge is invitation-only, for now

Ask for a place at the fire.

Firings run in small batches. Leave your email and the invitation lands there when your place opens. Nothing to install; the build is yours to keep.

Already invited, or already a member? Sign in at the forge