Event request
LinkedIn is required
A public RSVP request requires name, email, and LinkedIn; company is optional. Public requests enter the approval queue, while confirmed members and valid direct-invite links confirm through separate paths.
Selection & privacy
Know what is reviewed, stored, and shared.
What Overflow reviews, stores, and shares today, across event records, standing-community records, private assessment data, and optional public profiles.
Selection
The event and the standing community are separate decisions.
Community application
An assessment report is required
A standing-community application requires email, LinkedIn, and a reviewed AI Work Assessment HTML file. A successful submission records the membership status as applied.
Membership decision
Admin approved
The organizer reviews the private application record and decides membership. The current system supports applied, member, declined, removed, and inactive states.
Different threshold
Attendance is not membership
An assessment is not required to attend. Event participation does not by itself create membership.
Account sign-in
Google sign-in identifies the account. It does not share project content with Google.
Google sign-in requests only your basic identity: name, email address, and a stable account identifier. Overflow stores that identifier and the verified email so the same person returns to the same account.
If the verified Google email already belongs to an Overflow person, sign-in links to that record and its existing projects or community status. Otherwise the signup flow creates a project-owner account, without community membership.
Overflow does not receive or store your Google password, and it does not request access to Gmail, Drive, Calendar, or other Google services. Project briefs remain private between the project owner and Overflow.
Event data & roster
The RSVP record is private. Roster sharing and public listing are separate choices.
The RSVP collects name, email, LinkedIn, and optional company. LinkedIn stays on Overflow's private attendee record.
One checkbox adds the attendee to a roster shared with the group after the event, using name, company, and contact.
A second checkbox lets a confirmed attendee appear on the public event page using name, company, LinkedIn link, and public LinkedIn photo, and can be turned off from their private RSVP page. Overflow uses Unavatar to resolve the portrait and falls back to initials.
Leaving either box unchecked records no opt-in for that use. Event participation, after-event roster sharing, and public event-page listing are maintained separately from your profile.
Your profile
Nothing uploads itself, and private is the default.
- Local generation. The AI Work Assessment analyzes readable local agent history, requests authenticated GitHub history, and can add LinkedIn career chronology when the applicant opts in. It writes an HTML file and does not submit it.
- Comparison after submission. The local review file contains no cohort curves, placement, or comparison data. Overflow calculates that section only from the successfully submitted snapshot.
- Applicant review. The applicant can edit or remove material before uploading and must confirm review of the submitted profile.
- Upload checks. The server parses the structured profile data, discards applicant-supplied cohort payloads, removes marked LinkedIn career context and career fields, and rejects files containing common private-key, credential, or environment-secret patterns.
- Private storage. Overflow discards uploaded HTML, CSS, and JavaScript, then stores only normalized structured matching data and skills. Email and LinkedIn stay on the separate private person record.
- Optional publication. The application defaults to private-to-Overflow. Selecting public creates a page available to anyone and to search engines.
The matching layer
A stored profile is a record Overflow can actually query.
Overflow stores the normalized profile data and skill rows from a submitted report. That makes the private bench searchable when a project needs a specific kind of builder.
Contact identity and work evidence stay on separate records. The application email and LinkedIn URL sit on the private person record; the profile carries skills, tools, domains, and fit. Neither one requires the other to travel.
Owner controls & deletion
Profile owners can change visibility or remove the record.
Secure access
Email management link
The profile-access flow emails a one-time link. The current implementation uses a 15-minute link and a 30-day owner session.
Publication
Publish or unpublish
Publishing writes the public profile page. Unpublishing removes that public page while keeping the profile available privately inside Overflow.
Replacement
Upload a newer profile
The owner can replace the stored report while preserving the existing publication choice. Re-run the assessment whenever your work changes; the newest submission wins.
Deletion boundary
Delete the profile, not every record
Deletion removes the structured profile, public page, matching data, skill rows, and profile analysis data. The private person, LinkedIn, membership, and event-participation records remain.
Overflow does not currently publish a fixed retention period for the remaining person, membership, or event records. Contact the organizer to ask about those records.
Community rules
A working room, not a lead list.
The current operating rules for participation.
- Practitioners first. The room is for AI agencies, consultants, and builders already shipping for clients.
- No staffing or tooling pitches. Recruiters and people attending primarily to sell tooling are outside the stated fit.
- Do not treat the room as a lead list. Roster sharing exists to help attendees reconnect after the event.
- Respect profile visibility. Private profiles stay inside Overflow; only the owner can choose public publication through the supported flow.
- Participation can end. The admin supports removal from the community and from individual events.
Organizer contact
Questions about a record or a decision?
Overflow is hosted by Sam Gaddis. Use the profile-management flow for self-service controls, or contact Sam about event, membership, roster, or other private records.