How Divekit Works

Mon, 01 Jan 0001 00:00:00 +0000

Divekit turns one maintained course origin into individualized repositories and keeps the resulting distribution operable throughout an assignment. This page explains what is authored, what Divekit generates, and which boundaries need care before a real cohort is involved.

You can operate Divekit through its CLI or its web interface. Both use the same origin and distribution model.

From Origin To Results

flowchart LR
 MAINTAINER((Course maintainer))
 ORIGIN["Authored origin<br/>course files + .divekit/"]
 MEMBERS["Member input<br/>kept outside the origin"]
 DIVEKIT["Divekit<br/>CLI or web interface"]
 STATE["Generated distribution state<br/>individuals.json + remotes.json"]
 LOCAL["Local provider output"]
 WORK["GitLab work repositories"]
 STUDENT((Students))
 EVAL["GitLab eval repositories"]
 PLUGINS["Pinned plugin suites"]
 RESULTS["Plugin results<br/>reports + feedback"]

 MAINTAINER --> ORIGIN
 ORIGIN --> DIVEKIT
 MEMBERS --> DIVEKIT
 DIVEKIT --> STATE
 DIVEKIT --> LOCAL
 DIVEKIT --> WORK
 DIVEKIT --> EVAL
 STUDENT --> WORK
 WORK --> EVAL
 PLUGINS --> EVAL
 EVAL --> RESULTS
 RESULTS --> STUDENT
 RESULTS --> MAINTAINER

1. Author The Course Once

The origin repository is the maintained source for an assignment. It contains the course files and .divekit/ configuration that describe distribution, individualization, and optional evaluation behavior. Variation choices and individualization rules are authored inputs too.

Configuration Model

Mon, 01 Jan 0001 00:00:00 +0000

Divekit configuration is split across user-level and project-level files. This page explains the configuration model that course maintainers use. Detailed JSON schemas, keys, and fallback rules now live under Reference.

1. Configuration Layers

Divekit uses three practical layers:

User-level defaults in ~/.divekit/
Project-level defaults in <origin-repo>/.divekit/
Distribution-specific overrides in <origin-repo>/.divekit/distributions/<distribution>/

The CLI resolves files from the most specific layer outward. This keeps shared defaults reusable while still allowing per-distribution overrides.

2. User-Level Configuration