# Phantom Signal — Elon Pitch Operator Packet

**Tagline:** Not proof. A signal.  
**Package status:** First-pass static pitch package deployed to Cloudflare Pages at https://phantom-signal-elon-pitch.pages.dev . No custom-domain DNS or existing Phantom Signal production site changes performed.  
**Primary live URL for current audit:** https://phantomsignal-site.pages.dev  
**Current live status note:** The Pages URL returns HTTP 200 but currently shows a project-packet page, not the Elon-ready pitch experience.  
**Custom domain warning:** https://ps.breedloveforever.com is currently broken with Cloudflare 530 / 1033 and should not be used for outreach until fixed.

---

## 1. One-sentence pitch

Phantom Signal documents moments when Tesla / EV / ADAS machine-perception systems appear to render or classify human-like figures or anomalies where human observers report no visible cause — with skeptical review, safety protocol, and no proof-of-ghost claims.

## 2. Positioning rules

Use language like:

- Machine-perception anomaly
- Appears to detect
- Appears to render / classify
- Probabilistic inference
- Sensor fusion
- Under review
- Likely explained
- Unresolved

Avoid language like:

- Proves ghosts
- Tesla detected a spirit
- EVs see the dead
- Official Tesla / xAI affiliation
- Endorsed by Elon Musk
- Production-ready marketplace
- Any fake metrics, fabricated case counts, or invented partner claims

## 3. Public experience architecture

The intended public pitch experience should be navigable as a single link:

1. **Landing / hero**
   - "Not proof. A signal."
   - Establish independent, evidence-first, non-affiliated posture.
   - Link to live Pages URL while noting current page is not yet Elon-ready.

2. **Machine perception gap**
   - Explain that ADAS systems do not see like humans.
   - Frame anomalies as a useful edge-case conversation around autonomy and public perception.

3. **Demo map / signal cards**
   - Show anonymized, sample-safe cards.
   - Suggested fields: location type, timestamp, media type, vehicle/ADAS context, observer note, likely explanations checked, review status.

4. **Submit / join**
   - Scout submission path.
   - Owner contribution path.
   - Operator/reviewer/licensing path.

5. **Field protocol**
   - Safety, consent, privacy, GPS/media evidence, explain-first review.

6. **Deck request / pitch flow**
   - Elon-facing ask.
   - 10-slide deck outline.
   - Next-build checklist.

7. **Legal / safety boundary**
   - Independent concept.
   - No Tesla/xAI affiliation.
   - No official logos or UI mimicry.
   - No paranormal proof claims.

## 4. Roles

### Scouts

Scouts submit GPS-pinned/media evidence from real-world machine-perception moments.

Responsibilities:

- Capture only when safe: parked, passenger, or after the fact.
- Provide location type, timestamp, weather, road context, and observer statement.
- Preserve original media.
- Accept that submissions may be explained, rejected, or kept private.

### Owners

Owners contribute vehicle/location assets or footage.

Responsibilities:

- Offer access to vehicle footage, test locations, private lots, or repeatable observation points.
- Confirm permissions for location and media use.
- Support controlled repeats without unsafe driving.
- Help compare human observation against vehicle-rendered perception.

### Operators

Operators review, license, host, or produce future experiences.

Responsibilities:

- Moderate submissions.
- Apply the safety and evidence protocol.
- Manage redaction, consent, and review labels.
- Package approved cases into demos, partner briefings, episodes, or field missions.
- Maintain the non-affiliation boundary.

### Guests later

Guests can eventually explore approved public cases, attend hosted experiences, or follow story-driven field investigations. Guest-facing features should come after the evidence and safety foundation is credible.

## 5. Field protocol

Minimum case packet:

- GPS pin or precise location type if exact address is unsafe to publish.
- Date and timestamp.
- Original screenshot/video/photo where possible.
- Observer statement: what human witnesses could or could not see.
- Vehicle / ADAS context if known.
- Weather, lighting, traffic, and environmental notes.
- Known nearby objects: signs, reflective surfaces, pedestrians, animals, statues, memorials, trees, posts, parked vehicles.
- Submission consent and publication preference.

Review steps:

1. Confirm safety and legality of capture.
2. Preserve originals and record chain-of-custody notes.
3. Redact private data: faces, plates, home addresses, minors, sensitive property details.
4. Check likely explanations first: UI artifact, map data, reflection, occlusion, lighting, person/animal/object, weather, camera issue, signage, roadside object.
5. Assign status:
   - Likely explained
   - Under review
   - Unresolved
   - Rejected / unsafe / insufficient evidence
6. Publish only with cautious language.

Hard safety boundaries:

- No distracted driving.
- No trespassing.
- No harassment of property owners, witnesses, drivers, or bystanders.
- No blocking roads or staging dangerous scenes.
- No paranormal certainty claims.
- No instructions that encourage unsafe field work.

## 6. Safety and non-affiliation boundary

Phantom Signal is an independent concept and is not affiliated with, endorsed by, sponsored by, or officially connected to Tesla, xAI, Elon Musk, or any automaker.

Brand names may be referenced only descriptively when discussing user-submitted vehicle/ADAS observations.

Do not use:

- Tesla logos
- xAI logos
- Official UI mimicry
- Product screenshots that imply endorsement without rights or context
- Fabricated partner logos
- Fabricated metrics
- “As seen by Tesla” claims unless clearly tied to user-provided footage and review context

## 7. Elon-facing ask

The ask is **attention, feedback, and possible collaboration** — not endorsement.

Suggested wording:

> Elon — Phantom Signal is a cautious public archive for machine-perception anomalies: moments where EV/ADAS systems appear to classify human-like objects that witnesses cannot visually confirm. We are not claiming ghosts. We are asking whether this edge-case public layer could be useful, interesting, or worth pressure-testing with better data and review.

Specific asks:

1. **Attention:** Look at the single-link pitch experience.
2. **Feedback:** Tell us what would make the protocol credible or immediately disqualifying.
3. **Collaboration:** If useful, support a controlled pilot with expert review, vehicle/data context, or safe field tests.
4. **No endorsement required:** The project can remain independent and exploratory.

## 8. 10-slide deck outline

1. **Title:** Phantom Signal — Not proof. A signal.
2. **The pattern:** Drivers increasingly screenshot ADAS displays that appear to render human-like anomalies.
3. **The perception gap:** Machine perception differs from human perception; that gap is culturally powerful and technically interesting.
4. **Why it matters:** Autonomy education, anomaly review, public curiosity, and edge-case storytelling.
5. **The product:** Landing page, demo map, signal cards, submit/join flows, field protocol, operator packet.
6. **Roles:** Scouts, Owners, Operators, later Guests.
7. **Protocol:** Safety-first capture, GPS/media evidence, explain-first review, cautious labels.
8. **Boundary:** Independent, no Tesla/xAI affiliation, no proof-of-ghost claims, no fake metrics.
9. **Pilot:** Controlled submissions, curated case review, expert feedback, safe repeatable observations.
10. **Ask:** Attention, feedback, collaboration, data/vehicle support — not endorsement.

## 9. Next-build checklist

- [ ] Review local `index.html` and approve tone/design.
- [ ] Decide whether to copy this static page into the live Pages project.
- [ ] Fix custom domain Cloudflare 530 / 1033 before public outreach using `ps.breedloveforever.com`.
- [ ] Build real demo map and signal cards using placeholder-safe data first.
- [ ] Add Scout / Owner / Operator forms with consent and privacy language.
- [ ] Add deck request workflow.
- [ ] Export 10-slide deck as PDF.
- [ ] Draft moderation guide for operators.
- [ ] Draft legal/privacy review checklist.
- [ ] Connect newer MVP Cloudflare Functions/D1 handlers only after static pitch direction is approved.
- [ ] Create short outreach copy for X / email / DM.

## 10. Operator quick-start

Local files in this package:

- `/Users/amarabreedlove/phantom-signal-elon-pitch/index.html`
- `/Users/amarabreedlove/phantom-signal-elon-pitch/operator-packet.md`

Recommended review sequence:

1. Open `index.html` locally in a browser.
2. Confirm language stays within cautious machine-perception framing.
3. Confirm no Tesla/xAI logos, official UI mimicry, ghost-proof claims, or fake metrics appear.
4. Confirm the live Pages and broken custom-domain notes are still accurate before outreach.
5. After approval, copy into the appropriate Pages repository and deploy through the normal process.