# AABW builder support request catalog

Generated: 2026-06-18T21:00:00+07:00

Common event-day requests BP should detect, route, and turn into a short action loop for solo builders, teams, hybrid participants, and organizers.

## Team or collaborator fit

- Audience: solo
- Trigger: Builder is solo, missing a role, or asking where to find a teammate.
- Route: Team formation channel, nearby mentors, or scarce-role watchlist.
- BP action: Generate a crisp teammate ask and suggest the missing role rather than more generic networking.

Checklist:
- Name the missing capability
- State current artifact
- Ask one channel or person
- Decide recruit or cut scope

## Venue, room, or hybrid confusion

- Audience: hybrid
- Trigger: Builder asks where to go, misses a venue change, or is joining remotely.
- Route: Today route card, Luma RSVP context, public schedule, and remote fallback.
- BP action: Show the current venue, next session, travel/online fallback, and what to do if they are late.

Checklist:
- Confirm today venue
- Check next workshop
- Choose in-person or remote path
- Update team status

## Workshop notes into build tasks

- Audience: team
- Trigger: Builder attends a session but leaves with notes instead of implementation tasks.
- Route: Workshop router and operating playbook.
- BP action: Convert the session into one task, one mentor question, and one Devpost update.

Checklist:
- Capture one usable API/tool
- Assign one owner
- Timebox one experiment
- Record one partner follow-up

## Credits, API keys, deployment, or stack blocker

- Audience: team
- Trigger: Messages mention quota, API key, token, deploy, cloud, broken demo, or being stuck.
- Route: Rescue plan, workshop partner, cloud mentor, or fallback demo checklist.
- BP action: Prioritize the fastest safe unblock and keep a fallback recording path alive.

Checklist:
- Identify exact failure
- Ask one precise mentor question
- Choose workaround or cut scope
- Protect demo URL/video

## Devpost and final submission readiness

- Audience: solo
- Trigger: Builder has code but missing title, story, screenshots, video, repo, or final submit.
- Route: Devpost readiness panel and countdown guardrail.
- BP action: Turn the final submission into a checklist and highlight what is still missing.

Checklist:
- Lock track
- Write first-sentence user pain
- Attach demo URL or video
- Verify final submit

## Who should I ask?

- Audience: hybrid
- Trigger: Builder needs expert help but does not know which sponsor, mentor, judge, or organizer to approach.
- Route: Advisory router and event guide.
- BP action: Match the question to the right expert category and generate a concise ask.

Checklist:
- Pick one problem
- Name stack/domain
- Ask for decision not opinion
- Capture answer as task

## Organizer intervention need

- Audience: organizer
- Trigger: Many builders show the same blocker, confusion, or missing deadline step.
- Route: Intervention queue and organizer handoff.
- BP action: Cluster the issue and prepare a read-only broadcast or floor-team action for human approval.

Checklist:
- Cluster affected builders
- Draft one intervention
- Ask human approval
- Mark only after sent