Culina Academy

Learn the Culina framework.

Explore the operating model behind the framework: what gets defined, what gets reviewed, and what runs.

Culina Academy

Read the framework in more detail.

The Academy repository documents the Culina framework in depth, including delivery methodology, business-owned metadata, validation patterns, and the batch ETL operating model.

Open GitHub

Understand the documented operating model

Culina Academy documents the delivery methodology, business-owned metadata, validation patterns, and batch ETL operating model. Start with how requirements and discovery become a model, then follow how approved metadata defines the work. That distinction explains why configuration needs review before execution.

The documented architecture separates the control plane, orchestration, and data plane. Readers can examine what each owns, how a queue execution differs from a job definition, and how payloads and results connect those responsibilities.

Read validation with its limits

Further study can focus on the difference between returned workload diagnostics and official execution evidence, and between automatic retry and an operator-controlled rerun. Those distinctions matter when interpreting a failed or waiting job.

Validation also has a defined scope. The documented checks do not establish every business rule, and enabled checks run after the target write. Read the model alongside these limits rather than treating a completed status as universal proof of correctness. Continue in the existing Culina Academy GitHub repository.