The system the parole office never built.
Steel Man Resumes -- the Forge and the Refinery -- is career infrastructure for the person walking out with a ten-year gap on their resume and a disclosure question no one coached them to answer. Built for that person specifically.
Disclosure is a design problem, not a shame problem.
The standard advice on criminal-history disclosure is: be honest, be brief, move on. That advice is not wrong. It is just incomplete. It does not help you decide which employers to approach, how to frame the gap, what to say when the question comes up in an interview versus on a form, or how to build the surrounding narrative that makes the disclosure read as part of a coherent story rather than a red flag standing alone.
No existing career tool treated disclosure as a design problem. Most tools ignored it or outsourced it to a generic tips article. The Crucible was built to treat it as an engineering problem: one with inputs, a process, and an output you can test.
What was missing
Narrative infrastructure. A place to build the employment history truthfully, without shame, with strategic framing the user controls.
Disclosure architecture. A structured system for deciding when, how, and in what form to disclose, tied to specific employer categories and application contexts.
Compliance-first design. Any tool touching justice-impacted employment data carries legal and ethical obligations. No existing tool baked those obligations into the architecture.
Two tools. One through-line.
The Forge is the narrative engine. A user enters their employment history -- gaps, convictions, the full picture -- and the Forge builds a truthful, dignified narrative ready to anchor a resume, a cover letter, and a disclosure plan. It treats a justice-impacted history not as a liability to minimize but as material to work with honestly.
The Refinery turns that narrative into deployable documents: a resume, a disclosure plan calibrated to the specific employer context, and an application system that manages the full pipeline. The key architectural decision was that the connection between Forge and Refinery is not a file transfer; it is a live context link, so what is built in the Forge informs every output from the Refinery. The whole thing was engineered on a foundation of research -- a 33,543-word design brief with more than 150 peer-reviewed citations -- which is why the public claims are limited to what can be verified.
What got built -- verified at PL-027
32 API endpoints across JSearch job matching, R2 artifact storage, and decision logging. Compliance-first architecture throughout.
JSearch integration for job matching calibrated to fair-chance employers and justice-impacted hiring programs.
R2 artifact storage for user-generated documents. The user owns the output.
Decision logging so every disclosure recommendation is traceable to the inputs that produced it.
Live context bridge between Forge narrative and Refinery outputs. A persistent connection, not a copy-paste.
Two verified claims. Nothing beyond them.
The Crucible makes two public claims. Both are verifiable. No others are made on this page.
The person who was told to just be honest and move on.
The Crucible is not a general-purpose resume builder. It is built for the person with a justice-impacted history who needs to present that history honestly, strategically, and with enough narrative structure that the disclosure question does not derail the conversation every time it comes up. It is also built for the organizations -- reentry programs, workforce-development partners, navigators -- who work with that population and want a tool serious enough to trust with their clients' stories.
Who uses the Crucible
Returning citizens building their first post-release career narrative with honest, strategic framing.
Reentry navigators who need a tool they can walk clients through with confidence.
Workforce-development programs building a fair-chance hiring pipeline that does not treat disclosure as a liability to hide.
You might be wondering whether this is just another workforce-development tool with a dark color scheme.
Most workforce-development tools are designed for grant compliance: enough features to check a box, a dashboard that looks active, and a user experience no one ever called dignified. The Crucible was not built to satisfy a grant deliverable. It was built by someone who came through the system himself, who knows what the disclosure question feels like at 11pm before an interview, and who decided to engineer a better answer. The receipts on this page are what that work produced. They are verifiable, and the tools are live.
Working in reentry or workforce development?
Pilot access, partnership, and integration conversations are open. Start with what you are trying to solve.