# Builder Pulse connector data contracts

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

## Devpost participant snapshot

- Mode: participant
- Permission: Builder-provided profile/project data or organizer-approved export.
- Powers: skills normalization, team state, track readiness, submission checklist

Fields:
- username: Stable display handle for the builder's own preview.
- profileUrl: Evidence that the builder has a Devpost profile.
- role: Builder type for positional guidance.
- skills: Stack and teammate-fit routing.
- teamStatus: Solo/team intervention routing.
- track: Track-specific readiness checks.
- projectTitle: Draft/submission progress signal.

Forbidden:
- passwords
- private messages
- write actions
- profile edits

## Discord read-only observer

- Mode: participant
- Permission: Approved bot, admin export, or participant-visible channel snapshot. No personal user tokens.
- Powers: blocker detection, team formation asks, announcement reminders, workshop confusion routing

Fields:
- handle: Map participant-visible signal to the normalized preview.
- recentPosts: Detect blockers, team asks, and confusion from allowed channels.
- blockers: Explicit support requests if exported by an approved workflow.
- lastActiveHoursAgo: Prioritize stale or at-risk builders.
- channel: Route the support request back to the right public channel.

Forbidden:
- DMs
- posting
- moderation actions
- personal user tokens
- hidden/private channels

## Luma / event RSVP context

- Mode: participant
- Permission: Builder-visible RSVP/calendar context first; organizer guest/check-in export later.
- Powers: venue routing, hybrid attendance, workshop reminders, late-arrival fallback

Fields:
- rsvps: Sessions or days the builder has joined.
- attendanceMode: Onsite/remote routing and fallback logic.
- checkInStatus: Organizer-approved presence signal only.
- venue: Confirm location for the next in-person action.

Forbidden:
- guest email list without approval
- payment data
- ticket mutation
- event blasts

## Public AABW schedule

- Mode: public
- Permission: Public website, public Devpost overview, or organizer-supplied schedule file.
- Powers: daily briefing, venue router, workshop-to-task conversion, countdown/deadline context

Fields:
- day (required): Map event phase to builder action.
- date (required): Time-aware routing.
- venue (required): Location guidance.
- phase (required): Enable/integrate/design/build/demo framing.
- workshops: Convert sessions into implementation tasks.

Forbidden:
- unpublished contact details
- private attendee notes
- non-public speaker data

## Organizer roster or official export

- Mode: organizer
- Permission: GenAI Fund-approved read-only CSV/API/export.
- Powers: private triage, aggregate operations, duplicate signal merge, organizer intervention queue

Fields:
- builderId (required): Stable private key for de-duplication.
- role: Support routing and teammate-fit guidance.
- teamStatus: Intervention queue clustering.
- track: Track-aware readiness and deadline routing.
- consentFlags: Respect builder visibility and contact boundaries.

Forbidden:
- public raw roster exposure
- unapproved contact scraping
- sending messages
- changing registrations