Status Governance Evidence: AI Without the Hype

This working record captures observed evidence during the first complete module-development cycle. It does not establish a replacement status system or change learner-facing metadata.

Item	Current production language	Current learner availability	Owner	Evidence available	What would advance it?	Ambiguity
Module source page	Draft; learning-design package assembled and ready for cold review	Drafting in frontmatter and the Track Guide	Mike	Revised module page, outcomes, boundaries, and next steps	Cold review and facilitator dry run	Whether learner availability should be shown on every module page
In-person presentation	Internal presentation outline complete for rehearsal	Not currently offered; no format-specific label assigned	Mike	Slide outline and speaker notes	Camera rehearsal, facilitator dry run, and delivery approval	Whether format status should differ from module status
Human video explainer	Internal brief complete; no recording exists	Not currently offered; no format-specific label assigned	Mike	Video brief and rehearsal checklist	Camera rehearsal, captions/transcript plan, and review	Whether a video needs its own lifecycle and availability
Facilitator guide	Internal guide complete for dry run	Not currently offered; no format-specific label assigned	Mike	Facilitator guide, safety opening, and redirects	Nonauthor dry run and review	Whether brief source notes count as facilitator material
Learner worksheet	Internal printable worksheet complete	Available for internal review only	Mike	Reflection worksheet and take-home artifact	Learning-design and accessibility review	Whether a worksheet is required before any internal demonstration
Safe example set	Internal example bank complete, including backup transcript	Available for internal review only	Mike	Maple Park demo, eight learner options, and exclusion list	Safety/privacy review and facilitator rehearsal	Whether examples inherit module status or need separate review state
Feedback form	No approved form or route exists	Not available; the Track Guide makes no claim that a feedback route is live	Mike	Track Guide limitation statement	Approve a feedback route and response owner	Whether feedback availability is module-level or Lab-level
Pilot notes	No pilot notes exist	Not stated	Mike	Module status notes identify work needed before pilot	Run an approved pilot and capture findings	Whether pilot notes are a lifecycle stage, an evidence artifact, or both

Questions Raised

• What evidence distinguishes a source sketch available for internal review from a learner-available module?
• Does learner availability apply to a whole module, each delivery format, or both?
• Who owns the module, its delivery formats, and any changes to their status?
• What defines cold review or pilot preparation for this first module package?

Conflicting Labels

• The source package now uses production lifecycle Draft and learner availability Drafting; the evidence does not determine whether every module page should display the availability field.
• Mike is the current owner across the module source and supporting package. Reviewer roles are not yet assigned. Reviewer recruitment is in progress, and independent review work is deferred to the week of July 20.
• Separate internal source artifacts now exist for the presentation outline, video-explainer brief, facilitator guide, learner worksheet, safe example bank, and internal test plan. They remain drafts awaiting camera rehearsal, independent review, facilitator dry run, and testing.

Decisions That Could Not Be Made

• Whether format preparation should ever receive its own learner-facing availability label.
• Whether delivery formats need their own lifecycle and learner-availability fields.
• Whether a separate backlog disposition is useful beyond GitHub workflow.

Who Needed Authority

• Mike currently owns the module package and approves interim changes. Learner availability, pilot use, feedback routes, and any later status-system change still require explicit approval. Independent reviewers and facilitators have not yet been assigned.

Review Timing

Mike is recruiting reviewers.

Until the reviewer bench is established:

• Mike remains the current owner.
• Camera rehearsal and author self-review may continue.
• The package may be prepared for review.
• No author review should be represented as cold review or independent validation.
• Safety, privacy, accessibility, learning-design, and nonauthor facilitator reviews remain pending.
• Review work is targeted for the week of July 20, subject to reviewer availability.

What Learners Would Need to Know

• This is a recommended introduction, not a required gateway.
• It is still being developed and is not presented as a currently available class, video, or support service.

What Contributors Would Need to Know

• Record evidence and open questions here; do not introduce new status fields, badges, or catalog-wide terminology before the governance checkpoint.

Recommended Governance Changes

• None before the checkpoint. Use this evidence with a contrasting early-stage module before deciding whether any change is warranted.

---

Source: ops/status-governance-evidence/ai-without-the-hype.md