Step 302. ★ CTF #12: The Goal-Attainment Competition — Top 30%, Season Finale

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

Prerequisites: the qualifier final strategy document fixed in Step 300, and the battle pack completed in Step 301. This chapter is Level 3’s graduation exam.

What you need: the battle pack, the strategy document, the extended log form — and your usual routine. The competition scenes in this chapter are marked as screen examples.
Caution: the pressure of "the last competition" will come. The remedy is one — your usual routine, exactly. Competition-day you is the average of your training.
⚠️ 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 before starting.

The twelfth competition. The screen that made your palms sweat at the first competition in Step 279 is today a familiar work screen. This competition is Level 3’s finale and graduation exam — the goal is top 30%. The current skill built by eleven competitions of debriefs and boot camps, speed training and sealing, gets measured exactly as it is.

And one thing said in advance. This chapter prepares both the attainment scenario and the shortfall scenario. Top 30% is a goal, not a graduation condition — knowing how to measure growth regardless of the result is half of this chapter. Set the clock. The final round.

1. Learning Objectives

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

Execute the fixed strategy as-is, without experiments — blocking the temptation to modify strategy mid-competition
Run the battle pack at full operation, converting what you know into points through accuracy
Perform mid-competition checkpoints every 4 hours (ranking, progress vs. goal) and adjust
Fix the final ranking, per-field score, and goal attainment in the results form after the end
Measure growth with the designated retrospective frame whether the outcome is attainment or shortfall

2. Background Knowledge — Today’s Tools and Concepts

Today’s Tools at a Glance

Category	Details
Language/environment	A CTFtime weekend competition, the battle pack (Step 301), the strategy document (Step 300), the team channel
Today’s commands	No new commands — use only what’s inside the battle pack
Concepts needed	Strategy execution (no experiments), the checkpoint cadence, separating results from process, growth metrics, the average of training
Today’s deliverable	Completed competition log + final results form + retrospective document (attainment or gap analysis)

2-1. Why No Experiments — Keeping What Was Fixed Is the Last Training

Temptation comes mid-competition. "This problem would be fast with that technique I just saw." But an unverified technique’s expected value is often negative — and above all, today the strategy itself is the subject under test. Run while changing the strategy and, whatever the result, you’ll never know whether it was the strategy or the skill.

The document fixed with grounds in Step 300 gets executed as-is today. If it works, the strategy is proven; if not, data remains about which clause collapsed. Either way it becomes next season’s asset — experiments mix the two together.

2-2. The 4-Hour Checkpoint — The Habit of Looking Far

Expand Step 299’s 3-hour reassessment to competition scale. Every 4 hours, for 10 minutes, answer three questions.

Ranking: the current rank and the score gap to the goal line (top 30%)?
Progress: which phase are you in versus the budget table — is low-point recovery done?
Adjustment: what action has the largest expected point value in the remaining time?

Screen example (checkpoint log):

[Checkpoint 1 — competition 4:00] (screen example)
Ranking: 118th of 412 teams (top 29% borderline) — need +150 pts to the 30% line
Progress: low points 5/6 recovered, 20 min behind the budget table
Adjustment: the unrecovered low-point problem goes next; high-point Pwn held until checkpoint 2

How to read it: a checkpoint is not a ranking check but a redesign of the next 4 hours. Don’t rejoice or despair over the rank; close the checkpoint by fixing "the one next action." And remember — in a dynamically scored competition, the ranking shakes every time problems open and get solved. Read 4-hour-interval numbers as trends only.

2-3. Separating Results from Growth — Two Scorecards

This competition has two scorecards.

Scorecard	Contents	Nature
Results	Final ranking, top-30% attainment or not	Subject to luck and posing trends
Growth	The trajectory of 12 competitions — scores, solves, debrief completion rate, Write-up accumulation	Must trend upward over time

The results card is one round’s number; the growth card is twelve rounds’ trajectory. Attain top 30% with a stagnant growth card and next season is precarious; miss it with a rising growth card and that 30% is a matter of time. This chapter’s retrospective always reads both cards together — read only one and you misjudge either way.

2-4. The Physics of Pressure — The Usual Routine Is the Answer

The weight of "the last competition" shallows the breath and speeds the hands (makes them hasty). The countermeasure is physics, not willpower — executing exactly the start routine, meal times, and 10-second submit routine rehearsed in Step 300. When the body moves as usual, the mind follows.

And write this sentence on the log’s first line — "Competition-day me is the average of my training." A heart hoping for miracles makes mistakes; a heart trusting the average keeps the average. Twelve competitions’ average is already a solid number.

3. Follow Along

3-1. The Eve and the Morning — A Rerun of the Rehearsal

The evening before, re-run Step 300’s three-axis checklist — with the battle pack complete, it takes 30 minutes this time. Sleep early. On the morning, perform the start routine in the same order as the rehearsal, join the channel, and verbally confirm roles.

[Day-of start routine] (screen example)
-2:00  wake, meal, desk setup (same as rehearsal)
-0:30  gather in channel, verbal role confirmation: "I'm Web first; if stuck, one-line share"
-0:10  open the log form, today's sentence on the first line: "Competition-day me is the average of my training"
 0:00  full sweep begins

3-2. During the Competition — Executing the Strategy and the Checkpoints

20-minute full sweep, all low points, per-problem caps, 4-hour checkpoints — all exactly as fixed in Steps 299–300. Today’s single added item is restricting scoreboard checks to the checkpoints. Refreshing the ranking constantly raises no scores — only heart rates.

The order when stuck is also per the strategy document — check the cheat-sheet procedure → share a one-line status in the channel → switch to hold at the cap. If you catch yourself searching outside the battle pack, that’s a signal of haste. Stop and drink a glass of water.

3-3. The End — Fixing the Results

When the end is declared, hands off, and fix the results in the form. Fixing is recording, not conversation. Screen example:

[CTF #12 final results] (screen example)
Teams: 438   Final rank: 121st   Top 27.6%   Goal (top 30%) attained
Total score: 2000 pts   Solved: 8 problems   Wrong submissions: 4
By field: Web 600/800  Pwn 400/600  Rev 400/400  Crypto 200/500  Forensics 400/400
Checkpoints observed: 2/2   Strategy deviations: 0 (or N — record clause numbers if deviated)

How to read it: the last two lines are this chapter’s unique items. Were checkpoints done by the rules; how many strategy deviations occurred — this is "strategy execution power," the real variable this competition set out to measure. The ranking is made by posing trends, but these two lines are made entirely by you.

3-4. Scenario A — The Attainment Retrospective

If you landed inside the top 30%, the retrospective’s first question is not "what went well" but "which clauses worked." Screen example:

[Retrospective A — attained] (screen example)
Result: top 27.6% — goal attained
Clauses that worked: ① low-point full sweep (recovery 5/6, avg 22 min — training average reproduced)
                     ② declaring problem names before starting (duplicate starts 0 — down 2 from #11)
                     ③ the 10-second submit routine (4 wrong — half the season average)
Luck factor: Forensics 400/400 was lucky posing (exactly inside cheat-sheet range)
Growth card: score trajectory #10 1400 -> #11 1700 -> #12 2000 — uptrend confirmed
Next season's homework: Crypto score rate 40% — the only field below 50%

How to read it: always write the "luck factor" line. Only by admitting that part of the attainment was luck can you build a plan that doesn’t collapse when that luck is absent next competition. An attainment retrospective that ends in celebration alone leaves no data behind.

3-5. Scenario B — The Shortfall Gap Analysis

If you missed the 30%, the retrospective is not emotional processing but decomposing the gap. Split the point difference from the goal line into three branches.

[Retrospective B — missed] (screen example)
Result: top 34% — 210 pts short of the goal line
Gap decomposition:
  ① execution loss — gripped a held Crypto problem to the end (-~120 pts equivalent)
     -> clause violated: per-problem 90-min cap exceeded (1 deviation)
  ② skill limit — the high-point Rev problem lacked knowledge, not time
     -> moved to next season's learning tasks
  ③ luck/trends — our main fields' posing share was below the season average (uncontrollable)
Growth card: rank missed, but score and solves are season highs — trajectory rising
Verdict: ① immediately fixable, ② a task, ③ accepted. Next competition's goal maintained.

How to read it: this decomposition turns a miss from "defeat" into "report." ① has a prescription of rule-keeping training, ② of learning, ③ of acceptance — three gaps with three different prescriptions, and mixed together they leave only the crushed self-blame of "not enough." And look at the growth-card line — if a miss is also a season-high score, that’s not regression but the goal having run ahead.

3-6. The Team Celebration Retrospective — Closing Twelve Competitions

The last step is a ritual, not analysis. The team gathers and skims twelve competitions’ logs from the start. Each person names one "moment that changed me," and the next season’s first competition goes on the calendar.

[Celebration retrospective memo] (screen example)
- First competition (#1) score 300 -> last (#12) 2000
- The competition that made us a team: #3 (first role division)
- The most painful competition: #6 (mid-evaluation, barely top 50%)
- The most growth competition: #9 (first entry into the top-30% zone)
- Next season's first competition: in 3 weeks — each member completes Step 303's comprehensive evaluation before then

How to read it: this gathering’s purpose is the feeling of closure. If a team that ran twelve rounds together doesn’t declare "it’s over" together, the season ends blurrily in each person’s head and the retrospective never gets written. Growth on paper and closure in the heart — both are today’s deliverables.

4. Missions & Exercises

Mission — Complete CTF #12 and Its Retrospective

Execute the eve inspection and the day-of start routine per the rehearsal, and write today’s sentence on the log’s first line.
Execute the fixed strategy without deviations — if one occurs, record the clause number and reason.
Perform the 4-hour checkpoints and leave each checkpoint’s "one next action" in the log.
Complete 3-3’s results form after the end — ranking, per-field score, checkpoints observed, strategy deviations.
Write the retrospective document in the scenario A (attained) or B (missed) frame, and hold the team celebration retrospective.

Exercises

Exercise 1. From a "measurement" perspective, explain why experimenting with new techniques mid-competition is forbidden.

Exercise 2. Why must the ranking at checkpoints be read only as a "trend"? Connect your answer to dynamic scoring.

Exercise 3. Using the case of "a miss that is also a season-high score," explain why the results card and growth card must be read separately.

Exercise 4. In scenario B’s gap decomposition, why bother writing ③ (luck/trends) at all? What error arises if you omit it?

5. Model Answers & Completion Criteria

Mission Model Answer

Check against these verification criteria.

Fidelity of execution: are 2/2 checkpoints and 0 strategy deviations (or recorded reasons for deviations) left in the log? This line comes before the ranking — this competition’s first exam subject is execution power.
Results form completeness: are per-field scores written against their maximums, with checkpoints observed and deviation counts included?
Retrospective structure: if attained, does it have "clauses that worked" and "luck factor"; if missed, the three-branch gap decomposition (execution/skill/luck)? A retrospective of impressions alone is unfinished.
Growth card included: in either scenario, does the retrospective document include the 12-competition trajectory (scores or solves)?
Celebration retrospective held: did the team gather and close the season — is next season’s first competition on the calendar?

Exercise Answers

Answer 1. Because this competition is a test measuring the strategy’s validity. Insert a variable (new technique) midway and the result’s cause can no longer be attributed to strategy versus experiment — success or failure, it becomes data you can learn nothing from. Experiments belong to boot-camp time; a competition is time for executing and measuring what was fixed. Mix the two and the measurement dies.

Answer 2. In dynamic scoring, other teams’ solves change point values in real time, so the ranking moves even while you do nothing. In other words, a point-in-time ranking has a large admixture of external factors that aren’t your actions. So read the ranking only as a 4-hour-interval trend, and limit the checkpoint’s deliverable to "the one next action," not ranking interpretation.

Answer 3. Read only the results card and "miss = failure" follows, but if the growth card shows a season-high score, that reading is wrong — skill rose while the goal line rose faster, or posing trends were unfavorable, and overhauling the strategy in that state is the worst misjudgment. The reverse also distorts: good results with stagnant growth. The two cards are a cross-validation device that blocks each other’s misreadings.

Answer 4. Without ③, you’d mistake uncontrollable losses for ① or ② — modifying a perfectly good strategy or planning unnecessary self-blame learning. Writing the luck item explicitly is not excuse-making — it is the procedure that separates fixable gaps (①②) from variance to be accepted (③), so next season’s effort lands in the right place. What’s written under ③ is not a target of next season’s plan.

Completion Criteria Checklist

[ ] I executed the eve inspection and day-of start routine per the rehearsal
[ ] I started with "Competition-day me is the average of my training" on the log’s first line
[ ] I performed the 4-hour checkpoints twice and recorded each one’s "next action"
[ ] 0 strategy deviations, or deviations recorded with clause numbers and reasons
[ ] I completed the final results form (ranking, per-field score, checkpoints observed, deviations)
[ ] I wrote the retrospective document in the attainment/shortfall frame that matches the result
[ ] The retrospective includes the growth card of the 12-competition trajectory
[ ] I held the team celebration retrospective and put next season’s first competition on the calendar

6. Common Pitfalls & Fixes

Wall 1. My hands are shaking before it even starts

Symptom: the thought of "the last competition" makes you unlike your usual self.

Cause: pressure is a normal physiological response — you don’t eliminate it, you pass through it.

Fix: trust the routine. Mechanically execute the start routine’s first motions (desk setup, open the log form, write today’s sentence), and by the 20-minute full sweep your hands are already your usual hands. The body goes first and the mind follows — that’s what the rehearsal (Step 300) was for.

Wall 2. The checkpoint shows me far from the goal and my mentality shakes

Symptom: at 4 hours, top 45% — 30% looks far away.

Cause: the first-half ranking is not a predictor of the second half. If your strategy solves high-point problems late, the first-half ranking comes out low by design.

Fix: return to the checkpoint’s three questions — what you need is only "the one next action." And check the log. Are you behind the budget table, or on-strategy with points not yet stacked? If the latter, trust the planned second half and proceed — trusting the plan is also trained execution.

Wall 3. After a strategy deviation, I self-blame and chain mistakes

Symptom: you realize you blew past a cap, and trying to make it up, you spray wrong answers on the next problem.

Cause: a deviation’s cost is bigger in the haste that follows it than in the deviation itself.

Fix: record the deviation and let it flow away — the moment you write the clause number and reason in the log, the event becomes retrospective material and exits the current game. "Points already spilled get recovered in the retrospective" — move to the next problem on that one sentence.

Wall 4. I grabbed a new problem in a rush right before the end

Symptom: with 30 minutes left, the "one more problem" temptation.

Cause: the wrap-up phase’s task is not new points but finishing the points secured — submitting unsubmitted flags, re-verifying formats.

Fix: look again at the budget table’s wrap-up phase (Step 299) — the clause "no starting new problems" is already there. A rushed last-minute start succeeds far less often than a solved problem’s flag typo gets missed. The final 30 minutes’ contest is not offense but inspection.

Wall 5. The result missed the goal and I don’t want to write the retrospective

Symptom: you don’t want to look at the log again, and you want to postpone the retrospective.

Cause: the emotion is normal — but the retrospective is not something done after the emotion settles; it is a process performed regardless of emotion.

Fix: use the 24-hour rule — rest a day, then at exactly the same time the next day, open scenario B’s form. Having a form is the salvation of this moment — the gap decomposition handles numbers, not emotion, from the first line you write. And at the growth-card line, the twelve competitions’ trajectory will stand you back up.

7. Summary

Today’s Concepts

Concept	One-line explanation
Strategy execution (no experiments)	A competition is time for measuring what was fixed — insert a variable and the data dies
4-hour checkpoint	The three questions of ranking/progress/adjustment — the deliverable is "the one next action"
Results card & growth card	One round’s number and twelve rounds’ trajectory — read both to avoid misjudgment
Gap decomposition	Split a miss into execution/skill/luck — each has a different prescription
Declaring the luck factor	Admitting the luck inside an attainment keeps the next plan solid
The average of training	Competition-day me is the average of my training — trust routine, not miracles

Today’s Tools & Forms

Tool/form	What it does
Start-routine check	The device for passing through pressure by the body’s sequence
Checkpoint log	The 4-hour-interval redesign record
Final results form	Fixing ranking, per-field score, checkpoints observed, deviations
Retrospective frame A/B	Clause analysis for attainment / gap decomposition for shortfall
Celebration retrospective	The ritual of closing the season together — through next season’s first competition

The Core Instinct

The twelfth competition is over. Whichever way the result went, you are now someone who doesn’t just "sit" competitions but "operates" them — capable of running the full cycle of setting a strategy, executing it, measuring it, and decomposing it. That cycle is a skill that outlasts any single technique.

Rest a while. The season’s comprehensive evaluation begins by spreading this competition’s results form and twelve competitions’ logs across the desk — today’s records are that evaluation’s raw material.

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