Module Template

Every module in this curriculum follows the same skeleton, so a student can move between audiences — or between this course and the fellowship — and always know where the pieces live. This file is the contract.

The parts of a module

A module is a sequence of sessions. Each session is designed to run 45–75 minutes and contains exactly these parts:

Part	What it must contain
Session title	The name of the session, phrased as a question or a promise.
Learning objectives	2–4 concrete, checkable things a student can do after the session. Start each with an action verb: explain, compare, build, decide, defend.
Session plan	A minute-by-minute arc for the session, written for the instructor. Typically: open the question (5 min) → teach the concept (15–20 min) → apply it to a concrete case (15–20 min) → discuss (10–15 min) → close with the week's assignment (5 min).
Discussion prompts	2–4 questions that force application, not recall. The best prompts start with "What would you do…" or "Defend a position…"
Homework / reading	The reading (always cite the specific doctrine or literacy doc) and the deliverable (always concrete: a one-pager, a scored pursuit, a map).
Comprehension check	2–3 short questions for the student to self-check before the next session. Not graded.

The shared core and the audience track

The curriculum has one spine and three accents:

• shared-core — the six sessions every student takes. This is the pipeline, taught once, well. Nothing here is optional.
• strategic-initiative — six sessions for students from Strategic Initiative programs: the ecosystem, portfolio strategy, gate governance, the doctrine as an operating system.
• mba — six sessions for MBA students: business structure, revenue and margins, pricing-to-win, positioning, NAICS/HUBZone as go-to-market.
• mpa — six sessions for Masters in Policy Administration students: the public side, money flow, FAR and compliance, grants management, oversight and equity.

The core gives everyone the shared language; the track gives each audience the accent that matches their career. A student who takes the core plus any track has the full course. A fellowship participant and a college student following the same module are learning the same doctrine — that is the point of the shared skeleton.

Conventions every module must follow

1. Concepts, not tools. Sessions may mention that a system of record or an AI layer exists. They must never depend on a specific product. If a session cannot be taught with paper, pencil, and the doctrine docs, it violates the stack-agnostic rule (doctrine/08).
2. Real documents, safe exercises. Students should read real RFPs and NOFOs from SAM.gov and Grants.gov. Never ask them to chase live submission deadlines; use published, closed opportunities as teaching objects.
3. The pipeline is always in the room. Every session should connect to where it sits in the pursuit pipeline (doctrine/03), even when the session's topic is literacy or case work.
4. Self-checks, not pop quizzes. Comprehension checks are for the student, not the gradebook. Graded assessment lives in course/assessments-and-rubric.md.
5. The case travels. The Ravonics case (case-study/ravonics.md) is the shared teaching object — use it in every module so all audiences exercise the same company through the same doctrine.

How to adapt the template

If you are writing a new module:

1. Copy this file.
2. Replace the audience paragraph in "The shared core and the audience track."
3. Keep the skeleton: six sessions, each with the six parts above.
4. Map every session to the doctrine docs it teaches (the manifest.yaml registry will help you check coverage).
5. Run it past the stack-agnostic rule before you call it done.