Lab — Triage Notes
Simulate triage thread on report draft — lifecycle, communication, payment outcome literacy.
Visual · t20_triage_lab
Lab: mock triage on report draft. Original Cyberlium.
Practice the conversation before it happens live — needs-info, downgrade, dup, and polite close.
Using Report Lab DRAFT: (1) write mock triage thread — triager asks for clearer step 3, hunter replies with numbered clarification and redacted screenshot reference; (2) second scenario: severity downgrade with polite hunter response citing rubric + accepting Medium; (3) third scenario: duplicate notice — hunter thanks and documents root cause lesson; (4) note expected payout range from $PROGRAM table for assigned severity or honest $0 dup outcome. All fictional thread in chmod 600 notes — not posting to real program until ready. No harassment role-play, no disclosure threats in exercise.
1. Scenario writing
Three threads: needs-info, downgrade, duplicate — each ≤6 messages hunter side.
Use professional tone templates from Communication lesson.
Command guide
Try these commands — Scenario writing
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Triage notes — status + reply plan Program communication — in-platform only
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install curl
macOS: Built-in
Windows: Built-in (PowerShell: Invoke-WebRequest)
═══ LINUX / macOS ═══
Command — copy this
cat > "$HOME/cyberlium-lab/t20-triage-notes.txt" <<'EOF' status: new | needs more info | duplicate | resolved reply_plan: polite, factual, no pressure payment: platform rules vary; not guaranteed EOF
Command — copy this
source "$HOME/cyberlium-lab/t20-scope.env"; curl -sS -I "https://$SCOPE_HOST" 2>/dev/null | head -5 || curl -sS -I https://httpbin.org/ | head -5 grep status "$HOME/cyberlium-lab/t20-triage-notes.txt"
Primary tools to practice this lesson: grep, curl. Reference sites: Triage notes; Program communication. Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Lifecycle mapping
Label state transition per scenario: New → Needs info → Triaged, etc.
Note realistic wait times between messages in fiction (e.g., 3 business days).
3. Learning extraction
One paragraph: what you will do differently on next real submission.
Payment outcome noted without entitlement — learning value explicit.
4. What you ship: triage lab pack
Three mock threads + lifecycle labels + learning paragraph — chmod 600.
5. What you record before the next lesson
Triage lab pack path.
6. Wrong vs right: random sites vs in-scope program
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
- Wrong: Mock thread where hunter threatens triager for downgrade.
- Right: Triage lab pack with professional scenarios. Next: quiz.
Mission: triage lab
1) Write three mock triage threads. 2) Label lifecycle states. 3) Learning paragraph + payout note. 4) Secure notes chmod 600.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “Dup thread — when to accept gracefully?”
APPLY: Triage lab practices:
APPLY: True or False: Mock threads should include disclosure threats.
APPLY: Dup scenario hunter should: