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:

gh auth login --web --git-protocol https
gh extension install soheylm-passport-sandbox/gh-passport --force --pin v0.3.0
gh passport start

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#

For each mission, read the outcome and independent verification first. You may submit a concise sanitized explanation or equivalent bounded artifact when the mission permits it. 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 artifact contains any of those, create a fictional minimal example instead.

Responsibility Map#

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