Define the Inputs

The system begins with explicit source material — whatever you have:

• — A subject area or problem statement
• — Internal documents: SOPs, policies, manuals, product documentation
• — Regulatory or standards requirements
• — Desired learning outcomes
• — Role-specific constraints and assessment criteria
• — Nothing — just a description of what learners need to be able to do

If you have documents, they become the source. If you don’t, a clear description of your requirements is enough to begin.

Interpret the Knowledge Domain

Before generating content, Knowledge Foundry analyzes the subject to identify:

• — Core concepts and their relationships
• — Required competencies and prerequisite dependencies
• — Decision points and risk areas
• — Assessment moments
• — Alignment to curriculum, compliance, or quality frameworks

Documents are analyzed for structure, gaps, and inconsistencies. Where no documents exist, the system draws on deep domain knowledge to build a coherent model.

This phase is analytical, not generative. The system thinks before it writes.

Construct the Structured Framework

From the interpreted knowledge, a formal framework is built before a single lesson is written:

• — Sections, modules, and subtopics
• — Learning outcomes and must-teach requirements
• — Assessment points
• — Standards alignment — Bloom’s taxonomy, curriculum, compliance, or custom
• — Prerequisite dependencies

The framework is visible and fully editable before generation begins. Your team can add or remove chapters, adjust outcomes, modify dependencies, and confirm structure before any instruction is produced.

This is the defining shift: structure precedes content. Every time.

Generate Instruction Aligned to the Framework

Only after the framework is approved does the system generate instructional material:

• — Lesson content, activities, and assessments
• — Guidance, examples, and media blocks
• — Over a dozen block types per lesson — objectives, instruction, practice, summaries, case studies, assessments

The instruction follows the framework. Every piece of content has a defined purpose and a defined place within the program.

Your Team Reviews and Refines

Nothing is locked or auto-published. Your team retains full review authority over every block:

• — Review and edit any block independently
• — Re-order, re-generate, or revert any section
• — Adjust tone, complexity, or depth
• — Verify content against source materials
• — Add subject matter expert annotations

Individual blocks can be revised without touching the rest of the program. Every revision is version-controlled and carries a new content hash. The process is designed to support your team’s review workflow — not bypass it.

Your team approves. Nothing reaches learners without a deliberate decision.

Ready for Delivery

Once approved, programs are prepared for your delivery environment:

• — LMS deployment and enterprise rollouts
• — SCORM 1.2, SCORM 2004, and xAPI export for any compatible LMS
• — Multi-tenant and white-label environments
• — Audit-ready structure exports — HTML and PDF
• — Full delivery via KF LMS if needed

Deployments are verifiable: content is identified by hash so recipients can confirm what they received matches what was approved.