Contributors¶

The tab for people who change the estate's code: Nerthus.Platform, Nerthus.Config and this site. Running a site is Hosting. Nerthus.Core takes bug fixes only, and its code is described in Nerthus.Core (until cutover).

Start here¶

• The ecosystem map - which repositories exist, and how they connect.
• The working regime - how a change reaches main: branches, commits, merge requests, what runs locally and what only on GitLab.
• Read the programmes' history - where a task id lives in a commit, the branch names, and the commands that read a sprint or a task back.
• Write documentation - how a page on this site is written.

Nerthus.Platform¶

• Work on Nerthus.Platform - a clone to a green local run.
• Cut a Platform release - the tag, the image and the lock.
• The database - the two schemas and what each holds.
• The Platform pipeline - the jobs a merge request runs.
• Instance secrets - an instance's identity and its store.
• Credential classes and the redaction filter - every access-granting value, its ceiling, and why the program cannot print one.
• Sensitive data - the classes that are encrypted wherever they rest.

Nerthus.Config¶

• Nerthus.Config - what it owns and what it does not.
• Work on Nerthus.Config - a clone to a green local run.
• Test a cookbook - the unit, machine-container and VM arms, and what a container cannot prove.

Nerthus.Docs¶

• Nerthus.Docs - this repository, its checks and what they guard.

Where the rules live¶

The estate's design decisions are rulings, taken with the operator and kept in the workspace beside the checkouts; each repository's CLAUDE.md carries the rulebook it obeys. A page here states a rule for its reader and may cite the ruling's number; it does not argue it. Reference pages for routes, commands and errors are generated from each repository's contracts, not written here.