Organization partnership
Once submission is active, requests enter intake review. Fit leads to scoped follow-up — without exposing end-client identity on developer surfaces.
Choose intent, add details, review, then submit. Real delivery activates after backend connection — until then we show integration-blocked status. We never invent a success receipt.
Response time depends on request type and backend connection — we do not promise a fixed turnaround or invent SLAs.
Organization intake, membership redirect, support, or ops careers — each routes differently on purpose.
Name, email, and request body. Do not put secrets, OTPs, or employer-identifying dumps you would not want logged.
Until staging is connected, submit shows integration-blocked status — message is not saved. When connected, the same routes activate without a redesign.
Once submission is active, requests enter intake review. Fit leads to scoped follow-up — without exposing end-client identity on developer surfaces.
Use /join and /auth. Contact is not vetting. Identity, skills, and capacity are reviewed on the membership path.
Operational and careers requests queue internally when live. Until then, status stays honest — no decorative success state.