Eve library

Neith Training Program

Guide

Revision 1

On this page

Phase 52 training hub for the implemented Neith footprint. Use this guide to route engineers and operators into the correct learning track before they start changing release workflows, certification gates, or Neith Linux platform infrastructure.

Audience#

  • release engineers onboarding to @neith/release
  • QA contributors extending @neith/qa
  • platform engineers and operators validating @neith/linux

Learning Tracks#

Track Primary surface Focus Recommended outcome
Release operations docs/domains/neith/release/ versioning, rollout safety, distribution, publishing, and signoff can ship and recover a certified release train safely
Certification authors docs/domains/neith/qa/ deterministic auditors, evidence ledgers, fixture tests, and API docs can add a new Phase 52 certification gate without doc drift
Linux platform docs/domains/neith/linux/ flake validation, ISO/image workflows, modules, updates, and recovery can validate Neith Linux changes with reproducible verification

Suggested Role Paths#

  • release managers: finish the release track first, then the QA track if you need to own certification evidence
  • QA maintainers: complete the QA track and the release track so certification claims stay grounded in real workflows
  • platform owners: complete the Linux track and the release track when changes affect self-hostability or distribution evidence

Certification And Evidence#

Training is considered complete for Phase 52 only when each implemented Neith surface has:

  • structured learning objectives
  • hands-on labs tied to real repository workflows
  • an assessment or evidence checklist showing what successful completion looks like

The published certification for this criterion lives in docs/domains/neith/training-materials-certification.md.