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.
IntelliBotique is the practice. The Crucible is its product. The Smelters are products built on the Crucible, each one shaped for a different kind of maker.
Most software gets built before anyone checks whether it should exist. The Crucible works the other way round. A bad answer here costs you an afternoon. The same answer after launch costs you a year.
Is somebody actually stuck on this, or does it merely sound useful when you say it out loud?
What it costs to run, what somebody would plausibly pay, and whether those two numbers survive being put next to each other.
The claims it would make, the data it would touch, the promises it quietly implies. Not legal advice.
Can this be built as described, at this scope, with what exists today.
Whether it could go in front of real people without costing you your reputation.
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.
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.
It compiles. An unresolved import is a product that will not start on the machine you put it on.
Duplicate modules, unsafe cookies, missing security headers, dead code. The dull failures that reach production most often.
WCAG 2.2 AA. Shipping a product that some of your users cannot operate is a decision, so it is treated as one.
It gets built and started for real, not inspected and assumed. A product that only compiles is not a product.
Whether it looks like something a person made on purpose, rather than the default output of a machine.
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. The gates inform your call. They never take it from you.
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.
Every file, in the open. Change a line, add a feature, or hand it to a developer who will.
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.
It runs where you say: your laptop, a rented server, the cloud account with your name on the invoice.
A Smelter is the Crucible set up for one kind of maker. Two are running now. The forge is invitation-only for now: join the waitlist, and the invitation lands when your place opens. Smelter is the first door cut into this forge, not the last.
You built the Pickaxe. Now own it.
Your Pickaxe is live and doing its job. Smelter forges a second edition you can hold: the full source, the docs, the deploy steps, one ZIP, signed over to you.
Go to Smelter ↗ For venturesSay the thing that has been bothering you. Twenty ventures come off it and nineteen die on the board. The one still standing, you have to win.
Six booths, and each one you clear takes another veil off the animal.
Step onto the midway ↗Worth knowing before you choose: every build faces the same six gates on the way out, whichever door it came in.
Five plain questions, a plan you sign, and a product that has to pass its gates before it reaches you.
Not legal advice. Not financial advice.