Content Forge

When Forge is enabled for your organization, open Studio → Forge — *"Drop company knowledge → atomize → draft course + quiz + ack doc → publish."* Running jobs requires Run Forge (forge:run); approving and publishing drafts requires Publish Forge (forge:publish).

Run a job

1. Enter a Source title and paste the Source body — a manual, SOP, or policy text between 20 and 200,000 characters. (File upload and folder connect are not in the Studio UI yet; paste text.)
2. Choose Drop & build.
3. The job appears under Jobs and moves through the pipeline stages: queued → extracting → atomizing → mapping → packaging → awaiting_review. Failures show failed with a Retry button.

Review the draft

Open a job to see:

• Coverage — *{n} atoms · {n} topics* extracted from your source
• Knowledge atoms — the extracted facts; remove any that are wrong before publishing
• The draft package — a Course, cited Quiz items, a Document, and a Program that ties them together

Approve and publish

When the draft looks right, choose Approve, then Publish to Learning. Publishing creates real content in your library: a published course, its quiz, a published acknowledgement document, and a published program containing the course and document steps. Follow the Open in course builder link to refine the course like any other — then assign it.

If Forge is not visible, it is either not enabled for your organization or your role lacks Forge permissions — the server reports *"Content Forge is not enabled for this tenant"* when the feature flag is off.