This document specifies the system requirements for 8080.ai, a platform whose referral program grants credit to users who refer others. The product intent derived from the authoritative requirement thread is narrow and concrete: a user who registered through a friend's referral link, and the friend who referred them, must be able to (a) understand how the referral route works, (b) register or sign in through Apple or Google, (c) inspect their own account for referral credit and referral-related notifications, (d) obtain their personal referral link for sharing, and (e) reach 8080.ai support — including obtaining the support email address — to have a missing referral credit investigated.
The audience is Arabic-speaking, mobile-first, largely non-technical users who signed up through a friend's link (frequently via Apple sign-in) and who are anxious about a reward that never arrived. The product's job is to answer one question clearly: what is the support email, and how do I get my credit investigated?
The originating case that defines the product's tone and priorities: a referring user shared https://8080.ai/refer/Y7MJ7GI2, referred more than one person, registered on the platform through Apple rather than Google, and received no credit. The affected account email supplied was Izz.joudah@gmail.com. The user's final request was for the support email address itself.
8080.ai is delivered as a first-party web application with application-owned identity. Users enroll or authenticate through Apple or Google. Anonymous visitors can read the Landing page and reach the Support and Contact Us destinations without signing in; the referral workspace and the personal referral link are protected and require an authenticated session.
Current actors are the three accepted human personas — Referred User (Referral Participant), Referring User (Referrer), and Support Requester — plus the external identity providers (Apple, Google) and the 8080.ai support team, which is an outbound recipient rather than a persona in this product.
Accepted current behavior covers: registration through a referral link, referral of more than one person through one link, delivery of referral credit to the referring user's account, Apple/Google registration and sign-in, checking the account for referral credit and referral notifications, reaching 8080.ai support through the Support / Contact Us destination, and obtaining the support email address.
Narrow exclusions: the assistant/chat channel has no access to user accounts and cannot fix reward or referral technical issues; referral-credit problems are handled by the 8080.ai support team through the support page, where the affected user provides their email and problem details. No other support channels, account-management capabilities, or adjacent product modules are specified.
Delivery ownership. The referral program, the referral link, the credit ledger, the account, and the Support / Contact Us surfaces are all first-party 8080.ai responsibilities. Apple and Google own only the identity-provider leg of enrollment and sign-in; the product owns everything downstream of the returned identity. The 8080.ai support team owns investigation and resolution of referral-credit disputes; the product owns routing the case to them with the right facts attached.
Access ownership. Identity is application-owned and established through Apple or Google. Anonymous visitors may read the Landing page and use the Support and Contact Us destinations — this is deliberate, because a user whose credit is missing may not be able to sign in, or may be contacting support about an account they cannot access. The Referrals workspace and the Referral Link destination require an authenticated session, because they expose account-bound credit state and a personal sharing link.
Current boundary. Everything in this document is current: the referral route, enrollment, credit visibility, the personal referral link, the support email answer, the diagnostic checklist, and the support message form.
Future boundary. No future-horizon requirements were accepted in the authoritative thread. Nothing in this document should be read as committing to additional support channels, in-app ticketing, credit adjustment tooling, or account recovery.
No reference directive in this project declares content_source authority. Both supplied URLs (https://8080.ai/refer/Y7MJ7GI2 and https://8080.ai/support) are declared feature_reference with supplemental authority, and both rendered only a loading placeholder ("Loading workspace…") on static fetch. No verified factual entities, collections, contact details, or media references were extractable from them, so no content inventory is produced. The support email address is a product requirement to be surfaced by the Support destination, not a verified fact from a content source.
https://8080.ai/refer/<code>, with a copyable field and a short explanation of how referred users register through it.FR-01 — Referral program and credit (explicit) As a Referring User, I should earn referral credit on my account when people I refer register through my referral link, so that referring others is rewarded.
FR-02 — Registration through a referral link (explicit) As a Referred User, I should register in the app through a friend's referral link, so that my registration is attributed to that friend.
https://8080.ai/refer/Y7MJ7GI2.FR-03 — Referring more than one person (explicit) As a Referring User, I should be able to refer more than one person through my single referral link, so that each successful referral is counted.
FR-04 — Apple or Google registration and sign-in (explicit) As a Referred User or Referring User, I should register or sign in using Apple or Google, so that I can access my account without a separate password.
FR-05 — Checking the account for referral credit and notifications (explicit) As a Referring User, I should check my account for referral credit and for notifications or messages related to referrals, so that I know whether my referrals were credited.
FR-06 — Personal referral link (required_inference) As a Referring User, I should view and copy my personal referral link, so that I can share it with people I want to refer.
https://8080.ai/refer/<code> and the Copy control flashes ink and shows "Copied".FR-07 — Reaching 8080.ai support (explicit)
As a Support Requester, I should contact 8080.ai support through the support page at https://8080.ai/support, so that a referral-credit problem can be investigated.
FR-08 — Obtaining the support email address (explicit) As a Support Requester, I should be given the 8080.ai support email address, so that I can write to support directly about a missing referral credit.
FR-09 — Recording the referral relationship (required_inference) As the system, I should record the referral relationship only when a referred user completes registration through the referrer's referral link, so that credit is attributed to the correct referring account.
FR-10 — Identity before protected referral information (required_inference) As a Referred User or Referring User, I should enroll or authenticate through Apple or Google before protected referral information is available, so that my credit and referral link stay bound to my own account.
FR-11 — Returning to inspect credit and notifications (required_inference) As a Referring User, I should be able to return to my account at any time and inspect my referral credit and notifications, so that I can confirm whether a referral was credited after the fact.
FR-12 — Submitting a referral-credit issue to support (required_inference) As a Support Requester, I should submit a referral-credit issue to 8080.ai support through the Support / Contact Us destination with the affected user's email and problem details, so that the support team can investigate.
FR-13 — Diagnostic checklist pre-filling Contact Us (required_inference) As a Support Requester, I should have the diagnostic checklist pre-fill the Contact Us form when I submit it, so that I do not re-enter the same facts twice.
FR-14 — Support channel boundary (explicit) As the product, I should route referral-credit problems to the 8080.ai support team through the support page, so that the affected user provides their email and problem details to the party that can investigate.
Product context. This person arrived at 8080.ai because a friend sent them a referral link of the form https://8080.ai/refer/Y7MJ7GI2. They are not shopping for a product; they are following a personal invitation, and they are frequently on a phone. They may sign up with Apple rather than Google, which matters later because the sign-in method becomes a diagnostic fact.
Primary goal. Complete registration through the friend's link and confirm that the referral is properly attributed, so the friend gets credit and nothing about the invitation is left dangling.
Distinct accepted responsibilities. Opening the referral link and seeing the referral context; choosing Apple or Google to establish identity; completing registration so the relationship is recorded; and, if the attribution appears not to have taken, reaching Support.
Relevant inputs or decisions. Which identity provider to use (Apple or Google); whether the referral context shown on Sign Up matches the friend who invited them; whether to escalate to Support.
Interactions with other accepted participants. Their registration is the event that triggers credit for the Referring User. Their sign-in method and referred email become the facts a Support Requester supplies to the 8080.ai support team.
Observable success. Registration completes, the route rail advances past step 02, and the referral is recorded against the referring user's account.
Product context. This person is already registered and has been actively sharing their personal referral link. They have referred more than one person. Their defining experience in the source case is frustration: people registered through their link, they used Apple rather than

Referral credit not showing up? Reach Support or Contact Us for an investigation.
8080.ai · Referral credit desk
If a friend registered through your referral link and your credit never arrived, this desk routes the case. Paste the referral link you shared — the form is https://8080.ai/refer/<code> — and the route above moves to the step it broke at. The 8080.ai support team investigates the credit against the referral record; the platform does not issue it on the spot.
A referral credit never disappears without a reason — it stops at a step. The route runs from the person who shared the link, through the link itself, into the account that was registered with it, and out to the credit on the referring account. Whenever it stops early, the case is routed to 8080.ai support, not fixed here.
90Providers
Registration and sign-in on 8080.ai use one of two identity providers. The provider used is a diagnostic fact: a referral credit can go unattributed when the account was opened with the provider the referrer did not expect.
Apple
Apple is accepted here. Registration and sign-in both use this provider.
Google is accepted here. Registration and sign-in both use this provider.
Whichever provider opened the account, the support team needs the account email and the referral link to trace the registration.

Referral credit not showing up? Reach Support or Contact Us for an investigation.
8080.ai · Referral credit desk
If a friend registered through your referral link and your credit never arrived, this desk routes the case. Paste the referral link you shared — the form is https://8080.ai/refer/<code> — and the route above moves to the step it broke at. The 8080.ai support team investigates the credit against the referral record; the platform does not issue it on the spot.
A referral credit never disappears without a reason — it stops at a step. The route runs from the person who shared the link, through the link itself, into the account that was registered with it, and out to the credit on the referring account. Whenever it stops early, the case is routed to 8080.ai support, not fixed here.
90Providers
Registration and sign-in on 8080.ai use one of two identity providers. The provider used is a diagnostic fact: a referral credit can go unattributed when the account was opened with the provider the referrer did not expect.
Apple
Apple is accepted here. Registration and sign-in both use this provider.
Google is accepted here. Registration and sign-in both use this provider.
Whichever provider opened the account, the support team needs the account email and the referral link to trace the registration.
No comments yet. Be the first!