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

workbook

IDEAL Lab Onboarding Workbook

This is the no-JavaScript companion to the local browser Passport. It follows the same route and is not a second exercise system. If the browser works, use the browser: it shows only your current mission and performs the checks safely.

This is the no-JavaScript companion to the local browser Passport. It follows the same route and is not a second exercise system. If the browser works, use the browser: it shows only your current mission and performs the checks safely.

1. Install The Two Prerequisites#

You need Git and GitHub CLI. You do not need Python, VS Code, Obsidian, SSH, or an AI tool before starting.

Open PowerShell on Windows, Terminal on macOS, or your normal terminal on Linux. Run one command at a time:

git --version
gh --version

Expected: each command prints a version. If both work, skip installation.

Windows 10 Or 11 / PowerShell#

Run only the missing installer:

winget install --id Git.Git -e --source winget
winget install --id GitHub.cli --source winget

Expected: the installer reports success. Close the entire PowerShell window, open a new one, and repeat the two version checks. If winget is unavailable, use the official Git installer and official GitHub CLI installer.

macOS / Terminal With zsh#

Run git --version; macOS offers the Command Line Tools installer if needed. If Homebrew is already installed, install GitHub CLI with:

brew install gh

Otherwise use the official GitHub CLI package. Do not install Homebrew only for this onboarding.

Linux / Local Terminal#

Use the official Git instructions for your distribution and the GitHub-maintained CLI package instructions. Do not use the Snap build of GitHub CLI. Reopen the terminal and repeat both version checks.

If an installer is blocked or asks for administrator approval, stop. Keep the short non-secret message and use the safe help page. Do not change security policy, antivirus, SSH files, or system permissions.

2. Start Once#

Run these commands one at a time on your computer:

gh auth login --web --git-protocol https

Expected: GitHub opens in the browser and gh auth status reports your account.

gh extension install soheylm-passport-sandbox/gh-passport --force --pin v0.3.0

Expected: the launcher installs without an error.

gh passport start

Expected: a browser opens at an address beginning with http://127.0.0.1:. Keep that terminal open. Select your computer and the work you will actually do. Read the public-record notice before confirming; no fork or public record is created before that confirmation.

3. Follow One Current Mission#

The dashboard always gives one next action. A mission follows this order:

  1. understand the outcome and concept;
  2. inspect one correct example and one common trap;
  3. perform the bounded action on the named machine and shell;
  4. compare the observed result with the expected result;
  5. choose Check my work;
  6. correct the specific feedback until the mission is ready;
  7. review the public-content confirmations and choose Submit mission once;
  8. continue only after the trusted GitHub result appears.

Do not create or edit submission files yourself. Follow only the current mission; the launcher manages its public learning record in the background.

4. Submit One Mission#

The mission page creates a sanitized structured submission. If the mission has a synthetic practice file, it copies only the exact file declared by that mission. It never stages arbitrary files.

Before Submit mission, confirm that the generated answers and declared synthetic files contain no credential, private path, ETH identifier, real log, research data, screenshot, or confidential detail. Your GitHub username and the exercise result are public.

Expected: the page says Submitted to GitHub, waits for the automatic check, and then opens the dashboard. Do not submit again or create an empty commit. If no result appears after 30 minutes, use the dashboard's public non-secret help link once and return later.

When the Git mission begins, the Passport creates a separate practice folder and explains the required concepts and commands there. Until then, you do not need to understand or operate the record behind Submit mission.

5. Resume Later#

Close the browser and stop the local server with Ctrl+C when finished. Later, open PowerShell or a terminal and run this from any folder:

gh passport open

Expected: the browser restores the last page saved on this computer and then synchronizes trusted completion from GitHub. Do not reinstall or clone again.

6. If Blocked#

Run from any folder:

gh passport doctor

Keep the exact short non-secret error. Do not repair SSH, permissions, remotes, branches, PowerShell execution policy, or antivirus settings by guessing. Use the dashboard help link or the troubleshooting index.

7. Finish Line#

Training is complete only when the trusted dashboard says the assigned route is complete. A local checkbox, browser history, or AI answer is not a completion record. Real account access, data ownership, or authorization may still require the separately named operational owner; this does not make a routine training mission wait for a person.