Step 347. Competing in the Target Competition — The Curriculum’s Reckoning

Level 4 — Professional | Difficulty ★★★★★ | Estimated time: 2–3 weeks (training cycle) + 48 hours (completing the competition)

Prerequisites: the competition cycle of Steps 324–328, the championship-bid season of Steps 336–340, and the team operations plan v2 of Step 346. This chapter is, in effect, the graduation exam of this curriculum.

What you need: one confirmed target competition for the season, team operations plan v2, playbook v2.0 (Step 344), a tidy tool library, and your best condition.
Caution: every competition scene, rank, and log in this chapter is a screen example. The real competition is the one you fight yourself; this book only helps design that day’s operations.
⚠️ All exercises in this chapter are for your own lab and legal platforms only. Applying them to unauthorized systems is a crime. Read and follow the competition rules (team size, no external collaboration) before the start.

Do you remember the day you first opened PowerShell? Typing Get-Location, reading for the first time the location the prompt pointed to. From that day, you’ve passed through 347 Steps — getting comfortable in the terminal, learning code, understanding networks, taking your first shell, despairing at your first competition, challenging the OSCP, and coming to lead a team.

Today is the day you pour all of that accumulation onto one stage. The goal is one — your personal and team best. But before the start, let’s make one agreement and carry it in. This competition is not an end — it’s a milestone. Security is not a game that ends with one competition, and you have already become someone who can keep going. That agreement turns pressure into power.

1. Learning Objectives

By the end of this chapter, you will be able to:

Confirm the season’s target competition and design a training cycle to match it
Preside over the final pre-competition check (field placement, operating rules, equipment, library)
Perform the leader’s mid-competition roles: rotation orders, mood operations, information hub
Manage zero-solve stretches and losing streaks with planned procedures
Formalize the final record after the end and hand it over as material for the completion reckoning

2. Background Knowledge — Today’s Tools and Concepts

Today’s Tools at a Glance

Category	Details
Language/environment	Every weapon so far — playbook v2.0, the tool library, the team channel
Today’s commands	No new commands — everything 348 Steps taught you is today’s command
Concepts needed	The training cycle (focus, review, condition), the final-check checklist, the leader’s mid-competition roles, formalizing records
Today’s deliverable	A training plan + a final-check list + a competition log + an official record document

2-1. The Character of a Reckoning Competition — Not Measurement, but Expression

This competition’s goal is "a new personal best," but the philosophy of preparation is the opposite — not a day of stacking new things, but a day of pulling out everything you have. Same as not opening a new concept the night before an exam.

So the training cycle’s final week is filled not with learning new techniques but with three things — a final review of weaknesses (repeated mistakes in recent competition logs), a check of the library and playbook (do the tools open, are the cards current), and condition management. On this stage, condition is part of the tech stack.

2-2. The Training Cycle — Focus → Review → Condition

Split the time from the target competition’s confirmation date to competition day into three parts.

Training cycle (screen example — assuming confirmation 3 weeks out):
[Week 1] Focused training — marathoning last year's problems from the target
         competition and Write-ups of similar ones, 2 team mock CTFs (matched to real hours)
[Week 2] Weakness review — re-confirming each person's "repeated mistakes list,"
         final spurt for the empty field's growth assignee, playbook v2.0 consistency check
[Week 3] Condition — new techniques forbidden, sleep rhythm matched to competition
         hours, equipment check, complete rest the day before

A team review meeting attaches to the end of each week. This cycle’s enemy is "cramming until the day before" — a 48-hour competition’s result is made not by the 48 hours before it but by the structure of the 3 weeks before it.

2-3. The Final Check — The Leader’s Day-Before Checklist

The items of the check the leader presides over the day before the competition. Not a technical check — an operations check.

Final-check checklist (screen example):
[ ] Field placement — final confirmation of the assignment table (Step 346), backup order in case of absence
[ ] Operating rules — shift schedule, handoff format, re-confirmation of the 2-hour rotation rule
[ ] Equipment — each person's machine boots, VPN/lab environment, tool launch tests
[ ] Library — wordlists, scripts, the latest commit of playbook v2.0
[ ] Channel — team channel tidied, information-hub document (shared notes) opened
[ ] Sleep — everyone's bedtime/wake plan confirmed (timezone strategy, Step 328)

A surprising number of teams skip the "tool launch tests." An accident where the VM won’t boot in the competition’s first 30 minutes is not a technical defeat but an operations defeat — and an operations defeat is the most bitter kind.

2-4. The Leader’s Mid-Competition Roles — 48 Hours as the Center of Gravity

Step 346’s center-of-gravity leadership compressed into 48 hours is the leader’s mid-competition work. Four things, repeated.

Presiding over enumeration — right after the start, fix the full problem list and first assignments within 30 minutes. Early drift delays the team’s first solve.
Rotation orders — a 2-hour stall is the rotation signal. "Just a bit more" is a sentence that burns the whole team’s time, and a rotation order is a decision only the leader can make.
Mood operations — during losing streaks, bring an easy problem and move the scoreboard. Team morale is managed not by the total score but by "time elapsed since the last solve."
Information hub — gather scattering findings into one shared note. Late-competition solves often grow out of early-competition clues.

2-5. Formalizing the Record — The Reckoning Ends as a Document

The competition ends at the closing time, but the reckoning ends when the record is complete. The official record carries four things.

Final rank and score — including a scoreboard capture
Whether records were broken — stated against personal best / team best
Solve list — four-line records per problem (name, technique, clue, time taken)
Operations evaluation — shift-schedule compliance, the leader’s calls that hit and missed

This document becomes the final material for Step 348 — the completion retrospective — the next day. If the competition is the reckoning of this journey, this document is the reckoning of the reckoning.

3. Follow Along

3-1. Confirming the Target Competition and Back-Planning

From the season calendar, pick the one competition that is "the one." Three criteria — can the whole team give it 48 hours, does it weigh heavily toward our strength fields, and is there a past record that makes "beating it" measurable.

Target competition confirmation document (screen example):
- Competition: ____ (CTFtime link)
- Date/time: __/__ __:00 local ~ 48 hours
- Goal: team rank top __ (vs. __ last season), __ personal solves
- Growth goal: first solve in the growth-assignment field (rev)
- Back-plan: D-21 training start / D-7 new techniques forbidden / D-1 equipment check and complete rest

Note that there are two goals (a rank goal + a growth goal). Even if the rank misses, if the growth goal is achieved this competition is a success — a single goal manufactures a single failure.

3-2. Running the Training Cycle

Execute 2-2’s three-week structure. The weekly review-meeting records are this stage’s deliverable.

Training-cycle log (screen example):
[D-20] Mock CTF #1 — web rotation assignee (C) debuts as lead, 2 solves
[D-14] Weakness review — top repeated mistake from the last competition: "missed scan
       re-init" → trigger condition added to the top of playbook section 01
[D-10] Mock CTF #2 — rev growth assignee (D) lands first independent warmup rev solve
[D-7 ] New-technique freeze begins — announced in channel; violations(?) debated into
       substitution with existing tools
[D-2 ] Final condition — sleep rhythm confirmed, all-hands agreement on 23:00 bedtime

How to read it: the D-14 record is this cycle’s essence — discovering a repeated mistake and connecting the response into a playbook revision. Training’s deliverable is not points but the playbook’s diff. This is evidence that the "cycle of revision" built in Step 344 is turning.

3-3. Competing — The 48-Hour Log

On competition day, operations run as learned. Initial enumeration, engagement in score-efficiency order, rotation rules. Below is how that day looked.

Target competition log (screen example):
[00:00] Start. Full enumeration — 24 problems. Field assignments fixed in 30 minutes
[01:10] warmup web + misc solved in a row (+150). A good start
[04:00] Web rotation lead (C) solves a mid-tier web — the growth assignment's first fruit
[09:00] pwn stalled 2 hours — rotation ordered. B steps off, supports crypto
[12:00] Rotation meeting — mid-field on the scoreboard. Goal reconfirmed: hold top __
[18:00] Rev growth assignee (D) lands a first finals-grade rev solve — all-hands celebration (rule 1)
[26:00] Late-night stretch. One member on duty per the shift schedule — no gap confirmed
[34:00] 4-hour losing streak — recovered an easy misc first, restarted the scoreboard (mood operations)
[41:00] Final spurt — web chain completed; the competition's highest-point problem solved
[48:00] End. Final record fixed — on to 3-4 below

How to read it: the points in this log where the leader’s hand shows are 09:00 (the rotation order) and 34:00 (mood operations). Neither is a record of "having solved a problem" — both are records of "making the team solve." And the 18:00 celebration — the moment the growth assignment bore fruit in battle, the point where Step 346’s design was proven.

3-4. Right After the End — The Official Record

Fix the record within one hour of the end. Binding the numbers while memory is vivid decides the retrospective’s quality.

Official record (screen example):
- Competition: ____ / end time: __/__ __:00 local
- Final: __th place / __,___ points (scoreboard capture: scores/final.png)
- Records: team best rank renewed (__th → __th) ✅
           personal best solves tied (__) — renewal failed, a best-effort record
- Solve list: warmup web, warmup misc, web (mid), web (high), rev (D's first), crypto ×2, misc ×3 — __ total solves
- Growth goal: first finals-grade rev solve achieved ✅
- Operations evaluation: shift compliance 100%, leader calls — 09:00 rotation on target, 1 misjudgment in the 26:00 placement (details: )

Whether the record was broken or not, this document’s format is the same — because "the best-effort result and its analysis" is the record’s completion condition.

3-5. Handing Off the Reckoning — To Step 348

The last act is the handoff. Bundle this competition’s records as reckoning material for the whole journey.

Handoff list (screen example):
- Official record document → to the retrospective-materials folder
- Competition log (3-3) → turning-point candidates (D's first solve, the 41:00 chain)
- The 1 misjudgment in the operations evaluation → a revision candidate for team operations plan v2.1
- Attempt history on unsolved problems → material for next season's new-technique analysis

Once you’re here, the competition is truly over. And ahead of you, exactly one Step remains — the work of looking back.

4. Missions & Exercises

Mission — Complete the Target Competition and Challenge the Record

Confirm the target competition by the three criteria (schedule, field weighting, past record) and build the back-plan
Complete the 3-week training cycle (focus → review → condition) with weekly review meetings
Complete the final-check checklist (placement, rules, equipment, library, channel, sleep) the day before
Complete the 48 hours per the shift schedule, performing the leader’s rotation orders, mood operations, and information hub
Complete the official record within one hour of the end, and prepare Step 348’s material with the handoff list

Exercises

Exercise 1. Explain why the reckoning competition’s preparation philosophy is "pulling out everything you have" rather than "stacking new things," together with the D-7 new-technique freeze rule.

Exercise 2. Explain the sentence "the training cycle’s deliverable is not points but the playbook’s diff" through the D-14 case in 3-2.

Exercise 3. Explain why goals are set as a pair — a rank goal and a growth goal — unpacking the sentence "a single goal manufactures a single failure."

Exercise 4. Explain why 3-3’s 34:00 "recovering an easy problem during a losing streak" can be a loss in score efficiency yet is still the leader’s right answer, from the perspective of the team-morale management metric.

5. Model Answers & Completion Criteria

Mission Model Answer

3-1 through 3-5 are the answer: confirmation document (with back-plan) → 3-week cycle log → day-before checklist → 48-hour log → official record → handoff list.

How to verify: ① Is the goal a pair of rank + growth? ② Does the cycle log contain a discovery connected to a playbook revision? ③ Were all six checklist items checked? ④ Does the competition log carry the leader’s calls (rotation, mood) with timestamps? ⑤ Is record-renewal status stated in the official record, success or failure regardless? ⑥ Is the attempt history of unsolved problems preserved?

Exercise Answers

Answer 1. A 48-hour competition’s result is made by the structure of the 3 weeks before it, not the 48 hours before it, and adding a new technique in the final week mixes an unverified tool into the library, shaking trust mid-battle — time leaks away deciding "did this work before?" (same as Step 272’s unverified-command problem). The D-7 new-technique freeze is a device that freezes the library, creating the conditions where "the skill you have now" is fully expressed. New things can be learned after the competition — only the verified takes the reckoning’s stage.

Answer 2. What D-14 discovered was the repeated mistake "missed scan re-init," and the response was a revision adding a trigger condition to the top of playbook section 01. A mock CTF’s score means nothing at the next competition, but this diff works in every engagement going forward. Training is not an end in itself but a device that exposes mistakes safely, and training completes only when the exposed mistake connects to a playbook revision — Step 344’s revision cycle turning inside the training cycle.

Answer 3. If the goal is rank alone, the competition’s outcome variables (problem-field distribution, top teams’ condition) sit outside our control, so even a best effort can leave only "failure" — and that failure erodes the team’s next-season motivation. A growth goal (e.g., first rev solve) is a controllable variable, so even if the rank misses, grounds remain to confirm the season’s design was right. Setting goals as a pair is not the technique of lowering goals — it’s the technique of adding measurement axes to guarantee the competition’s harvest.

Answer 4. Team morale is a function not of total score but of "time elapsed since the last solve." As a losing streak lengthens, each member falls into an isolation like "I’m the only one not solving," and isolation reduces the number of attempts itself — the true cause of points not coming. Recovering an easy problem resets that elapsed time to zero; even if immediate score efficiency drops, it restores the team’s total attempt volume for the next four hours. The leader is the person optimizing not one problem’s points but the whole team’s expected points per hour.

Completion Criteria Checklist

[ ] I confirmed the target competition and built the back-plan (D-21/D-7/D-1)
[ ] I completed the 3-week training cycle with weekly review meetings
[ ] I have a record of connecting a training discovery to a playbook revision
[ ] I completed the six final-check items the day before the competition
[ ] I completed the 48 hours per the shift schedule
[ ] As leader, I performed rotation orders, mood operations, and the information hub, and left them in the log
[ ] I completed the official record (rank, record-renewal status, solve list, operations evaluation) within one hour of the end
[ ] Mission: I preserved the attempt history of unsolved problems and completed the handoff list

6. Common Pitfalls & Fixes

Wall 1. I’m crushed under the pressure of the name "reckoning"

Symptom: the closer the competition gets, the more your usual skill won’t come out. Your hands go stiff.

Cause: you framed this competition as "the end" — the whole journey feels like it’s being graded by one event.

Fix: fix the frame — this competition is not an end but a milestone. Security is not a game that ends with one competition; training continues next week, and you have already become someone who can keep going. And look again at 3-1’s growth goal — rank is outside your control, but the growth goal is inside it. Putting your eyes on the controllable is the straight road of pressure management.

Wall 2. Equipment acts up in the competition’s first hour

Symptom: 20 minutes in, the VM won’t boot or the VPN won’t connect.

(screen example)
VBoxManage: error: The virtual machine ... has terminated unexpectedly

Cause: you skipped the "tool launch tests" in the day-before check, or an update/config change slipped in between the check and the competition.

Fix: on the day — the leader immediately reassigns that member’s problems to the deputy and runs recovery in parallel (enumeration must not stop). From next time — harden the checklist’s equipment item to "launch tests the evening before + no config changes afterward." The "just one update" right before a competition is nearly all of this wall.

Wall 3. As the strong one, I can’t let go of a problem

Symptom: you notice you’ve been staring at the same problem for 4 hours. You broke the rotation rule yourself.

Cause: the temptation of "just a bit more" comes to leaders too — more strongly, in fact, to the strong, who feel they can solve it.

Fix: put into the rules that the leader’s rotation is ordered not by themselves but by the deputy — "everyone including the leader rotates after a 2-hour stall; enforcement belongs to the next person on duty." The moment the leader is the rule’s exception, the rule becomes decoration. And leave your attempt history in the shared note where you step off — the last way to make the 4 hours you were holding into the team’s asset.

Wall 4. We missed the goal badly — the team’s mood has sunk

Symptom: after the end, the channel is quiet. Nobody brings up the retrospective.

Cause: silence right after a defeat is a normal reaction — the problem is silence extending into skipping the retrospective.

Fix: the motivation-management rules (Step 346) exist for this moment — the retrospective happens within 48 hours regardless of results. But let the leader set its first sentence — "first, well done; and this record is next season’s starting point." Then fill in the official record’s "best-effort result and its analysis" together. Once analysis begins, the silence breaks — the way a team endures defeat is not forgetting but dissecting.

Wall 5. We won (or hit the goal) and I feel strangely empty

Symptom: you broke the record, but the joy is short and an emptiness arrives.

Cause: the journey’s final goal has disappeared — goal loss comes even after success.

Fix: it’s normal, and the prescription for this feeling is exactly the next Step. In Step 348 you’ll look back on this journey and design the next one — new goals are made there. Today, just celebrate. Remember the team rules’ first item was "official celebration of achievements" — that rule applies to the leader too.

7. Summary

Today’s Concepts

Concept	One-line explanation
The reckoning competition’s philosophy	Not a day of stacking new things — a day of pulling out everything you have
The 3-week training cycle	Focused training → weakness review → condition management — D-7 new-technique freeze
The final check	Placement, rules, equipment, library, channel, sleep — preventing operations defeats
The leader’s mid-competition roles	Presiding over enumeration · rotation orders · mood operations · information hub
The pair of goals	Rank goal (outside control) + growth goal (inside control) — guaranteeing the harvest
The official record	Rank, record-renewal status, solve list, operations evaluation — the reckoning of the reckoning

Today’s Deliverables & Procedures

Deliverable/procedure	What it does
Target competition confirmation document	The back-plan and the pair of goals
Training-cycle log	Weekly reviews + records of connections to playbook diffs
Final-check checklist	The six items of the evening before
48-hour competition log	Time-axis record — including the coordinates of the leader’s calls
Official record document	Scoreboard capture and record-renewal status
Handoff list	The four things passed on as Step 348’s material

The Core Instinct

The day you first opened PowerShell, you learned to read the path in the prompt — "where am I right now." Today’s scoreboard is the same question. Written there is the position your 348-step journey has delivered you to. Whether that number is bigger or smaller than hoped, it is not an arrival but a coordinate — the next journey departs from this coordinate.

And look at the log again. Inside it are the traces of all 348 Steps — Step 1’s prompt, the trembling of the first shell, the first competition’s zero-solve stretch, the playbook’s revisions, the team’s growth. Today’s 48 hours were the union of all those days. Well fought. Now — it’s time to look back.

Once every box is checked, Step 347 is complete.