HAACC WORKSHOP / PUBLIC PREFLIGHT

A deadline should create evidence not noise

HAACC Workshops turn an understandable Guide into a bounded public build. Dates, judges, sponsors, capacity, and registration stay unannounced until the people and rules required to run them are real.

Read the proposed pilots

01 / Proposed pilots

These are public event contracts under design, not open registrations.

01
PreflightSoftware

Launch Window 001

Start from one understandable open project, then ship a version another ordinary person can see, try, and question.

Timing
Dates TBD / UTC
Participation
Interest only; no seat reserved
Sponsor
None announced
Primary output
An inspectable result
Read preflight contract
02
PreflightLow-risk hardware

Hardware Foundry 001

Turn a low-risk hardware idea into an inspectable feasibility, cost, safety, and manufacturing-readiness case before anyone is asked to scale it.

Timing
Dates TBD / UTC
Participation
Interest only; no seat reserved
Sponsor
None announced
Primary output
Use-case and system brief
Read preflight contract

02 / PREFLIGHT

What preflight means

A public preflight lets potential participants inspect the event before HAACC asks for commitment. It also prevents an attractive page from pretending that operations already exist.

  1. 01

    No invented date, capacity, prize, sponsor, judge, or registration count.

  2. 02

    Rules and scoring freeze before registration opens; changes remain versioned.

  3. 03

    AI use is allowed and disclosed. Rights, safety, eligibility, and judging remain human decisions.

  4. 04

    Stars, likes, reposts, traffic, and sponsor interest never determine results.

03 / WORKS

Every result returns as evidence

A completed Workshop should produce inspectable Works: what ran, what failed, what was checked, what remains unknown, and what help is needed next.

See public Works