Capability · Framework Intelligence

Structure the subject before writing anything about it.

Framework Intelligence maps concepts, relationships, progression, and assessment logic. Instruction is written after that, not before. The framework is the object of record. Content is downstream of it.

framework://ingest · aml-ctf-v3.2
01
Why this matters

The framework is the thing that gets audited.

When a regulator, an accrediting body, or your own board asks how you know a program covers what it should, the answer is not the slide deck. The answer is the framework: the object that names every concept the subject requires, every assessment that confirms it, and every source that implies it must exist.

Without an authored framework, the coverage question has no defensible answer. With one, the answer is a file, and the file is testable.

Six moves inside Framework Intelligence

What the system actually does.

Concept mapping

Discrete concepts are extracted from source material, deduplicated across documents, and organized into a working ontology.

Relationship graph

How concepts depend on, contain, contradict, or supersede each other, modeled explicitly rather than implied by paragraph order.

Assessment logic

Which concepts must be assessed, at what depth, and with what evidence. All defined as part of the framework, before instruction begins.

Progression design

Prerequisite chains and cognitive load are laid down so learners meet concepts in the order the subject actually requires.

Alignment mapping

Each framework node ties back to a source requirement: a policy clause, a standard, a competency, or an accreditation statement.

Review gates

Frameworks are proposed by the system and approved by a human owner. Nothing generates until the framework is signed off.

How it runs

From source material to approved framework.

Framework Intelligence is a proposal-and-approval loop. The system proposes. A human owner approves. Nothing generates downstream until the framework is signed.

STEP 01

Ingest source

Documents, policies, standards, subject matter expert notes, and prior training material are ingested. Formats are normalized. Provenance is retained.

STEP 02

Extract requirements

The system identifies what must be known: concepts, capabilities, behaviors, and decisions. Each requirement is sourced back to the sentence that implies it.

STEP 03

Propose framework

A structured framework is drafted, covering concepts, relationships, progression, and assessment points. Reviewable, editable, and always cited.

STEP 04

Human approval

The framework owner reviews, revises, and approves. Only an approved framework can drive content production downstream.

What you get out

A framework you can review, revise, and defend.

The output is not a slide deck describing what the framework could be. It is a structured artifact, inspectable, versionable, and exportable, that becomes the source of truth for each downstream activity: content generation, gap analysis, verification, and evidence.

Concept nodes carry definitions, prerequisites, and source citations. Relationships are typed (depends on, contains, contradicts, supersedes). Assessment points specify the evidence a learner must produce to demonstrate competence. Provenance ties each node to the source sentence that implies it.

Common questions

How Framework Intelligence works, in detail.

Outlining tools capture what an author decides to write about. Framework Intelligence starts one level up. It extracts, from your source material, what must be true for a learner to be competent, and it represents that as a structured, traceable object separate from the instruction that will later teach it. The framework outlives any single course.
No. Framework Intelligence proposes a framework grounded in the source material you provide, and your subject matter expert approves, revises, or rejects it. What changes is what the SME spends their time on. Reviewing structure and edge cases, rather than writing paragraphs.
Yes, and this is common. The system reads existing training as source, extracts the framework it implies, then compares that framework to your authoritative documents. The gaps between the two are usually the story.
A structured object. Concept nodes, relationship edges, assessment definitions, and provenance links back to source. Readable by humans in the Foundry, and exportable to JSON, XML, or a spreadsheet for review outside the system.
You do. The framework and all its versions belong to your organization. If you leave the platform, you leave with the framework, its provenance, and its evidence.
Bring a subject

See your framework build itself.

Send us a policy, a standard, or a subject you already teach. We spend 45 minutes with the Foundry on your material, and you leave with the framework it produces. Yours to keep.

We reply within one business day.