Step 300. ★ CTF #11: Qualifier Dress Rehearsal — A Rehearsal Validated at 80% Power

Level 3 — Real-World CTF & Advanced Offensive Skills | Difficulty ★★★★☆ | Estimated time: 2 days (competition participation + post-competition tactics meeting)

Prerequisites: the order strategy and decision rules fixed in Step 299’s 10-problem time attack. This chapter runs the last overseas competition before the qualifier as the "final rehearsal."

What you need: one weekend competition registered on CTFtime, Step 299’s time budget table and decision rules, and an equipment/network/document inspection checklist. The competition scenes in this chapter are marked as screen examples.
Caution: this competition’s goal is not ranking but validation. Run at 80% power, and inspect everything about qualifier day in definitive form, not future tense.
⚠️ 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, etc.) before starting.

Suppose the qualifier is ten days away. Raising your skill by then is nearly impossible — but the rate at which your skill converts into points can still go up substantially. The device for that is today’s competition — the last overseas competition run under the qualifier’s rules, used as a final rehearsal of every sector from equipment to communication.

The rehearsal’s deliverable is not points but documents. Using the data collected in this competition to fix qualifier day’s problem-selection order, time allocation, and team operations — that is today’s completion condition.

1. Learning Objectives

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

Operate a competition as "a simulation of the qualifier" — matching even the time slots and rest plan
Execute a final inspection checklist across the three axes of equipment/network/documents and fill its gaps
Apply Step 299’s fixed order strategy in a real competition and record its performance as data
Hold a post-competition tactics meeting to fix the qualifier final strategy document (selection order, allocation, communication)
Build a condition-management plan through the eve of the qualifier that blocks the cramming temptation

2. Background Knowledge — Today’s Tools and Concepts

Today’s Tools at a Glance

Category	Details
Language/environment	A CTFtime weekend competition, the team channel (Discord, etc.), Step 299’s log form, document tools
Today’s commands	No new commands — the inspection checklist and the strategy document are today’s tools
Concepts needed	Conditions of simulation (identical rules), the 80% principle, the three inspection axes, the tactics meeting, condition as a resource
Today’s deliverable	Inspection checklist (checked) + competition log + qualifier final strategy document + condition plan table

2-1. Why 80% — The Balance of Validation and Expenditure

A point from the source material — overexert in the competition right before and qualifier-day condition collapses. This competition is not the qualifier; it is a measuring device for the qualifier. Go all-in on the measuring device and you have no resources left for the actual game.

Concretely, 80% means this. If you usually pull an all-nighter in competitions, this time you keep the same sleep plan as the qualifier. If a problem appears featuring a technique you’d love to learn, you record it without digging deep. Even if the ranking disappoints, you don’t play overtime. Do your best, but do not spend everything — this delicate balance is this competition’s operating skill.

2-2. The Three Inspection Axes — Equipment, Network, Documents

Accidents that ruin a competition for non-skill reasons almost always occur on three axes.

Axis	Inspection items	Failure scenario
Equipment	Discord/platform account logins, VM boot, tool versions, battery/power	Burning the competition’s first 30 minutes on login trouble
Network	Bandwidth check, VPN connection test (for platform access), backup means (tethering)	Unstable connection breaking the mid-game rhythm
Documents	Latest cheat-sheet/playbook locations, log form opened, rules summary	Wasting 10 minutes unable to find the needed cheat sheet

All three share one property: skill cannot recover them. A brilliant player who spends 40 minutes on a VPN connection sees those 40 minutes of expected score evaporate. So the evening before this competition, inspect the three axes by actual operation — not "it should work" but "I ran it."

2-3. Designing the Data Records — Collecting the Basis of Qualifier Strategy

This competition’s log adds two columns to Step 299’s form — grounds for problem selection and team communication events.

Problem | Field | Points | Start | Finish | Wrong | Selection grounds | Communication event

"Selection grounds" is one phrase for why you picked that problem — full sweep priority 1, reassessment switch, teammate request, etc. "Communication event" is a moment when team operations affected the score — solved via hint share, duplicate start discovered, 30 min unreachable, etc. These two columns are the material of the post-competition tactics meeting. Record only scores and you know "what"; record grounds and events and you see "why."

2-4. The Tactics Meeting — A Competition Ends Not at the Finish but at the Meeting

Hold the team tactics meeting not right after the end but the next morning — a meeting right after an all-nighter has emotion but no accuracy. The meeting has exactly one deliverable: the qualifier final strategy document. Its table of contents is fixed in advance.

Qualifier final strategy document (table of contents)
1. Problem selection order — full-sweep criteria, priority rules
2. Time allocation — per-phase budgets, per-problem cap, reassessment points
3. Role assignments — who covers which field first
4. Communication protocol — share timing, request format, rules for when unreachable
5. Contingency plan — fallback means for equipment/network accidents

Each item is filled with evidence from this competition’s log. An evidence-free sentence ("let’s work hard") is not strategy but a slogan — all of them are deletion targets.

3. Follow Along

3-1. The Day Before — The Three-Axis Final Inspection Checklist

Once registered, run the checklist below by actual operation the evening before. Check each item not as "confirmed" but as "executed."

[Equipment]
[ ] Competition platform login -> reached the competition page
[ ] Team channel (Discord) voice/screen-share test once
[ ] Attack VM boot + snapshot state check
[ ] Run-test 3 random attack tools (nmap, burp, gdb, etc.)
[ ] Laptop power adapter + battery 100%

[Network]
[ ] Connect with the platform VPN config file -> ping a problem server
[ ] One speed test (record the baseline)
[ ] Backup means: same connection test over phone tethering

[Documents]
[ ] Latest cheat-sheet/playbook locations confirmed (shortcuts pinned)
[ ] 'Selection grounds/communication event' columns added to the Step 299 log form
[ ] Competition rules summary: duration, wrong-answer penalty, flag format, prohibitions

How to read it: if even one item on this list fails, that is this rehearsal’s first harvest — you found, with ten days still remaining, a defect that would have been a disaster on qualifier eve. Repair failed items immediately and reflect them in the qualifier checklist too.

3-2. Running the Competition — By the Qualifier’s Rules

On competition day, execute a day exactly per the qualifier plan. Screen example (operations plan table):

[Competition operations plan — qualifier-identical conditions] (screen example)
09:00 start routine (wash up/meal/desk setup — same order as qualifier day)
09:30 competition starts -> full sweep (Step 299 method, 20 min)
09:50 all-low-points phase
12:30 lunch 20 min (away — at the same time as the qualifier)
13:00 mid-reassessment -> order adjustment
17:00 dinner 20 min + stretching
17:30 remaining high-point attack
21:30 wrap-up routine — re-verify flag formats, finish unsubmitted work
22:00 end. No solving afterward — tactics meeting booked for tomorrow morning

How to read it: the key is that even meal and rest times match the qualifier. Condition rhythm is something the body remembers, so resting at different times in the rehearsal leaves that rhythm unvalidated. The "80% power" applies here too — you end at 22:00 and do not stay up all night.

3-3. During the Competition — Recording Grounds and Events

Record with the two columns attached to Step 299’s log habit. Screen example:

[Competition log excerpt] (screen example)
jwt-confusion | Web | 300 | 10:20 | 11:05 | 1 | full sweep priority 2 | asked teammate A to check alg confusion -> instant answer
heap-note     | Pwn | 400 | 11:10 |   -   | 0 | points priority 1     | switched to hold at 13:00 reassessment
backup-zip    | For | 200 | 13:10 | 13:40 | 0 | reassessment switch   | duplicate start with teammate B found -> roles confirmed

How to read it: the third line’s "duplicate start discovered" may be the most expensive data gained in this competition — an event where two people gripped the same problem and duplicated 40 minutes. This one line enters the strategy document’s item 4 (communication protocol) as the clause "declare the problem name in the channel before starting." Points vanish, but a line like this keeps earning points in the qualifier.

3-4. The Next Day — The Tactics Meeting and the Qualifier Final Strategy Document

The team gathers and fills 2-4’s table of contents. The order: ① put the log on screen and walk it together by time slot, ② extract 3 well-made decisions and 3 stuck ones, ③ fix each table-of-contents item with its evidence. Screen example (part of the document):

1. Problem selection order
   - Strict 20-min full sweep. After 'instant/ponder/hold' judgments, all low points.
   - Grounds: this competition's low-point recovery rate 100% (6/6), average 24 min/problem.
2. Time allocation
   - Per-problem cap 90 min. 120 min for Pwn (reflecting our team's average solve time).
   - Grounds: 110 min into heap-note for 0 pts — the only case of breaching the Pwn cap.
4. Communication protocol
   - Declare the problem name in the channel before starting (lesson of the 1 duplicate start).
   - Stuck 30 min -> mandatory one-line progress share in the channel.

How to read it: check that every clause has a "Grounds:" line behind it. The grounds must come from this competition’s log. Once this document is fixed, it is read-only until the qualifier — every temptation of a new strategy goes to the "next season" memo.

3-5. Until the Qualifier — The Condition-Management Plan

The last deliverable is a ten-day plan table. The principle is no excessive cramming — you’ve entered the stretch where not new knowledge but condition decides the qualifier score. Screen example:

[Qualifier D-10 to D-1 condition plan] (screen example)
D-10~D-7  light maintenance training: re-read cheat sheets + 1 known-type problem/day (for confidence)
D-6~D-3   Step 301's final reinforcement (debrief block — no new techniques)
D-2       re-run the equipment/network/documents checklist, final read-aloud of the strategy document
D-1       no training. Bed 1 hour earlier than usual. Two alarms.

How to read it: D-1’s "no training" is the hardest clause to keep. Anxiety whispers "just one more problem," but what the eve’s one problem takes away is sleep, and what sleep takes away is the entire 8 hours of focus. Share the plan table in the team channel — it becomes a device where each of you blocks the others’ cramming.

4. Missions & Exercises

Mission — Complete the Qualifier Dress Rehearsal

Pick a weekend competition on CTFtime and finish team registration — choose a format as close to the qualifier as possible (time slot, duration).
Run 3-1’s three-axis inspection checklist the day before, and repair any failed items.
Run the competition per 3-2’s operations plan and complete the log with the two added columns.
Hold the tactics meeting the next day and fix the qualifier final strategy document (5 table-of-contents items) with its grounds.
Build the D-10 condition plan table and share it in the team channel.

Exercises

Exercise 1. From a measuring device’s perspective, explain why this competition is run at "80% power."

Exercise 2. Why are accidents on the three inspection axes (equipment/network/documents) "unrecoverable by skill"?

Exercise 3. Why add the "selection grounds" and "communication event" columns to the log? What stays invisible when you record only scores?

Exercise 4. In the qualifier final strategy document, why is a clause without a "Grounds:" line a deletion target?

5. Model Answers & Completion Criteria

Mission Model Answer

Check against these verification criteria.

Fidelity of identical conditions: do meal, rest, and end times match the qualifier plan — "roughly similar" is not a simulation.
Evidence of inspection: does the three-axis list show traces of execution (including repair records)? Passing everything in one go is also normal — that is the inspection’s purpose.
The log’s two columns: are selection grounds and communication events filled in? Zero communication events may mean not "there were none" but "you didn’t see them" — ask teammates at the meeting.
Clause-grounds binding in the strategy document: do all 5 table-of-contents items carry grounds from the log?
Sharing of the condition plan: is the team looking at the same table, including the D-1 "no training" clause?

Exercise Answers

Answer 1. Because a measuring device that destroys its subject makes measurement meaningless. This competition’s purpose is validating qualifier-day operations, but running at full power accumulates fatigue and leaves qualifier day’s "me" below the training average. 80% is not laziness — it is the operating condition that simultaneously protects the validity of the validation data and qualifier-day condition.

Answer 2. Because time’s expected score evaporates regardless of skill. A 30-minute login failure and 40 minutes of VPN instability steal the same 70 minutes of opportunity from a brilliant player. Skill breaks through technical stalls, but only prior inspection blocks infrastructure accidents — which is why the three axes are validated the day before, not during the competition.

Answer 3. Because scores show only "what happened," not "why that choice was made" or "how team operations intervened in the score." The selection-grounds column becomes material for validating the strategy (order rules), and the communication-event column surfaces operational variables like duplicate starts and hint shares. Only with both does the tactics meeting become cause analysis instead of score appreciation.

Answer 4. Because a clause without grounds comes from hope, not from this competition’s data. Sentences like "let’s work hard" or "let’s focus" are not executable actions and perform no function under qualifier-day pressure. The strategy document’s value lies in the log grounds attached to each clause — without grounds, you must delete so the document becomes a manual, not a collection of slogans.

Completion Criteria Checklist

[ ] I picked a competition with a format similar to the qualifier and finished team registration
[ ] I ran the three-axis (equipment/network/documents) checklist the day before and repaired failures
[ ] I operated meal, rest, and end times identically to the qualifier plan
[ ] I completed the log including selection-grounds and communication-event columns
[ ] I fixed the qualifier final strategy document’s 5 items with grounds at the tactics meeting
[ ] I switched the strategy document to read-only and separated new strategy memos into "next season"
[ ] I built the D-10 condition plan table and shared it in the team channel

6. Common Pitfalls & Fixes

Wall 1. The competition went so well I slipped into full-sprint mode

Symptom: the ranking is rising and you want to keep solving, even all night.

Cause: the temptation of ranking is normal — but this competition’s prize is not ranking; it is a validated strategy document.

Fix: declare the end time in the team channel before starting. A public promise is stronger than private willpower. And recall — climbing 100 places in this competition adds 0 points to the qualifier, but burning your condition here subtracts from it.

Wall 2. The checklist passed everything and it felt like a formality

Symptom: a feeling of "it’s all working anyway, why bother?"

Cause: the inspection’s value isn’t only in finding failures — the certainty of "I ran it" is itself an asset that reduces qualifier-eve anxiety.

Fix: reframe the purpose. This inspection is defect hunting and simultaneously a rehearsal of the start routine. Hands that made one full lap from login to VPN the day before do not tremble on qualifier morning. Repetition that looks like formality builds the body’s routine.

Wall 3. Not a single communication event got recorded

Symptom: the communication-event column is blank.

Cause: read generously, smooth operations; read harshly, a blind spot in observation — mostly the latter. Duplicate starts, unanswered requests, mistimed shares exist in every team.

Fix: go around and ask at the tactics meeting — "one communication moment that frustrated you during the competition." Finding it in conversation, not records, is fine. Backfill discovered events into the log — the log isn’t written only during the competition; it’s completed at the meeting.

Wall 4. The strategy document became a copy of the last competition’s

Symptom: newly fixed, yet its contents match the previous strategy.

Cause: two readings are possible — the strategy has converged (good signal), or this competition’s log wasn’t truly reflected (bad signal).

Fix: the test is simple — check whether each clause’s "Grounds:" line points to this competition’s log. If it does, the strategy has converged; lock the document read-only. If it points only to old logs, you haven’t answered this competition’s questions — restart the meeting from "what changed in this competition."

Wall 5. With the qualifier approaching, I suddenly want to learn new techniques

Symptom: a new technique from a recommended post keeps catching your eye. "What if this appears in the qualifier?"

Cause: the most expensive temptation anxiety produces. As the source material warns — in a qualifier, points come from "accurate execution of what you already know."

Fix: move the new technique to a "post-qualifier" folder in your notes app and close it. A technique learned in ten days has low expected qualifier points, and what drains away in that time is the accuracy of known techniques — and sleep. Handling that temptation is a task already assigned to the final debrief block before the qualifier — leave it to that routine and close it today.

7. Summary

Today’s Concepts

Concept	One-line explanation
Conditions of simulation	Only identical time slots, rest, and end times make it validation — a similar competition is not a simulation
The 80% principle	Do your best, but do not spend everything — the measuring device must not eat the real game’s resources
The three inspection axes	Equipment/network/documents — accidents skill cannot recover get caught the day before
Selection grounds & communication events	The log’s two columns that keep the "why" of scores — the tactics meeting’s material
The tactics meeting	A competition ends not at the finish but at the next morning’s meeting
Strategy document read-only	Every new strategy after fixation goes to the "next season" memo

Today’s Tools & Forms

Tool/form	What it does
Three-axis checklist	The day-before infrastructure validation — checked by execution
Operations plan table	The rehearsal script of qualifier day’s one day
Extended log form (7 cells)	Problem, points, times, wrong + selection grounds + communication events
Qualifier final strategy document (5 sections)	Order/allocation/roles/communication/contingency — grounds on every clause
D-10 condition plan table	Blocking cramming and protecting sleep — team sharing is the device

The Core Instinct

You may forget today’s competition ranking. What must remain is three things — a checklist with no blanks, a strategy document with grounds attached, and the body’s memory that "qualifier-day me moves exactly like this day."

Having reached your eleventh competition, a competition for you is no longer an event but a process. Load the material (preparation), run it (operations), inspect (meeting), and pass it to the next process (the qualifier) — today you finished that process’s final test run.

Once every box is checked, Step 300 is complete. Click the checkbox in the sidebar to save your progress.