Curriculum previewThis is not your assigned passport. No identity, answers, or completion progress are stored here.How to start your passport
Handbook / maintainers

maintainers

Freshness And Source Policy

Volatile policy/reference pages should state:

Metadata#

Volatile policy/reference pages should state:

Owner:
External/system facts verified:
Review by:
Primary sources:

Use a three-month review window for Euler, AI tools, data/security rules, and account capabilities. Use six months for stable lab procedures unless a known change requires earlier review.

Primary-Source Order#

  1. Current ETH policy or ETH HPC documentation.
  2. Live read-only system inspection for lab-specific facts.
  3. Official vendor/project documentation.
  4. Lab-owner decision for local policy.

Community tutorials may help explain a concept but must not establish current ETH policy, quotas, entitlements, or security behavior.

What Verification Means#

Do not change a date merely because a link still opens. Check the specific claim, command, expected result, affected operating system, and relevant lab policy. Record uncertainty rather than turning an assumption into a rule.

High-Risk Volatile Claims#

  • Euler accounts, limits, partitions, GPU identifiers, storage, and tunnel behavior.
  • es_fuge entitlement and student caps.
  • AI tool assessments and allowed data classifications.
  • Package, Python, CUDA, PyTorch, editor, and extension versions.
  • GitHub authentication and API/security behavior.
  • Software available on shared Blade/lab machines.

Scheduled Review#

The documentation checker validates that named volatile pages contain review metadata. A scheduled workflow should open or update an issue when a date has expired; the maintainer then verifies the facts rather than automatically advancing the date.