How Divekit Works

A product-level view of how Divekit turns an origin into distributed repositories and evaluation results.

This section gives course maintainers the product model needed to plan and operate a distribution.

Start with the system overview to understand which content Divekit reads, which state it generates, and where student data crosses into GitLab.

Pages:

Contributors who need package boundaries, internal services, or GUI server details should use the canonical CLI architecture documentation.

Follow authored course content through distribution, student work, evaluation, and reporting.

Divekit uses a hierarchical configuration system with both global and project-specific settings.