← All Workshops

HAACC WORKSHOP CONTRACT / Software

Launch Window 001

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

Status
Preflight
Track
Software
Timing
Dates TBD / UTC
Participation
Interest only; registration is not open
Sponsor
None announced

Dates are not set. Any future schedule will be published in UTC with local-time guidance before registration opens.

Email an expression of interest This email does not register you, reserve a seat, create an account, or imply selection.

01 / FIT

Who this is for

  • A solo participant or team of up to three people willing to make one small result understandable.
  • Someone who can set aside focused build time after the dates are announced and can document what failed.
  • A participant willing to disclose AI use, source licenses, known limits, and the exact submitted version.

Who this is not for

  • Anyone seeking automatic execution or a safety endorsement for an unfamiliar repository.
  • Projects whose main strategy is collecting Stars, likes, reposts, or votes.
  • Work that cannot show its sources, license position, or a result another reviewer can inspect.

Eligibility before opening

  • Participants must be at least 18 for the first pilot; this rule will be reviewed before a later youth track.
  • The project must identify its source project or declare that it is original work.
  • The submitted result must remain inspectable through the review period; private materials require a separate review path.

02 / PREPARE

Preparation checklist

  1. 01

    Choose one visible result

    Write one sentence describing who will see what after the build. A technology name is not an outcome.

  2. 02

    Select a permitted source

    Record the source URL, exact revision, license, attribution, and any unresolved rights question.

  3. 03

    Prepare a clean workspace

    Remove secrets and personal paths, use test data, and do not give unfamiliar code access to valuable accounts or files.

  4. 04

    Define proof before building

    Decide what screenshot, demo, test, or observation would prove the result, and what would show it failed.

03 / PROCESS

How the Workshop will run

  1. 01

    Register interest

    The current email is a planning signal only. It does not reserve a seat or create an account.

  2. 02

    Confirm the brief

    Freeze the user, visible result, source revision, proof plan, known risk, and help needed before the build window.

  3. 03

    Build and keep a log

    Keep decisions, failures, AI assistance, source changes, and tests visible instead of polishing away uncertainty.

  4. 04

    Freeze the submitted version

    The deadline record will bind the demo, repository revision or file digest, claims, evidence, and declared limits.

  5. 05

    Independent review and appeal

    At least two eligible reviewers assess major awards, declare conflicts, and record reasons before the appeal window closes.

04 / OUTPUT

What must be delivered

01

Required

An inspectable result

A live link, installable package, or reviewable local artifact with a clear access path.

02

Required

60-120 second demonstration

Show the intended user completing the main outcome without hiding loading, errors, or manual intervention.

03

Required

Plain-language project note

State the user, result, setup, source and license, one supported claim, and one known limitation.

04

Required

AI use statement

List the tools used, what they produced, what a person checked, and any unverified output that remains.

05

Required

Failure and decision log

A concise record of what broke, what changed, and what still needs testing.

05 / REVIEW

Judging criteria

Weights total 100. Popularity and sponsor interest are excluded.

30

Outcome clarity

Can the intended user understand the promise and complete the main path?

points
30

Verifiable evidence

Do the submitted artifact, demonstration, and tests support the central claim?

points
20

Meaningful adaptation

Does the work solve a distinct user problem rather than only reskinning a source project?

points
20

Honest boundaries

Are sources, AI assistance, failures, unknowns, safety limits, and rights stated without exaggeration?

points

Integrity rules

  • Rules and judging weights will be frozen before registration opens; later corrections will be versioned and visibly logged.
  • Stars, likes, reposts, traffic, and sponsor purchasing interest do not affect judging.
  • Reviewers must disclose conflicts and recuse themselves from affected submissions.
  • A published result describes the reviewed scope; it is not a security certification or a promise of current installability.

06 / AI + RIGHTS

AI use

AllowedDisclosure required
  • AI may assist research, coding, design, testing, writing, and translation, but the participant remains responsible for the submission.
  • The submission must name AI tools, describe their role, and separate human checks from unverified output.
  • AI does not make the final rights, safety, eligibility, or judging decision.

IP, consent, and appeal

  • Creators retain their project IP. Participation does not transfer ownership to HAACC, a reviewer, or a future sponsor.
  • Public display, commercial licensing, and sponsor contact are three separate decisions. Declining one does not invalidate the submission.
  • A submission may only include material the participant owns or is allowed to use, with required attribution and notices preserved.
Appeal path

Before results are finalized, a participant may request a written review of eligibility, conflict, rights, or scoring through the HAACC contact address.

07 / GOVERNANCE

Sponsor firewall

Contribution
No sponsor, prize, or funded service has been announced.
Challenge control
No outside organization currently controls the challenge statement.
Judging
No sponsor judge has been appointed. Any future relationship and conflict will be disclosed before rules are frozen.
Participant data
No participant data is shared with a sponsor. A future sponsor cannot receive identifiable data without itemized consent.
Direct contact
Sponsor contact, if introduced later, requires a separate participant opt-in.

08 / SAFETY

Safety boundary

Classification
Unknown software remains untrusted

  • Unknown repositories are untrusted. HAACC does not execute arbitrary submissions or certify them as safe.
  • Do not place API keys, passwords, private data, personal file paths, or valuable accounts in the build environment.
  • Any future runnable review must use a disposable environment with no secrets, no host mounts, least privilege, resource limits, and restricted network access.

NEXT STEP

Interest is not registration

HAACC will publish dates, named operating roles, final rules, capacity, and any sponsor relationship before registration can open.

Email an expression of interest This email does not register you, reserve a seat, create an account, or imply selection.