# Introduction to Project Editorial Slayer

**Application for HackMD Non-profit Sponsorship**

**Contact**
> Võ Hoàng Anh (SPyofgame)
> Competitive Programming Teacher (Non-Profit)
> [e-mail]
> Ho Chi Minh City, Vietnam

## 1) Mission & Who We Serve

* We are a teacher-led program helping **high-school/undergrad students** master **competitive programming (CP)** through **structured practice, transparent analytics**, and **mentored feedback**.
* Our goal: **boost performance** (rating, problem-solving depth, implementation hygiene) while **tracking progress** responsibly using our open tools and the **OAI framework** (Observation → Abstraction → Implementation).

### What success looks like

* Students consistently **reach milestones** (next grade/rank/peak).
* **Habits** stabilize (daily/weekly streaks, healthy cadence).
* **Coverage** widens (ratings, tags, divisions), and **accuracy** rises (oneshot %, fewer late WAs/TLEs).
* Measurable **contest pacing** improvements (faster first AC, fewer penalty resubmits).

## 2) Our Approach (OAI + Statistics EXP System)

We teach with a simple mental model:

* **Observation (O):** read constraints, formats, promises; identify traps; log timelines and verdicts.
* **Abstraction (A):** map problems to models (DP/greedy/graph/NT), prove predicates/invariants, choose complexity budgets.
* **Implementation (I):** ship clean code: modular DS/IO, guard rails, local tests, stress & replay.

We pair OAI with our **stats/EXP system (“Starrank”)** that uses public OJ data (e.g., Codeforces API) to compute:

* **Milestones:** next rank/order/level, personal bests.
* **Progress:** vs yesterday/last week/month/quarter and rolling 1/7/30/91d.
* **Habits:** streaks, day-of-week cadence.
* **Coverage & Completeness:** ratings/tags/divisions/verdicts.
* **Accuracy & Diagnostics:** oneshot rate, shots/AC, per-tag hit rate, **failure timing** (sample/pretest/systest), **near-TLE/MLE** footprints.
* **Trends:** last-100 AC distribution, median/IQR, **comfort** vs current rating.
All tables render to Markdown so students can **see, reflect, and adjust** their plan weekly.

> Privacy note: We analyze **public submission data** and store only training analytics; no commercial use.

## 3) Why HackMD (and how we’ll use it)

HackMD is perfect for our **note-centric** workflow: lesson plans, shared checklists, postmortems, and weekly analytics snapshots.

### We will:

1. **Publish curricula & playbooks**

* OAI primers, tag ladders, difficulty ladders, “read-before-code” checklists.
2. **Run weekly notebooks**

* “Week N Goals,” problem sets, **progress tables** pasted as Markdown, action items per student.
3. **Standardize reflection**

* Contest/postmortem templates (root cause by O/A/I, next actions), **habit** & **accuracy** rubrics.
4. **Collect evidence**

* Links to submissions, snippets, failing seeds, delta-debug traces.
5. **Operate safely**

* Private team for minors & sensitive reflections; publish selected pedagogy as public notes.

**Why sponsorship:** We are an educational/non-profit initiative with \~\[X–Y] active students. A sponsored Prime Team lets us:

* Keep a **private workspace** (student safety & privacy) with **up to 20 members** (or more during peak season).
* Use advanced features (permissions, attachments, history) to sustain weekly operations.

## 4) Recent / Representative Programs (publicly shareable)

* **OAI Bootcamp (4 weeks):** speed hygiene → model depth → reading finesse → mixed mocks.
* **Starrank Weekly:** leaderboard + 15 tables (Highlights, Progress, Habits, Tag Peaks, L100 Trend, Failures, Accuracy…).
* **Peer Review Sprints:** students annotate each other’s O/A/I logs inside HackMD.
* **Community Sessions:** open notes on graph DP, flows, geometry hygiene, etc.

> Links (replace with your notes):
>
> * Curriculum overview: \[link]
> * Sample weekly report: \[link]
> * Contest postmortem pack: \[link]

## 5) How HackMD fits our day-to-day workflow

**Mon:** Publish “Week Plan” (targets by tag/rating, 3 focus levers).
**Tue–Thu:** Students work; append micro-tests, failing seeds, O/A/I checkpoints.
**Fri:** Auto-generate stats tables → paste into “Week Report.”
**Sat:** Review & coaching comments inline; assign next actions.
**Sun:** Publish 2 public notes (mini-lectures) to give back to the community.

## 6) Students & Impact

* **Cohorts:** \[e.g., 25 HS students, 10 freshmen], mixed levels (1200–2000+ CF).
* **Improvements (last term):** median +\[X] rating, +\[Y]% oneshot, −\[Z]% late failures, +\[K] active streak days.
* **Equity:** zero-cost instruction; loaner hardware/time for students with limited resources; open public notes.

## 7) Sponsorship Request

* **Plan:** HackMD Prime Team (private), **\[20] seats** (coaches + students).
* **Duration:** \[12 months], renewable if we meet reporting goals.
* **Why needed:** student privacy + collaborative templates; budget-constrained non-profit/club.

## 8) Compliance & References

* **Non-profit / school letter:** attached or available on request.
* **Code of conduct & privacy:** minors’ PII never published; notes exclude personal data; public notes are pedagogy-only.
* **References:** \[school/club page], \[GitHub org], \[community partner], \[CF group].

---

## Appendix A — Templates (copy for your workspace)

### A.1 OAI Sheet (per problem)

# OAI Sheet — Problem: [CF ####X]

## O — Observation
- Constraints & promises:
- Format pitfalls:
- Micro-tests (3):

## A — Abstraction
- Model(s) considered:
- Predicate / invariant:
- Complexity budget:

## I — Implementation
- Plan (≤12 lines pseudo):
- Guardrails (overflow, indexing, epsilon):
- Local tests / fuzz seeds:

### A.2 Contest Postmortem (team)

# Contest Postmortem — [Round / Date]
- Start latency: __   Penalties: __   First-AC at: __
- Pacing pivots: [when/why]
- Late failures: sample/pretest/systest counts
- Root causes by O/A/I:
  - O: ...
  - A: ...
  - I: ...
- Next-week actions (3 levers): 1) __  2) __  3) __

### A.3 Weekly Progress Note (per student)

# Week N — [Name]
- Milestones: next grade/order/level delta
- Progress: 1/7/30/91d EXP
- Habit: day/ week streaks
- Coverage: rating/tag/division
- Accuracy: oneshot %, shots/AC, per-tag hit
- Diagnostics: late75/90/99, near-TLE/MLE
- Plan: 2 comfort + 2 grow + 1 stretch problems

---

### Vietnamese summary (optional for your audience)

**Chúng tôi là giáo viên hướng dẫn lập trình thi đấu**, dùng khung **OAI (Quan sát → Trừu tượng → Cài đặt)** và hệ **thống thống kê EXP** để **nâng hiệu suất** học viên và **theo dõi tiến độ** minh bạch. HackMD giúp chúng tôi **viết giáo trình, nhật ký OAI, báo cáo tuần, postmortem** và chia sẻ công khai các ghi chú học thuật. Xin tài trợ **Prime Team riêng tư** để đảm bảo **quyền riêng tư học sinh** và vận hành ổn định (≈20 ghế).

---

#### One-line subject for the email

> **“\[Your Organization] applies for HackMD non-profit sponsorship”**

#### Attach with the email

* Proof of non-profit/educational status (PDF/image).
* This public note link.
* Short intro (who you serve, why HackMD, privacy need), and 2–3 public sample notes.