System State Arena — Competition Prep

Summary

Preparation for System State Arena — an invitation-only Linux systems competition testing mastery of filesystem internals, process state, networking, security enforcement, automation, and network architecture under air-gapped constraints with terminal-only access.

Objective

Place top 20 out of 100 international participants. Below 20th triggers permanent disqualification and restricted performance registry.

Competition Format

  • 3 days (Aug 22-24, 2026)

  • Phase I: Individual diagnostics (15-45 min tasks)

  • Phase II: Paired problem-solving

  • Phase III: Team-based full-environment scenario (up to 2 hours)

  • Final: Solo endurance under sustained load + live perturbations

Environment

  • Air-gapped — no internet

  • Terminal-only — no GUI

  • Editors: vim, nano only

  • References: man, info, /usr/share/doc only

  • Python: standard library only

  • All commands logged and evaluated

Scoring

Domain Weight What They’re Testing

Accuracy

40%

Correct solution — no trial-and-error

System Reasoning

25%

Explain WHY, not just HOW

Efficiency

20%

Fewest commands, fastest path

Automation

15%

Reproducible scripts, idempotent

Documentation Requirement

All work must be documented in real-time using AsciiDoc (preferred) or Markdown. Documentation is scored on clarity, accuracy, structure, and traceability. This is a built-in advantage.

Phase Summary

Phase Description Status Target

0: Assessment

Baseline skills audit across all 6 domains

❌ Not started

Week 1 (Apr 21-27)

1: Filesystem & Inodes

Inode lifecycle, links, metadata, /proc filesystem, disk anomalies

❌ Not started

Weeks 2-4 (Apr-May)

2: Process & System Calls

/proc/<pid>, strace, lsof, file descriptors, scheduling, signals

❌ Not started

Weeks 4-7 (May-Jun)

3: Networking

ss, ip, routing, socket state, interface config, troubleshooting

🟡 Partial (daily work)

Weeks 5-8 (Jun)

4: Security

AppArmor profiles, SELinux contexts/booleans, nftables, privilege boundaries

❌ Not started

Weeks 7-10 (Jun-Jul)

5: Automation

Bash strict mode, Python stdlib (os, subprocess, pathlib), idempotent ops

🟡 Partial (daily work)

Weeks 9-12 (Jul)

6: Network Architecture

Subnetting, RFC1918, NAT strategies, architectural justification

🟡 Partial (daily work)

Weeks 10-13 (Jul-Aug)

7: Integration

Full scenarios, live perturbation response, timed exercises

❌ Not started

Weeks 13-17 (Aug)

8: Man Page Mastery

Navigate man/info without internet — section numbers, cross-refs, /search

❌ Not started

Continuous (every session)

Strengths (Leverage)

  • AsciiDoc documentation system (2,954 files, partials, includes) — most competitors can’t write AsciiDoc

  • Network engineering daily (ISE, FTD/FMC, VLANs, 802.1X, subnetting)

  • Bash scripting (set -euo pipefail, traps, heredocs, error handling)

  • Text processing (grep, awk, sed, find, xargs, jq) — daily use on real data

  • Python (netapi, pandas, API integrations)

Gaps (Close)

  • Filesystem internals — inodes, /proc filesystem, stat format strings

  • Process state — strace, lsof, /proc/<pid>/fd, file descriptors, signals, scheduling

  • System calls — the kernel interface (man 2 open, man 2 read, man 2 write, man 2 fork, man 2 exec)

  • Security enforcement — AppArmor profile writing (not just status), SELinux policy, nftables (not iptables)

  • Air-gapped man navigation — section numbers (1=commands, 2=syscalls, 5=file formats, 8=admin), cross-references

Metadata

Field Value

PRJ ID

PRJ-2026-04-system-state-arena

Author

Evan Rosado

Created

2026-04-21

Last Updated

2026-04-21

Status

Active

Category

Education / Competition Prep

Priority

P0

Competition Date

August 22-24, 2026

Prep Window

123 days (2026-04-21 to 2026-08-21)

Next Review

2026-05-01

Related