Experienced Fast-Path Diagnostic

Use this page only if you can already demonstrate several competencies. The fast path changes pace, not safety policy or verification.

If Git, GitHub CLI, branches, pull requests, or command-line verification are new to you, stop here and follow the beginner workbook from step 1. Do not use this diagnostic to skip practical work you cannot yet reproduce independently.

Start The Same Passport#

Experienced and beginner routes use the same launcher. On your computer, open a separate command terminal (PowerShell on Windows, zsh on macOS, Bash on Linux).

Check the account. Keep the status output private.
```
gh auth status --active --hostname github.com
```
Only if no intended account is active, sign in, then repeat the status check. Stop if it still names another account.
```
gh auth login --hostname github.com --web --git-protocol https
```
If you already have a working Passport on this computer, run gh passport open and continue there. On another computer, use resume. Neither case needs a new Passport.
For first installation only, install the compatible launcher and start it.
```
gh extension install soheylm-passport-sandbox/gh-passport --pin v0.12.1
gh passport start
```
Expected: the local browser opens your lesson list. If installation reports an existing extension or startup stops, use the named failure in the help index; do not delete the course folder.

Select every activity your work requires. The route always includes the universal safety core and adds prerequisites automatically. Do not create a second local setup if you already started; resume from any folder with gh passport open.

Use Existing Evidence Carefully#

Read the outcome and independent verification first. Keep working tools and accounts, and proceed at your own pace. Both current 3.0.0 and retained 2.1.2 require the declared small fictional files, structured choices and checks; it does not automatically accept an arbitrary real-project artifact or explanation instead. Keep any separate operational review private. You may not skip:

lab-specific account, data, incident, and shared-compute policy;
objective verification;
the public-content safety check;
the controller result;
any separately named operational approval required for real access or ownership.

Experience does not make broad logs, ETH or other private identifiers, real project data, or credentials safe to publish. Your GitHub username is already visible through the fork; do not add further identity data. If an existing file or result contains any of those, create a fictional minimal example instead.

Responsibility Map#

Activity	Required track
Edit or review GitHub content	Code Contributor
Develop or run Python projects	Git then Reproducible Python
Use coding agents	Git baseline then AI Agent User
Run Euler CPU jobs	Euler CPU
Run Euler GPU jobs	Euler CPU then Euler GPU
Manage shared research data	Data Steward
Use Blade	Blade User
Supervise or approve access	Supervisor and Staff

If you cannot independently explain or reproduce a mission's verification, complete the practical steps rather than claiming equivalent evidence.