Powerhouse presents

Power Game Contest — Rules

Not a game show — esports. Clock, score, declared stack, artifact proof.

Names

• Power Game Contest: one public Matchday.
• Power Game Championship: the season ladder.
• Matchday: one brief, one match clock, one primary metric.
• Powerhouse: public host brand.

Phase 1 — Free-for-all

• No classes, handicaps, or approved-tool lists.
• Bring whatever agent setup you run. Declare it, then hammer.
• Classes come only after free-for-all produces legends and footage.

Match clock

≤90′ running hammer. Stack declare (5′ max) → hammer (90′ max) → stoppage / verify (10′) → verdict (≤5′). Freeze at whistle; pointers must be public and immutable. Phase 1 has no overtime.

Score

Each Matchday publishes exactly one falsifiable primary metric. For Matchday #0: HANDOFF_P99_MS. Verified entries rank by the brief rule; unverified entries receive distance scoring; DQ is listed last.

Stack declaration

Before hammer, file STACK.yaml with competitor, agents, runtimes, models, human-in-loop limits, APIs, and repo or package. Material undeclared tooling is DQ-UNDECLARE.

Mandatory artifacts

At freeze publish CLAIM.md, REFeree.md, verify.sh (or verify.mjs), STACK.yaml, and a public immutable stranger-repeatable artifact.

DQ codes

DQ-NOARTIFACT · DQ-DECK · DQ-VERIFYFAIL · DQ-CLAIM · DQ-PRIVATE · DQ-LATE · DQ-UNDECLARE · DQ-CLOCK · DQ-CONDUCT

Enter path: waitlist → STACK prep → HAMMER on Matchday #0