Curriculum-as-Code on Coach Alan

Essay 36: What If I Didn't Standardize the Loop?

Wed, 23 Sep 2026 08:45:00 -0700

In the architectural evolution of Curriculum-as-Code (CaC) across our higher education courses and clinical exercise science programs, few frameworks have proven as foundational as the Mission Loop (Pattern / Rule / Solve).

By demanding that every learning challenge follow an explicit three-phase pipeline—observing empirical telemetry, confronting it with non-negotiable Single Source of Truth (SSoT) constraints, and deriving a human-verified solution—we insulated our classrooms from generative AI hallucination and restored the cognitive friction of authentic deduction.

The Logic Grid: Why Good Assessment Looks Like Sudoku (and How the Mission Loop Solves the AI Crisis)

Thu, 03 Sep 2026 10:00:00 -0700

The conversation surrounding generative artificial intelligence in higher education has fixated on the wrong villain.

We wring our hands over language models because they can instantly generate a cohesive, grammatically pristine 500-word essay on physical inactivity or socioeconomic barriers to healthcare. In response, institutions have spent millions on probabilistic detection software that flags innocent non-native English speakers while failing to detect basic prompt injections.

The crisis is not that the machine can write. The crisis is that our assignments were built to reward surface-level fluency rather than analytical deduction.

Curriculum-as-Code, ADA Title II Compliance, and Fleet-Wide Accessibility Refactoring

Tue, 25 Aug 2026 16:53:00 -0700

When the Department of Justice codified WCAG 2.1 AA standards under ADA Title II for public higher education institutions, it ended the era of reactive, page-by-page accessibility audits. Traditional post-publication fixes inside LMS rich text editors fail to scale across multi-section course fleets.

Achieving sustainable compliance requires moving accessibility upstream into a version-controlled engineering workflow: Curriculum-as-Code.

The Upstream Accessibility Pipeline

By authoring instructional materials in standardized Markdown and validating them through automated linting pipelines before deployment, entire categories of accessibility errors are eliminated at the source.

Essay 17: Engineering Resilience: Resolving False-Positive Contrast Errors and Array Parsing Script Failures via Curriculum-as-Code

Fri, 14 Aug 2026 00:00:00 +0000

Essay 17: Engineering Resilience: Resolving False-Positive Contrast Errors and Array Parsing Script Failures via Curriculum-as-Code

TL;DR: Automated accessibility checkers in Learning Management Systems often flag false-positive contrast errors due to array parsing script failures caused by deeply nested, visual-editor HTML bloat. Curriculum-as-Code (C-a-C) resolves this at the source by replacing GUI color adjustments with deterministic Markdown pipelines, native semantic hierarchies starting at <h2>, and zero inline color overrides.

The Guided Learning Trifecta: AI Simulation, Clinical Application, and Deterministic Auditing

Tue, 11 Aug 2026 00:00:00 +0000

The Guided Learning Trifecta: AI Simulation, Clinical Application, and Deterministic Auditing

When higher education institutions scramble to integrate Generative AI into workforce programs, they usually make one of two mistakes: they treat AI as a passive text summarizer, or they fear it as an unstoppable cheating engine. Both approaches miss the true potential of intelligent instructional engineering.

In applied health sciences and vocational education, AI should neither replace human instruction nor act as an open-ended conversational oracle. Instead, it must be deployed as a structured, deterministic learning partner within a three-tier execution pipeline: The Guided Learning Trifecta.

The Mission Loop Architecture: Pattern, Rule, and Solve in Coded Instruction

Tue, 11 Aug 2026 00:00:00 +0000

The Mission Loop Architecture: Pattern, Rule, and Solve in Coded Instruction

In traditional health science education, assignment prompts often ask open-ended questions like “Describe how you would design an exercise program for a diabetic client.” While well-intentioned, these unconstrained assignments invite vague responses, obscure student reasoning errors, and make objective assessment extraordinarily difficult.

When curriculum is engineered as code, learning tasks require a structured, deterministic execution pipeline: The Mission Loop.

The Vibe-Coding Paradigm: Speed, Intuition, and Full-Stack Execution in Instructional Engineering

Tue, 11 Aug 2026 00:00:00 +0000

The Vibe-Coding Paradigm: Speed, Intuition, and Full-Stack Execution in Instructional Engineering

For decades, building custom educational software or interactive lab tools required navigating a massive barrier to entry: armies of full-stack developers, months of sprint cycles, and rigid proprietary frameworks. If an educator wanted an interactive molecular flavor workbench or an agentic PWA for clinical exercise testing, they were forced to submit feature requests to software vendors and wait years for bloated, one-size-fits-all releases.

Continuous Integration for Pedagogy: Writing Automated Unit Tests for Learning Outcomes

Tue, 04 Aug 2026 00:00:00 +0000

Continuous Integration for Pedagogy: Writing Automated Unit Tests for Learning Outcomes

In software engineering, continuous integration (CI) pipelines run automated test suites on every commit to ensure system contracts remain unbroken. In traditional instructional design, however, curriculum changes are committed without automated verification—resulting in broken prerequisites, unmapped learning outcomes, and silent accessibility regressions that go unnoticed until students encounter them.

Continuous Integration for Pedagogy shifts quality assurance from a manual pre-semester review to an automated background process running on every Git commit.

Instructional Engineering: Transforming Curriculum into Version-Controlled Source Code

Thu, 30 Jul 2026 00:00:00 +0000

Instructional Engineering: Transforming Curriculum into Version-Controlled Source Code

For decades, instructional design has treated educational content as static documents trapped inside proprietary Learning Management Systems or binary PDFs. Instructional Engineering replaces this reactive model with software design principles: modularity, automated linting, plain-text portability, and continuous delivery.

The Shift from Design to Engineering

Traditional instructional design focuses heavily on visual presentation within specific tools. Instructional Engineering treats content as an evolving software system that must meet strict operational criteria: