Lux-Ear Internal Knowledge Base - User contributions [en]

The Listening Post — Ear Mold Types and Retail Pricing

2026-05-10T03:19:57Z

Scott: Add Listening Post product catalog: ear mold styles, descriptions, retail/wholesale pricing, and Lux-Ear relevance notes

== The Listening Post — Ear Mold Types & Retail Pricing ==

'''Source:''' The Listening Post (The Listening Stack), Santa Cruz area, CA<br>
'''Website:''' http://www.listeningstack.com<br>
'''Relevance:''' Competitor/reference retailer offering custom-fit ear molds and hearing protection. Useful for understanding market pricing, product categories, and ear mold terminology relevant to Lux-Ear's custom silicone ear tip product line.

----

=== Background: Ear Mold Fit Types ===

Custom ear molds are made from impressions of the wearer's ear canal and concha. The fit style determines acoustic performance, retention, comfort, and discretion. Key styles from most to least occluding:

{| class="wikitable" style="width:100%"
|-
! Style !! Description !! Fitting Range !! Notes
|-
| '''Full Concha (Standard)''' || Fills the entire concha area and tragus. Used for extreme feedback cases, body aids, snap-in receivers, and pilot headsets. || Profound loss || Largest, most retentive style. Cosmetics not a concern.
|-
| '''Full Shell''' || Follows concha contours top to bottom; carved out inside. Optional helix lock for high-gain feedback control. || Moderate to profound || Helix lock available at no charge.
|-
| '''Half Shell''' || Upper concha (cymba) removed for comfort and easier insertion. Good for dexterity issues. || Moderate to severe || Popular with older users.
|-
| '''Skeleton''' || Open concha with rim seal — inconspicuous, allows airflow in bowl of ear. || Mild to severe || Most popular style balancing discretion and retention.
|-
| '''Semi-Skeleton''' || Similar to skeleton but without full rim at back of concha — ideal when concha lacks definition. || Mild to severe || Not available in Ultraflex or Silicone II materials.
|-
| '''Canal''' || Helix and concha removed; only canal portion retained. Requires long canal impression (past second bend). || Mild to moderate || Must be made with long canals for retention.
|-
| '''Micro Canal''' || Minimal — canal only, very discreet. Same canal requirement as Canal style. || Mild to moderate || Smallest standard style.
|-
| '''Micro Canal w/ Concha Lock''' || Micro canal with small anti-tragus retention arm. Aids removal; aesthetically popular. || Mild to severe || Not available in Ultraflex or Silicone II.
|}

----

=== Ear Plug Styles (Silicone Custom) ===

{| class="wikitable" style="width:100%"
|-
! Style !! Use Case
|-
| '''MAXprotect''' || Maximum hearing protection; optional Impulse Toggle Filter
|-
| '''Surf / Swim''' || Water protection; optional Hearing Membrane variant
|-
| '''Sleep''' || Bowled canal or standard canal for sleep comfort
|-
| '''Concert / Musician (TLS Filter)''' || Flat-attenuation musician's plug with TLS proprietary filter
|-
| '''Concert / Musician (Etymotic Filters)''' || Higher-fidelity musician's plug with Etymotic Research filters
|-
| '''Motorsport''' || Racing/motorsport noise management with TLS filter
|-
| '''Police Radio Adapter / SWAT''' || Single-ear or dual-ear tactical radio adapter
|}

----

=== TLS Retail Pricing (MSRP per set) ===

==== Electronic Hearing Protection ====

{| class="wikitable"
|-
! Product !! MSRP (per set)
|-
| Platinum SoundGear — BTE (NRR -29 dB) || $699.99
|-
| Platinum SoundGear — ITE (NRR -24 dB) || $999.99
|-
| Silver SoundGear — BTE (NRR -29 dB) || $599.99
|-
| Silver SoundGear — ITE (NRR -24 dB) || $899.99
|-
| SoundGear Universal Fit — Police/Tactical/Shooters (no custom fit) || $399.99
|-
| SoundGear Universal Fit — Industrial (lower dB shutoff, no custom fit) || $399.99
|}

==== TLS Wholesale Pricing — Ear Mold Styles ====

{| class="wikitable"
|-
! Style !! One Ear (wholesale) !! Two Ears (wholesale) !! w/ Toggle Filter
|-
| Full Concha / Full Shell / Half Shell / Skeleton / Canal / Micro Canal || $39 || $65 || —
|-
| Micro Canal w/ Concha Lock || $45 || $70 || —
|-
| MAXprotect || $39 || $65 || $89
|-
| Surf or Swim / Sleep / Concert (TLS Filter) / Motorsport || $39 || $65 || —
|-
| Concert / Musician (Etymotic Filters) || $69 || $89 || —
|-
| Police Radio Adapter / SWAT || $45 (1 ear) || $89 (both) || —
|}

----

=== Audiophile & Bluetooth Custom Earphones (MSRP) ===

{| class="wikitable"
|-
! Product !! MSRP
|-
| JayBird Bluebuds X with Silicone Custom Molds (Bluetooth) || $299.99
|-
| Westone CR10 Vinyl Earphones (Custom & Wired) || $269.99
|-
| Westone AC20 Earphones (Custom & Wired) || $379.99
|-
| Tunz Duo Audiophile Earphones (Custom & Wired) || $299.99
|-
| Tunz Trio XB Extra Bass Earphones (Custom & Wired) || $439.99
|}

----

=== Relevance to Lux-Ear ===

* The Listening Post represents the incumbent custom-fit ear solution in the Santa Cruz / Bay Area market — traditional audiologist impression → lab fabrication model (2–3 week turnaround).
* Wholesale ear mold cost: ~$39–$70/set. Lux-Ear's target blended ASP of $125 is positioned above wholesale but well below TLS MSRP, with same-session delivery as a key differentiator.
* The '''skeleton''' and '''canal''' styles are most directly analogous to Lux-Ear's custom silicone ear tip form factors for AirPods/earbuds.
* Material comparison: TLS offers acrylic, vinyl, silicone. Lux-Ear uses silicone exclusively — consistent with the softest, most comfortable, and most durable option per industry consensus.
* TLS uses traditional ear impression (otoplasty) method requiring an audiologist. Lux-Ear replaces this with 3D photogrammetric scanning via Zermatt scanner — no impression material, no audiologist required, scalable to kiosk/home kit model.

----
[[Category:Competitive Intelligence]]
[[Category:Ear Anatomy and Fit Types]]
[[Category:Market Pricing]]
[[Category:Lux-Ear Reference]]

Zermatt/Research/Photometric Stereo

2026-05-08T06:23:48Z

Scott: ClaudeBot: Zermatt research notes

= Photometric Stereo for Ear Scanning =
''May 7, 2026''

== Technique ==
Single fixed camera captures images illuminated sequentially from different LED positions around a ring. Surface normals and 3D depth reconstructed computationally. Reported accuracy: 0.05mm. Introduced by Wolfgang Herwald, April 28, 2026.

== MVPS Studio (Reference Implementation) ==
* Developer: Dr. Berkan Lafci, ETH Zurich | Published: February 2024
* GitHub: https://github.com/berkanlafci/mvpsstudio
* Hardware: 24-LED NeoPixel ring (~66mm OD), Raspberry Pi 5, Ubuntu 22.04, GPIO pin 10
* Software: Open-source deep learning reconstruction pipeline for surface normal estimation

== Optics ==
* '''Diffuser:''' Rosco Cinegel 3026 Tough White Diffusion (=LEE 216), 20x24" sheet — 36% transmission (Y), 1.5 stop loss. Cut to fit over LED ring to soften point sources.
* '''Polarizers:''' Selens 7.8x11.8" adhesive linear polarizing sheets (x2) — cross-polarization eliminates specular glare from skin. One sheet over LED ring (source), one over camera lens (analyzer), rotated 90° to each other.

== Calibration Spec ==
LEE 216 = Rosco Cinegel 3026 = 36% luminance transmission, 1.5 stop reduction. Use this when accounting for diffuser attenuation in photometric stereo light intensity calculations.

== Controller ==
Raspberry Pi 5 (8GB RAM), Ubuntu 22.04. GPIO pin 10 (physical pin 19) for LED data line.

Zermatt/Competitive/Apple Ear Tips

2026-05-08T06:23:43Z

Scott: ClaudeBot: Zermatt research notes

= Apple Ear Tip Supplier Research =
''April 28, 2026''

== Key Finding ==
Apple does not disclose ear tip suppliers. Almost certainly LSR (Liquid Silicone Rubber) molding vendors under NDA, integrated via Foxconn/Luxshare.

== Pricing Signal ==
Typical wholesale: $0.015–$0.50 per piece. High-volume multi-cavity tooling. This is the cost floor Lux-Ear custom tips compete against in the consumer's mind.

== Strategic Positioning ==
The real competitor is the bundled S/M/L tip — not audiology brands or other custom-tip companies. No incumbent optimizes for fit. Most users assume poor fit is just "how earbuds are."

* S/M/L tips = reading glasses rack at CVS
* Lux-Ear = LensCrafters prescription lenses

Structural advantage: Incumbents cannot easily move to custom fit — breaks retail model, complicates inventory, requires new infrastructure. That is the opening.

== Pitch Deck Note ==
Do NOT show competitor logos. Show "S/M/L model" vs "Custom-fit model" and visually destroy the incumbent assumption. Lux-Ear is creating a new category: no one currently owns "fit" in consumer audio.

Zermatt/Research/Key People

2026-05-08T06:23:43Z

Scott: ClaudeBot: Zermatt research notes

= Key People — Photometric Stereo Research Network =
''May 7, 2026''

== Dr. Berkan Lafci ==
* Former: PhD researcher, ETH Zurich — developed MVPS Studio photometric stereo project (Feb 2024)
* Current: Senior ML Research Scientist, Align Technology (Invisalign/iTero), Zurich — dental 3D CV and mesh generation
* Note: No ear canal research found at Align. Space appears open for Lux-Ear.
* ETH colleagues/lab-mates worth exploring as collaborators on reconstruction algorithms.

== Richard Rau ==
* Role: Senior Research Engineer, Sonova R&D HQ, Stäfa, Switzerland (~20km from Zurich)
* Background: PhD-level; Best Paper Runner-Up IPCAI 2021; ultrasound imaging, 3D reconstruction, audiological engineering
* Co-author with Lafci on academic photometric stereo work
* Sonova completed clinical trial NCT05000047 (2021): 3D ear canal scanning vs silicone impressions for hearing aid fitting

== Connection Chain ==
Wolfgang Herwald → Lafci (ETH/MVPS Studio) → Richard Rau (Sonova R&D) → Sonova AG

Direct academic link from Zermatt scanning research into the world's largest hearing care company (Phonak, Unitron, Advanced Bionics), which is already running clinical trials in exactly our space, located 20km from Etienne Coulon.

== Action ==
Deferred until working Zermatt prototype. Do not contact until prototype milestone reached.

Zermatt/Hardware/LED Rings

2026-05-08T06:23:41Z

Scott: ClaudeBot: Zermatt research notes

= Zermatt LED Ring Hardware =
''May 7, 2026''

== Ordered Units (SK6812 RGBW Natural White ~4500K) ==
{| class="wikitable"
! PID !! Description !! LEDs !! Price !! URL
|-
| 2852 || NeoPixel Ring 12x RGBW Natural White || 12 || $9.50 || https://www.adafruit.com/product/2852
|-
| 2855 || NeoPixel Ring 16x RGBW Natural White || 16 || $11.95 || https://www.adafruit.com/product/2855
|-
| 2862 || NeoPixel Ring 24x RGBW Natural White || 24 || $19.95 || https://www.adafruit.com/product/2862
|}

== Why Natural White ~4500K ==
* Most even illumination for photometric stereo on skin
* True white phosphor (RGBW) gives cleaner white than RGB mixing
* Warm white causes yellow cast; cool white causes specular highlights

== Key Specs ==
* Outer diameter: 66mm (24-LED ring) | Power: 5V DC, up to 1.2A | Chip: SK6812 RGBW

== Datasheets ==
* SK6812: https://cdn-shop.adafruit.com/product-files/1138/SK6812%20LED%20datasheet%20.pdf
* WS2812: https://cdn-shop.adafruit.com/datasheets/WS2812.pdf
* WS2812B: https://cdn-shop.adafruit.com/datasheets/WS2812B.pdf
* NeoPixel Überguide: https://learn.adafruit.com/adafruit-neopixel-uberguide

== Libraries ==
* Adafruit NeoPixel: https://github.com/adafruit/Adafruit_NeoPixel
* FastLED: https://github.com/FastLED/FastLED | https://fastled.io/docs/

== Signal Conditioning ==
* 470Ω resistor in series on data line (protects GPIO, prevents ringing)
* 1000µF 10V capacitor across power rails (prevents brown-out on LED inrush)

Zermatt GitHub and Collaboration

2026-05-07T21:14:55Z

Scott: about our technical information on GitHub

{{Lux-Ear Header}}
__TOC__

== Zermatt — GitHub Repository & Collaboration Setup ==

{| class="wikitable" style="font-size:14px; width:100%"
|-
! style="background:#1E5F8E; color:white; width:20%" | Field
! style="background:#1E5F8E; color:white" | Detail
|-
| '''Repository URL''' || https://github.com/mcgregor94086/zermatt
|-
| '''Visibility''' || Private
|-
| '''Owner''' || Scott L. McGregor (mcgregor94086)
|-
| '''Status''' || Active — hardware sprint complete
|-
| '''Classification''' || CONFIDENTIAL — PATENT PENDING
|-
| '''Last updated''' || {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}}
|}

---

=== What this page covers ===

This page documents:
* The structure of the Zermatt GitHub repository
* How to invite and manage collaborators (specifically Akien MacIain)
* How to authenticate from your Mac (Personal Access Token)
* How to push sprint files using the automation script
* The Notion/Google Docs knowledge-sharing workflow

---

== Repository Structure ==

{| class="wikitable" style="font-size:14px; width:100%"
|-
! style="background:#1E5F8E; color:white" | Folder
! style="background:#1E5F8E; color:white" | Contents
|-
| <code>hardware/pcb/</code> || KiCad 8 PCB files — Zermatt_v0.kicad_pcb + .kicad_pro
|-
| <code>hardware/docs/</code> || Circuit schematic, wiring diagram, PCB layout (SVG + DOCX)
|-
| <code>hardware/bom/</code> || Bill of materials (Zermatt_v0_BOM.xlsx)
|-
| <code>docs/architecture/</code> || v0 full architecture document (DOCX)
|-
| <code>docs/assembly/</code> || Step-by-step assembly manual with diagrams (DOCX)
|-
| <code>docs/patent/</code> || Provisional patent application (DOCX)
|-
| <code>software/firmware/</code> || ESP32 MicroPython firmware
|-
| <code>software/app/</code> || React Native iOS/Android app
|-
| <code>software/server/</code> || PHP server code (DreamHost)
|-
| <code>presentations/</code> || Architecture overview deck (PPTX)
|-
| <code>DECISIONS.md</code> || Architecture decision log — updated before every commit
|-
| <code>README.md</code> || Project overview and quick-start guide
|}

---

== Collaborators ==

{| class="wikitable" style="font-size:14px; width:100%"
|-
! style="background:#1E5F8E; color:white" | Name
! style="background:#1E5F8E; color:white" | GitHub Username
! style="background:#1E5F8E; color:white" | Role
! style="background:#1E5F8E; color:white" | Status
|-
| Scott L. McGregor || mcgregor94086 || Owner || Active
|-
| Akien MacIain || akienm || Collaborator (read/write) || Invitation sent — awaiting acceptance
|-
| Wolfgang Herwald || WolfgangHerwald || Collaborator || Active — NDA on file
|}

'''To invite a new collaborator:'''
# Go to https://github.com/mcgregor94086/zermatt/settings/access
# Click '''Add people'''
# Enter their GitHub username or email
# They receive an email — they must click Accept to gain access

---

== Authentication: Personal Access Token ==

GitHub stopped accepting passwords in 2021. You need a '''Personal Access Token (PAT)''' to push from Terminal.

=== Generating a new token ===

# Go directly to: https://github.com/settings/tokens
# Click '''Generate new token (classic)'''
# Name: <code>MacBook Zermatt</code>
# Expiration: 1 year
# Check the '''repo''' scope checkbox
# Click '''Generate token'''
# '''Copy it immediately''' — GitHub shows it only once. It looks like: <code>ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxx</code>

=== Saving to Mac Keychain ===

The first time you run <code>git push</code> after generating a token:
* Username: your GitHub username (<code>mcgregor94086</code>)
* Password: paste the token

Mac Keychain saves it automatically — you will not be asked again until the token expires.

{{Note|If you see "Authentication failed", your token has expired. Generate a new one at https://github.com/settings/tokens and repeat the steps above.}}

---

== Pushing Files: Sprint Automation Script ==

The push script <code>zermatt_github_push.sh</code> automates the full file organisation and commit workflow.

=== What it does ===
# Pulls latest from GitHub
# Creates the correct folder structure if missing
# Copies all downloaded sprint files to the right folders
# Updates <code>DECISIONS.md</code> with new ADR entries
# Updates <code>README.md</code> if missing
# Stages all files, commits with a detailed message, and pushes

=== How to run it ===

Open Terminal and paste these two commands:

<syntaxhighlight lang="bash">
cd ~/Projects/Lux-Ear/zermatt
bash ~/Downloads/zermatt_github_push.sh
</syntaxhighlight>

=== Commit message tag convention ===

{| class="wikitable" style="font-size:14px"
|-
! style="background:#1E5F8E; color:white" | Tag
! style="background:#1E5F8E; color:white" | Use for
|-
| <code>[HARDWARE]</code> || PCB files, schematics, wiring, BOM
|-
| <code>[FIRMWARE]</code> || ESP32 MicroPython code
|-
| <code>[APP]</code> || React Native iOS/Android app code
|-
| <code>[SERVER]</code> || PHP server code
|-
| <code>[DOCS]</code> || Word docs, assembly manual, architecture
|-
| <code>[DECISIONS]</code> || DECISIONS.md updates
|-
| <code>[ADMIN]</code> || README, GitHub Issues, project management
|}

---

== Daily Git Commands Cheat Sheet ==

{| class="wikitable" style="font-family:monospace; font-size:14px; width:100%"
|-
! style="background:#1E5F8E; color:white" | What you want to do
! style="background:#1E5F8E; color:white" | Type this in Terminal
|-
| Go to your Zermatt folder || <code>cd ~/Projects/Lux-Ear/zermatt</code>
|-
| Check what has changed || <code>git status</code>
|-
| Pull latest from GitHub || <code>git pull</code>
|-
| Stage all files || <code>git add -A</code>
|-
| Commit with a message || <code>git commit -m "[DOCS] Updated assembly notes"</code>
|-
| Push to GitHub || <code>git push</code>
|-
| Run the sprint push script || <code>bash ~/Downloads/zermatt_github_push.sh</code>
|-
| See recent history || <code>git log --oneline -10</code>
|-
| Undo last commit (keep files) || <code>git reset --soft HEAD~1</code>
|}

---

== Troubleshooting ==

{| class="wikitable" style="font-size:14px; width:100%"
|-
! style="background:#C0392B; color:white" | Error message
! style="background:#C0392B; color:white" | What it means
! style="background:#C0392B; color:white" | Fix
|-
| Authentication failed || Token expired or wrong || Generate new PAT at https://github.com/settings/tokens
|-
| rejected, non-fast-forward || GitHub has newer changes || Run <code>git pull --rebase</code> then <code>git push</code>
|-
| nothing to commit || No changes since last push || Normal — run <code>git status</code> to confirm
|-
| fatal: not a git repository || Wrong folder || Run <code>cd ~/Projects/Lux-Ear/zermatt</code> first
|-
| command not found: git || Git not installed || Run <code>xcode-select --install</code> in Terminal
|-
| Permission denied (publickey) || SSH not set up — use HTTPS || Run: <code>git remote set-url origin https://github.com/mcgregor94086/zermatt</code>
|}

---

== Notion / Google Docs: Sharing Context with Akien ==

The GitHub repo stores all files. A separate Notion page (or Google Doc) captures the '''human-readable sprint summaries''' and Claude conversation context that cannot live in GitHub.

=== Current recommended approach ===

{| class="wikitable" style="font-size:14px; width:100%"
|-
! style="background:#1E5F8E; color:white" | What
! style="background:#1E5F8E; color:white" | Where
! style="background:#1E5F8E; color:white" | How Akien accesses it
|-
| All code and generated files || GitHub repo || Browser preview or clone
|-
| KiCad PCB file || GitHub /hardware/pcb/ || Download → open in KiCad 8
|-
| Assembly manual, patent, BOM || GitHub /docs/ || Download → open in Pages/Numbers
|-
| Sprint summaries + diagrams || Notion page (or Google Doc) || Public share link — no login needed
|-
| Design decisions log || DECISIONS.md in GitHub || Read in browser
|-
| Task tracking || GitHub Issues || Comment, create new tasks
|}

=== Notion Free plan ===
* Free — no credit card, no expiry
* Unlimited pages
* 1 read-only guest (enough for Akien)
* Sign up at: https://notion.so

=== To share a Notion page with Akien (no account needed) ===
# Open the page in Notion
# Click '''Share''' (top right)
# Toggle '''Publish to web''' ON
# Copy the link and send to Akien by email or text

---

== Current Sprint Status ==

=== Hardware Sprint — Complete ===

{| class="wikitable" style="font-size:14px; width:100%"
|-
! style="background:#1A6B2A; color:white" | Deliverable
! style="background:#1A6B2A; color:white" | File
! style="background:#1A6B2A; color:white" | Status
|-
| KiCad PCB file || Zermatt_v0.kicad_pcb || ✅ Complete
|-
| KiCad project file || Zermatt_v0.kicad_pro || ✅ Complete
|-
| Circuit schematic || ZERM-SCH-001_Circuit_Schematic.svg || ✅ Complete
|-
| Wiring diagram || ZERM-WRG-001_Wiring_Diagram.svg || ✅ Complete
|-
| PCB layout plan || ZERM-PCB-001_PCB_Layout.svg || ✅ Complete
|-
| Hardware document || Zermatt_v0_Circuit_Wiring_PCB.docx || ✅ Complete
|-
| Bill of Materials || Zermatt_v0_BOM.xlsx || ✅ Complete
|-
| Architecture document || Zermatt_v0_Architecture.docx || ✅ Complete
|-
| Assembly manual || Zermatt_v0_Assembly_Manual.docx || ✅ Complete
|-
| Provisional patent || LuxEar_Zermatt_Provisional_Patent.docx || ✅ Complete
|-
| Architecture deck || LuxEar_Zermatt_Architecture_Overview.pptx || ✅ Complete
|}

=== Next Sprint — Firmware & App ===
* ESP32 MicroPython firmware (BLE, WiFi, motor control, LED, audio, camera trigger)
* React Native app skeleton (BLE pairing, scan UI, customer form)
* Server job intake API + database schema

---

== Related IKB Pages ==

* [[Zermatt Scanner — Hardware v0]]
* [[Zermatt Scanner — Architecture]]
* [[Lux-Ear — Active Projects]]
* [[Lux-Ear — Key Contacts]]

[[Category:Zermatt]] [[Category:GitHub]] [[Category:Operations]]

Main Page

2026-05-07T21:09:31Z

Scott: /* 2. Technology */ added Zermatt/GitHub and Collaboration link

== Lux-Ear Go-To-Market Pages ==

=== 1. Overview ===
* [[Executive Summary]]
* [[Market Overview]]
* [[GTM Strategy]]

=== 2. Technology ===
* [[Technology Platform]]
* [[Data Architecture]]
* Zermatt/GitHub and Collaboration
* [[Business Model]]
* [[Partnership Model Clarification]]

=== 3. Financials ===
* [[Revenue-Sharing Models]]
* [[Pricing Models]]
* [[Margin Analysis]]

=== 4. Operations and Partners ===
* [[Retailer and Brand Partner Outreach]]
* [[Marketing and Events]]
* [[Document Preparation]]

=== 5. Manufacturing and Logistics ===
* [[3D Printing Partners]]
* [[Established Ear-Tip Manufacturers]]
* [[Independent 3D Printing Facilities]]
* [[Local Delivery Services]]

=== 6. Hardware ===
* [[Ear Scanner Design and Manufacturing]]
* [[Components Bill of Materials (BOM)]]
* [[Potential Manufacturers]]
* [[3D Printing Equipment for Local Facilities]]
* [[Demonstration Systems for Funding]]
* [[BOM Elements Previously Mentioned]]
* [[Lux-Ear Ear Scanner Models]]
* [[Mobile Event Scanner]]
* [[Retail Kiosk Scanner]]

=== 7. Planning & Strategy ===
* [[Executive Summary (Bullet Points)]]
* [[Main Document: Lux-Ear Go-to-Market Plan]]
* [[Product Models]]
* [[Launch Plan]]
* [[Fulfillment Model]]
* [[Strategic Partnerships]]
* [[Hardware Overview]]
* [[Financial Considerations]]
* [[Milestones & Roadmap]]

=== 8. Software ===
* [[Scanner Finder Programmer's Manual]]
* [[Scanner Control Programmer's Manual]]
* [[Scanner Ordering programmer's Manual]]

Lux-Ear Internal Incidents & Operations Log

2026-01-08T06:04:36Z

Scott: Normalized incident index ordering and status consistency

{{DISPLAYTITLE:Lux-Ear Internal Incidents & Operations Log}}

== Purpose ==
This page serves as the authoritative chronological record of operational incidents, infrastructure failures, recovery efforts, and follow-up actions related to Lux-Ear systems and workflows.

It is intended to:
* Preserve institutional memory
* Reduce repeated troubleshooting
* Support accountability and learning
* Provide a foundation for future automation and reporting

---

== How to Use This Log ==
* Each incident should have its own dedicated page using the [[Template:Incident|Incident Template]]
* Incidents should be listed below in reverse chronological order (newest first)
* This log summarizes incidents; detailed analysis belongs on individual incident pages

---

== Incident Index ==

{| class="wikitable sortable"
! Date
! Incident Title
! Status
! Systems Affected
! Primary Owner
|-
| 2025-12-18
| [[Incident 2025-12-18 – MediaWiki BotPassword Authentication Failure]]
| Resolved / Documented
| MediaWiki / API Automation
| Scott
|-
|2025-12-XX
|[[Incident 2025-12-XX – Cumulative Infrastructure & Cognitive Overload]]
|Resolved / Documented
|Infrastructure / Operations / Human
|Scott
|-
| 2026-01-06
| [[Incident 2026-01-06 – iCloud Sync & Local Visibility Failure]]
| Resolved
| iCloud / Finder / macOS
| Scott
|}

---

== Ongoing / Open Incidents ==


---

== Recently Resolved Incidents ==


---

== Related Pages ==
* [[Template:Incident]]
* [[Lux-Ear Infrastructure]]
* [[Lux-Ear Operations]]
* [[Lux-Ear Automation Roadmap]]

---

[[Category:Incidents]]
[[Category:Operations]]
[[Category:Infrastructure]]

Lux-Ear Internal Incidents & Operations Log

2026-01-08T05:57:00Z

Scott: added new incident in table

{{DISPLAYTITLE:Lux-Ear Internal Incidents & Operations Log}}

== Purpose ==
This page serves as the authoritative chronological record of operational incidents, infrastructure failures, recovery efforts, and follow-up actions related to Lux-Ear systems and workflows.

It is intended to:
* Preserve institutional memory
* Reduce repeated troubleshooting
* Support accountability and learning
* Provide a foundation for future automation and reporting

---

== How to Use This Log ==
* Each incident should have its own dedicated page using the [[Template:Incident|Incident Template]]
* Incidents should be listed below in reverse chronological order (newest first)
* This log summarizes incidents; detailed analysis belongs on individual incident pages

---

== Incident Index ==

{| class="wikitable sortable"
! Date
! Incident Title
! Status
! Systems Affected
! Primary Owner
|-
| 
| [[Incident YYYY-MM-DD – Title]]
| Open / Mitigated / Resolved
|
|
|-
| 2025-12-18
| [[Incident 2025-12-18 – MediaWiki BotPassword Authentication Failure]]
| Open
| MediaWiki / API Automation
| Scott
|-
| 2026-01-06
| [[Incident 2026-01-06 – iCloud Sync & Local Visibility Failure]]
| Resolved
| iCloud / Finder / macOS
| Scott
|-
| 2025-12-XX
| [[Incident 2025-12-XX – Cumulative Infrastructure & Cognitive Overload]]
| Resolved / Documented
| Infrastructure / Operations / Human
| Scott
|}

---

== Ongoing / Open Incidents ==


---

== Recently Resolved Incidents ==


---

== Related Pages ==
* [[Template:Incident]]
* [[Lux-Ear Infrastructure]]
* [[Lux-Ear Operations]]
* [[Lux-Ear Automation Roadmap]]

---

[[Category:Incidents]]
[[Category:Operations]]
[[Category:Infrastructure]]

Incident 2025-12-XX – Cumulative Infrastructure & Cognitive Overload

2026-01-08T05:52:55Z

Scott: Create incident page

= Incident 2025-12-XX – Cumulative Infrastructure & Cognitive Overload =

== Summary ==
Between mid-December 2025 and early January 2026, a series of unresolved infrastructure failures, configuration regressions, and tooling instability accumulated into a broader operational and cognitive overload incident. While no single system outage fully explains the duration or impact, the combined effect significantly impaired troubleshooting efficiency, documentation, communication, and recovery pacing.

This incident captures the *systemic interaction* between technical failures and human operational capacity, and explains why several otherwise manageable issues escalated into prolonged disruption.

== Impact ==
* Delayed resolution of multiple technical incidents
* Inability to automate documentation and recovery tasks
* Extended reliance on fragile manual workflows
* Significant reduction in effective communication capacity
* Missed or delayed responses to critical business and personal communications
* Increased risk of error due to fatigue and context loss

== Contributing Factors ==
=== Technical ===
* MediaWiki BotPassword authentication failures blocking automation
* iCloud Drive sync state ambiguity (files present but not locally visible)
* SSH, networking, and host identity instability across multiple Macs
* Tooling churn (Migration Assistant avoidance, backup reconfiguration, cloud mounting changes)
* Lack of reliable “known good” operational baseline during recovery

=== Operational ===
* Parallel recovery of multiple systems without a stable control plane
* Absence of centralized incident tracking until late in the timeline
* Manual documentation overhead during degraded conditions
* Context switching across infrastructure, OS, hosting, and cloud services

=== Human / Cognitive ===
* Sustained troubleshooting under sleep deprivation
* Psychological overload reducing task initiation and prioritization
* Emotional demands from close relationships during the same period
* Reduced executive function affecting triage, communication, and planning

== Timeline (Condensed) ==
* 2025-12-18 – Initial MediaWiki BotPassword automation failure
* Late Dec 2025 – Expansion of infrastructure instability across Macs and services
* Early Jan 2026 – iCloud Drive visibility failure obstructs access to critical files
* 2026-01-06 – Incident documentation and structured recovery begin
* 2026-01-07 – Incident index, templates, and meta-analysis established

== Resolution ==
This incident was resolved through *documentation, stabilization, and structural recovery*, not a single technical fix. Resolution actions included:
* Establishing a formal Incident Index and templates
* Documenting root causes and timelines for individual incidents
* Restoring visibility into cloud-synced assets
* Re-establishing reliable wiki access and manual publishing
* Acknowledging cognitive and operational limits as first-class incident factors

== Lessons Learned ==
* Incident management must account for human capacity, not just system uptime
* Automation failures have outsized impact during degraded states
* Documentation is a recovery tool, not an afterthought
* Psychological overload is an operational risk multiplier
* Meta-incidents help prevent misattribution of blame or cause

== Follow-Up Actions ==
* Resume automation only after manual baselines are stable
* Maintain incident logging during—not after—disruptions
* Schedule proactive communication check-ins during recovery periods
* Treat sustained overload as a trigger for scope reduction, not escalation

== Related Incidents ==
* [[Incident 2025-12-18 – MediaWiki BotPassword Authentication Failure]]
* [[Incident 2026-01-06 – iCloud Sync & Local Visibility Failure]]

== Category ==
[[Category:Incidents]]
[[Category:Operations]]
[[Category:Infrastructure]]

Lux-Ear Internal Incidents & Operations Log

2026-01-08T05:47:39Z

Scott: Fix index row alignment for iCloud Sync incident

{{DISPLAYTITLE:Lux-Ear Internal Incidents & Operations Log}}

== Purpose ==
This page serves as the authoritative chronological record of operational incidents, infrastructure failures, recovery efforts, and follow-up actions related to Lux-Ear systems and workflows.

It is intended to:
* Preserve institutional memory
* Reduce repeated troubleshooting
* Support accountability and learning
* Provide a foundation for future automation and reporting

---

== How to Use This Log ==
* Each incident should have its own dedicated page using the [[Template:Incident|Incident Template]]
* Incidents should be listed below in reverse chronological order (newest first)
* This log summarizes incidents; detailed analysis belongs on individual incident pages

---

== Incident Index ==

{| class="wikitable sortable"
! Date
! Incident Title
! Status
! Systems Affected
! Primary Owner
|-
| 
| [[Incident YYYY-MM-DD – Title]]
| Open / Mitigated / Resolved
|
|
|-
| 2025-12-18
| [[Incident 2025-12-18 – MediaWiki BotPassword Authentication Failure]]
| Open
| MediaWiki / API Automation
| Scott
|-
| 2026-01-06
| [[Incident 2026-01-06 – iCloud Sync & Local Visibility Failure]]
| Resolved
| iCloud / Finder / macOS
| Scott
|}

---

== Ongoing / Open Incidents ==


---

== Recently Resolved Incidents ==


---

== Related Pages ==
* [[Template:Incident]]
* [[Lux-Ear Infrastructure]]
* [[Lux-Ear Operations]]
* [[Lux-Ear Automation Roadmap]]

---

[[Category:Incidents]]
[[Category:Operations]]
[[Category:Infrastructure]]

Lux-Ear Internal Incidents & Operations Log

2026-01-07T09:35:48Z

Scott: Initial incident index structure

{{DISPLAYTITLE:Lux-Ear Internal Incidents & Operations Log}}

== Purpose ==
This page serves as the authoritative chronological record of operational incidents, infrastructure failures, recovery efforts, and follow-up actions related to Lux-Ear systems and workflows.

It is intended to:
* Preserve institutional memory
* Reduce repeated troubleshooting
* Support accountability and learning
* Provide a foundation for future automation and reporting

---

== How to Use This Log ==
* Each incident should have its own dedicated page using the [[Template:Incident|Incident Template]]
* Incidents should be listed below in reverse chronological order (newest first)
* This log summarizes incidents; detailed analysis belongs on individual incident pages

---

== Incident Index ==

{| class="wikitable sortable"
! Date
! Incident Title
! Status
! Systems Affected
! Primary Owner
|-
| 
| [[Incident YYYY-MM-DD – Title]]
| Open / Mitigated / Resolved
|
|
|-
| 2025-12-18
| [[Incident 2025-12-18 – MediaWiki BotPassword Authentication Failure]]
| Open
| MediaWiki / API Automation
| Scott
|}

---

== Ongoing / Open Incidents ==


---

== Recently Resolved Incidents ==


---

== Related Pages ==
* [[Template:Incident]]
* [[Lux-Ear Infrastructure]]
* [[Lux-Ear Operations]]
* [[Lux-Ear Automation Roadmap]]

---

[[Category:Incidents]]
[[Category:Operations]]
[[Category:Infrastructure]]

Lux-Ear Internal Incidents & Operations Log

2026-01-07T09:07:53Z

Scott: Create incident index page

{{DISPLAYTITLE:Lux-Ear Internal Incidents & Operations Log}}

== Purpose ==
This page serves as the authoritative chronological record of operational incidents, infrastructure failures, recovery efforts, and follow-up actions related to Lux-Ear systems and workflows.

It is intended to:
* Preserve institutional memory
* Reduce repeated troubleshooting
* Support accountability and learning
* Provide a foundation for future automation and reporting

---

== How to Use This Log ==
* Each incident should have its own dedicated page using the [[Template:Incident|Incident Template]]
* Incidents should be listed below in reverse chronological order (newest first)
* This log summarizes incidents; detailed analysis belongs on individual incident pages

---

== Incident Index ==

{| class="wikitable sortable"
! Date
! Incident Title
! Status
! Systems Affected
! Primary Owner
|-
| 
| [[Incident YYYY-MM-DD – Title]]
| Open / Mitigated / Resolved
|
|
|}

---

== Ongoing / Open Incidents ==


---

== Recently Resolved Incidents ==


---

== Related Pages ==
* [[Template:Incident]]
* [[Lux-Ear Infrastructure]]
* [[Lux-Ear Operations]]
* [[Lux-Ear Automation Roadmap]]

---

[[Category:Incidents]]
[[Category:Operations]]
[[Category:Infrastructure]]

Template:Incident

2026-01-07T09:03:36Z

Scott: Initial Incident template

{{DISPLAYTITLE:Incident YYYY-MM-DD – <Short Title>}}

== Summary ==
A brief, factual description of what went wrong, written so that someone unfamiliar with the system can understand the issue in 2–3 sentences.

---

== Impact ==
* What was blocked or degraded
* Who or what was affected
* Whether workarounds existed

---

== Timeline ==
* '''YYYY-MM-DD HH:MM''' – Initial symptom observed
* '''YYYY-MM-DD HH:MM''' – Key diagnostic step
* '''YYYY-MM-DD HH:MM''' – Mitigation attempt
* '''YYYY-MM-DD HH:MM''' – Investigation paused or resolved

---

== Technical Context ==
* '''System / Component:'''
* '''Versions:'''
* '''Environment:''' (local, server, cloud, mixed)
* '''Relevant configuration:'''

---

== Root Cause ==
A concise explanation of the underlying cause.
Avoid blame; focus on system behavior, configuration gaps, or missing assumptions.

---

== Resolution Status ==
* '''Status:''' Open / Mitigated / Resolved / Deferred
* '''Resolution summary:''' (If resolved or partially resolved)

---

== Follow-Up Actions ==
* [ ] Concrete action item
* [ ] Configuration change
* [ ] Documentation update
* [ ] Automation or monitoring improvement

---

== Notes ==
Optional section for:
* Contributing factors
* Contextual constraints
* Human or organizational factors
* Links to related incidents

---

[[Category:Incidents]]
[[Category:Operations]]
[[Category:Infrastructure]]

Incident 2025-12-18 – MediaWiki BotPassword Authentication Failure

2026-01-07T08:56:30Z

Scott: An attempt to enable automated posting and maintenance tasks on the Lux-Ear Internal Knowledge Base (MediaWiki 1.41.1) failed due to incomplete BotPassword authentication configuration.

Incident 2025-12-18 – MediaWiki BotPassword Authentication Failure

Summary

An attempt to enable automated posting and maintenance tasks on the Lux-Ear Internal Knowledge Base (MediaWiki 1.41.1) failed due to incomplete BotPassword authentication configuration. Although bot users and bot passwords were successfully created and stored in the database, API authentication using those credentials consistently failed.

This incident blocked automation work, delayed publication of operational documentation, and contributed to extended manual intervention during a period of broader infrastructure instability.

⸻

Impact
• Automated posting to the Wiki via API was not possible
• Deployment and documentation automation scripts were blocked
• Manual wiki edits were required during an already degraded operational state
• Contributed to cumulative operational and cognitive overload

⸻

Timeline (condensed)
• 2025-12-18 – Initial attempt to create and use BotPasswords for API access
• Bot users and passwords appeared correctly in the database (bot_passwords table)
• API login attempts (action=login, action=clientlogin) consistently failed
• Extensive debugging confirmed credentials were correct but rejected
• Investigation paused due to overlapping infrastructure issues

⸻

Technical Findings
• MediaWiki version: 1.41.1
• $wgEnableBotPasswords = true
• Bot password records existed and were correctly stored
• Bot users had appropriate groups (bot, sysop, bureaucrat, etc.)
• API endpoint (/api.php) was functional
• Missing authentication provider:
• BotPasswordAuthenticationProvider was not registered in wgAuthManagerAutoConfig
• As a result, AuthManager could not authenticate bot credentials even though they existed

⸻

Root Cause

BotPasswords were enabled at the configuration level, but the corresponding authentication provider was not registered with MediaWiki’s AuthManager system. This created a misleading state where bot credentials could be created and stored but never successfully authenticated.

⸻

Resolution Status

Unresolved at time of incident.

The issue requires explicit configuration of the BotPassword authentication provider in LocalSettings.php, or verification that required components are correctly loaded for MediaWiki 1.41.x.

⸻

Follow-Up Actions
• Explicitly register BotPasswordAuthenticationProvider in wgAuthManagerAutoConfig
• Verify BotPassword API login using a minimal test script
• Document the correct configuration pattern for future deployments
• Resume automation work once API authentication is confirmed functional

⸻

Notes

This incident occurred during a period of compounded infrastructure changes (new Mac setup, SSH environment changes, backup reconfiguration, and network instability). The cumulative effect significantly increased time-to-resolution beyond what the individual issue would normally require.

⸻

[[Category:Incidents]]
[[Category:Operations]]
[[Category:MediaWiki]]
[[Category:Infrastructure]]

⸻

When you’re ready, next we can:
• create the standard incident template from this
• extract and publish the remaining incidents from the ZIP
• add a brief incident index entry to the Operations Log page

Lux-Ear Internal Incidents and Operations Log

2026-01-07T08:11:58Z

Scott: This page is the entry point for documenting significant technical, operational, and human-factors incidents affecting Lux-Ear systems, infrastructure, and workflows. The purpose of this log is not blame, but learning: * Preserve hard-won diagnostic knowledge * Reduce repeated outages * Improve recovery speed * Acknowledge human limits as part of system reliability == How to use this log == * Each incident should have its own page * Incidents sh

= Lux-Ear Internal Incidents & Operations Log =

This page is the entry point for documenting significant technical, operational,
and human-factors incidents affecting Lux-Ear systems, infrastructure, and workflows.

The purpose of this log is not blame, but learning:
* Preserve hard-won diagnostic knowledge
* Reduce repeated outages
* Improve recovery speed
* Acknowledge human limits as part of system reliability

== How to use this log ==
* Each incident should have its own page
* Incidents should be factual, time-ordered, and candid
* Partial or unresolved incidents are acceptable and encouraged

== Incident Categories ==
* Infrastructure & Hosting (DreamHost, DNS, SSL, backups)
* macOS & Client Systems
* MediaWiki & Knowledge Infrastructure
* Authentication & Automation
* Human Factors & Operational Load

== Index of Incidents ==
''(Incident pages will be listed here as they are published.)''

Data Architecture

2025-05-20T05:29:53Z

Scott: /* Architecture Diagram */ clean up text

== Lux-Ear Internal Wiki ==
=== Page: Data Architecture ===

'''Overview'''
This page describes the proposed data architecture for Lux-Ear, leveraging Firebase to provide scalable, real-time infrastructure for kiosk scanners, customer-facing apps, internal tools, and cloud-based services.

=== Architecture Diagram ===

[[File:LuxEar_Data_Architecture_Diagram.png |800px|center|thumb|Proposed Firebase-based architecture for Lux-Ear]]

=== Key Components ===

* '''Firebase Authentication'''

* Authenticates users and devices (e.g., kiosk operators, customers, franchisees).
* Supports multi-platform logins and enforces secure, role-based access.

* '''Firestore (Cloud Firestore)'''

* NoSQL database used to store metadata for scans, kiosk statuses, user profiles.
* Real-time updates across web and mobile clients.
* Offline caching support for kiosk and mobile operations.

* '''Firebase Cloud Storage'''

* Stores large files including 3D ear scans, images, diagnostic logs.
* Access control rules tied to user or kiosk identity.

* '''Firebase Cloud Functions'''

* Hosts backend logic for events like scan upload, payment processing, and scan-to-CAD conversion.

* '''Firebase Hosting'''

* Serves static pages and web applications (e.g., Find a Scanner, Admin Dashboard).

* '''Analytics and Crashlytics'''

* Provides usage statistics, session tracking, and error diagnostics.

=== Optional Extensions ===

* Google Cloud Vertex AI: AI-based modeling of ear shapes.
* BigQuery: Advanced analytics on scan volumes, locations, and trends.
* Stripe: Payment integration via Firebase Cloud Functions.
* AppCheck: Ensures requests come from verified app clients.

=== Author ===
Scott McGregor
Lux-Ear Founder and Product Strategy Lead

Data Architecture

2025-05-20T05:27:11Z

Scott: New Data Architecture page

== Lux-Ear Internal Wiki ==
=== Page: Data Architecture ===

'''Overview'''
This page describes the proposed data architecture for Lux-Ear, leveraging Firebase to provide scalable, real-time infrastructure for kiosk scanners, customer-facing apps, internal tools, and cloud-based services.

=== Architecture Diagram ===

[[File:LuxEar_Data_Architecture_Diagram.png |800px|center|thumb|Proposed Firebase-based architecture for Lux-Ear]]

=== Key Components ===

* '''Firebase Authentication'''

* Authenticates users and devices (e.g., kiosk operators, customers, franchisees).
* Supports multi-platform logins and enforces secure, role-based access.

* '''Firestore (Cloud Firestore)'''

* NoSQL database used to store metadata for scans, kiosk statuses, user profiles.
* Real-time updates across web and mobile clients.
* Offline caching support for kiosk and mobile operations.

* '''Firebase Cloud Storage'''

* Stores large files including 3D ear scans, images, diagnostic logs.
* Access control rules tied to user or kiosk identity.

* '''Firebase Cloud Functions'''

* Hosts backend logic for events like scan upload, payment processing, and scan-to-CAD conversion.

* '''Firebase Hosting'''

* Serves static pages and web applications (e.g., Find a Scanner, Admin Dashboard).

* '''Analytics and Crashlytics'''

* Provides usage statistics, session tracking, and error diagnostics.

=== Optional Extensions ===

* Google Cloud Vertex AI: AI-based modeling of ear shapes.
* BigQuery: Advanced analytics on scan volumes, locations, and trends.
* Stripe: Payment integration via Firebase Cloud Functions.
* AppCheck: Ensures requests come from verified app clients.

\=== How to Add This Page to the Internal Wiki ===

1. Log into the Lux-Ear Internal Knowledge Base.

2. In the search bar or URL, go to:

`https://ikb.lux-ear.com/index.php?title=Luxear_data_architecture`

3. If the page does not yet exist, click "Create this page".

4. Copy and paste the entire content of this document.

5. Save the page.

6. To link this page from another, insert:

`[[Luxear_data_architecture|Data Architecture]]`

For example, from your main index or technical documentation section.

7. To upload the diagram:

* Go to "Upload file" in the left sidebar.
* Upload `LuxEar_Data_Architecture_Diagram.png`.
* Make sure the filename matches the one referenced in the `[[File:...]]` tag above.

=== Author ===
Scott McGregor
Lux-Ear Founder and Product Strategy Lead

Main Page

2025-05-20T05:25:52Z

Scott: /* 2. Technology */ changed name of Data Architecture page

== Lux-Ear Go-To-Market Pages ==

=== 1. Overview ===
* [[Executive Summary]]
* [[Market Overview]]
* [[GTM Strategy]]

=== 2. Technology ===
* [[Technology Platform]]
* [[Data Architecture]]
* [[Business Model]]
* [[Partnership Model Clarification]]

=== 3. Financials ===
* [[Revenue-Sharing Models]]
* [[Pricing Models]]
* [[Margin Analysis]]

=== 4. Operations and Partners ===
* [[Retailer and Brand Partner Outreach]]
* [[Marketing and Events]]
* [[Document Preparation]]

=== 5. Manufacturing and Logistics ===
* [[3D Printing Partners]]
* [[Established Ear-Tip Manufacturers]]
* [[Independent 3D Printing Facilities]]
* [[Local Delivery Services]]

=== 6. Hardware ===
* [[Ear Scanner Design and Manufacturing]]
* [[Components Bill of Materials (BOM)]]
* [[Potential Manufacturers]]
* [[3D Printing Equipment for Local Facilities]]
* [[Demonstration Systems for Funding]]
* [[BOM Elements Previously Mentioned]]
* [[Lux-Ear Ear Scanner Models]]
* [[Mobile Event Scanner]]
* [[Retail Kiosk Scanner]]

=== 7. Planning & Strategy ===
* [[Executive Summary (Bullet Points)]]
* [[Main Document: Lux-Ear Go-to-Market Plan]]
* [[Product Models]]
* [[Launch Plan]]
* [[Fulfillment Model]]
* [[Strategic Partnerships]]
* [[Hardware Overview]]
* [[Financial Considerations]]
* [[Milestones & Roadmap]]

Main Page

2025-05-20T05:19:04Z

Scott: /* 2. Technology */

== Lux-Ear Go-To-Market Pages ==

=== 1. Overview ===
* [[Executive Summary]]
* [[Market Overview]]
* [[GTM Strategy]]

=== 2. Technology ===
* [[Technology Platform]]
* [[Luxear_data_architecture]]
* [[Business Model]]
* [[Partnership Model Clarification]]

=== 3. Financials ===
* [[Revenue-Sharing Models]]
* [[Pricing Models]]
* [[Margin Analysis]]

=== 4. Operations and Partners ===
* [[Retailer and Brand Partner Outreach]]
* [[Marketing and Events]]
* [[Document Preparation]]

=== 5. Manufacturing and Logistics ===
* [[3D Printing Partners]]
* [[Established Ear-Tip Manufacturers]]
* [[Independent 3D Printing Facilities]]
* [[Local Delivery Services]]

=== 6. Hardware ===
* [[Ear Scanner Design and Manufacturing]]
* [[Components Bill of Materials (BOM)]]
* [[Potential Manufacturers]]
* [[3D Printing Equipment for Local Facilities]]
* [[Demonstration Systems for Funding]]
* [[BOM Elements Previously Mentioned]]
* [[Lux-Ear Ear Scanner Models]]
* [[Mobile Event Scanner]]
* [[Retail Kiosk Scanner]]

=== 7. Planning & Strategy ===
* [[Executive Summary (Bullet Points)]]
* [[Main Document: Lux-Ear Go-to-Market Plan]]
* [[Product Models]]
* [[Launch Plan]]
* [[Fulfillment Model]]
* [[Strategic Partnerships]]
* [[Hardware Overview]]
* [[Financial Considerations]]
* [[Milestones & Roadmap]]

Main Page

2025-05-20T05:16:57Z

Scott: /* 2. Technology */ added Data Architecture

== Lux-Ear Go-To-Market Pages ==

=== 1. Overview ===
* [[Executive Summary]]
* [[Market Overview]]
* [[GTM Strategy]]

=== 2. Technology ===
* [[Technology Platform]]
* [[Luxear_data_architecture|Data Architecture]]
* [[Business Model]]
* [[Partnership Model Clarification]]

=== 3. Financials ===
* [[Revenue-Sharing Models]]
* [[Pricing Models]]
* [[Margin Analysis]]

=== 4. Operations and Partners ===
* [[Retailer and Brand Partner Outreach]]
* [[Marketing and Events]]
* [[Document Preparation]]

=== 5. Manufacturing and Logistics ===
* [[3D Printing Partners]]
* [[Established Ear-Tip Manufacturers]]
* [[Independent 3D Printing Facilities]]
* [[Local Delivery Services]]

=== 6. Hardware ===
* [[Ear Scanner Design and Manufacturing]]
* [[Components Bill of Materials (BOM)]]
* [[Potential Manufacturers]]
* [[3D Printing Equipment for Local Facilities]]
* [[Demonstration Systems for Funding]]
* [[BOM Elements Previously Mentioned]]
* [[Lux-Ear Ear Scanner Models]]
* [[Mobile Event Scanner]]
* [[Retail Kiosk Scanner]]

=== 7. Planning & Strategy ===
* [[Executive Summary (Bullet Points)]]
* [[Main Document: Lux-Ear Go-to-Market Plan]]
* [[Product Models]]
* [[Launch Plan]]
* [[Fulfillment Model]]
* [[Strategic Partnerships]]
* [[Hardware Overview]]
* [[Financial Considerations]]
* [[Milestones & Roadmap]]

Luxear data architect

2025-05-20T05:14:31Z

Scott: added a diagram

== Lux-Ear Internal Wiki ==
=== Page: Data Architecture ===

'''Overview'''
This page describes the proposed data architecture for Lux-Ear, leveraging Firebase to provide scalable, real-time infrastructure for kiosk scanners, customer-facing apps, internal tools, and cloud-based services.

=== Architecture Diagram ===

[[File:LuxEar_Data_Architecture_Diagram.png |800px|center|thumb|Proposed Firebase-based architecture for Lux-Ear]]

=== Key Components ===

* '''Firebase Authentication'''

* Authenticates users and devices (e.g., kiosk operators, customers, franchisees).
* Supports multi-platform logins and enforces secure, role-based access.

* '''Firestore (Cloud Firestore)'''

* NoSQL database used to store metadata for scans, kiosk statuses, user profiles.
* Real-time updates across web and mobile clients.
* Offline caching support for kiosk and mobile operations.

* '''Firebase Cloud Storage'''

* Stores large files including 3D ear scans, images, diagnostic logs.
* Access control rules tied to user or kiosk identity.

* '''Firebase Cloud Functions'''

* Hosts backend logic for events like scan upload, payment processing, and scan-to-CAD conversion.

* '''Firebase Hosting'''

* Serves static pages and web applications (e.g., Find a Scanner, Admin Dashboard).

* '''Analytics and Crashlytics'''

* Provides usage statistics, session tracking, and error diagnostics.

=== Optional Extensions ===

* Google Cloud Vertex AI: AI-based modeling of ear shapes.
* BigQuery: Advanced analytics on scan volumes, locations, and trends.
* Stripe: Payment integration via Firebase Cloud Functions.
* AppCheck: Ensures requests come from verified app clients.

\=== How to Add This Page to the Internal Wiki ===

1. Log into the Lux-Ear Internal Knowledge Base.

2. In the search bar or URL, go to:

`https://ikb.lux-ear.com/index.php?title=Luxear_data_architecture`

3. If the page does not yet exist, click "Create this page".

4. Copy and paste the entire content of this document.

5. Save the page.

6. To link this page from another, insert:

`[[Luxear_data_architecture|Data Architecture]]`

For example, from your main index or technical documentation section.

7. To upload the diagram:

* Go to "Upload file" in the left sidebar.
* Upload `LuxEar_Data_Architecture_Diagram.png`.
* Make sure the filename matches the one referenced in the `[[File:...]]` tag above.

=== Author ===
Scott McGregor
Lux-Ear Founder and Product Strategy Lead

File:LuxEar Data Architecture Diagram.png

2025-05-20T04:57:11Z

Scott: Firebase Data Architecture Diagram

== Summary ==
Firebase Data Architecture Diagram

Luxear data architect

2025-05-20T04:45:19Z

Scott: LuxEar Planned Data Architecture

== Lux-Ear Internal Wiki ==
=== Page: Data Architecture ===

'''Overview'''
This page describes the proposed data architecture for Lux-Ear, leveraging Firebase to provide scalable, real-time infrastructure for kiosk scanners, customer-facing apps, internal tools, and cloud-based services.

=== Architecture Diagram ===

[[File\:LuxEar\_Data\_Architecture\_Diagram.png|800px|center|thumb|Proposed Firebase-based architecture for Lux-Ear]]

=== Key Components ===

* '''Firebase Authentication'''

* Authenticates users and devices (e.g., kiosk operators, customers, franchisees).
* Supports multi-platform logins and enforces secure, role-based access.

* '''Firestore (Cloud Firestore)'''

* NoSQL database used to store metadata for scans, kiosk statuses, user profiles.
* Real-time updates across web and mobile clients.
* Offline caching support for kiosk and mobile operations.

* '''Firebase Cloud Storage'''

* Stores large files including 3D ear scans, images, diagnostic logs.
* Access control rules tied to user or kiosk identity.

* '''Firebase Cloud Functions'''

* Hosts backend logic for events like scan upload, payment processing, and scan-to-CAD conversion.

* '''Firebase Hosting'''

* Serves static pages and web applications (e.g., Find a Scanner, Admin Dashboard).

* '''Analytics and Crashlytics'''

* Provides usage statistics, session tracking, and error diagnostics.

=== Optional Extensions ===

* Google Cloud Vertex AI: AI-based modeling of ear shapes.
* BigQuery: Advanced analytics on scan volumes, locations, and trends.
* Stripe: Payment integration via Firebase Cloud Functions.
* AppCheck: Ensures requests come from verified app clients.

\=== How to Add This Page to the Internal Wiki ===

1. Log into the Lux-Ear Internal Knowledge Base.

2. In the search bar or URL, go to:

`https://ikb.lux-ear.com/index.php?title=Luxear_data_architecture`

3. If the page does not yet exist, click "Create this page".

4. Copy and paste the entire content of this document.

5. Save the page.

6. To link this page from another, insert:

`[[Luxear_data_architecture|Data Architecture]]`

For example, from your main index or technical documentation section.

7. To upload the diagram:

* Go to "Upload file" in the left sidebar.
* Upload `LuxEar_Data_Architecture_Diagram.png`.
* Make sure the filename matches the one referenced in the `[[File:...]]` tag above.

=== Author ===
Scott McGregor
Lux-Ear Founder and Product Strategy Lead

Luxear data architect

2025-05-20T04:43:02Z

Scott: LuxEar Planned Data Architecture

\== Lux-Ear Internal Wiki ==
\=== Page: Data Architecture ===

'''Overview'''
This page describes the proposed data architecture for Lux-Ear, leveraging Firebase to provide scalable, real-time infrastructure for kiosk scanners, customer-facing apps, internal tools, and cloud-based services.

\=== Architecture Diagram ===

\[\[File\:LuxEar\_Data\_Architecture\_Diagram.png|800px|center|thumb|Proposed Firebase-based architecture for Lux-Ear]]

\=== Key Components ===

* '''Firebase Authentication'''

* Authenticates users and devices (e.g., kiosk operators, customers, franchisees).
* Supports multi-platform logins and enforces secure, role-based access.

* '''Firestore (Cloud Firestore)'''

* NoSQL database used to store metadata for scans, kiosk statuses, user profiles.
* Real-time updates across web and mobile clients.
* Offline caching support for kiosk and mobile operations.

* '''Firebase Cloud Storage'''

* Stores large files including 3D ear scans, images, diagnostic logs.
* Access control rules tied to user or kiosk identity.

* '''Firebase Cloud Functions'''

* Hosts backend logic for events like scan upload, payment processing, and scan-to-CAD conversion.

* '''Firebase Hosting'''

* Serves static pages and web applications (e.g., Find a Scanner, Admin Dashboard).

* '''Analytics and Crashlytics'''

* Provides usage statistics, session tracking, and error diagnostics.

\=== Optional Extensions ===

* Google Cloud Vertex AI: AI-based modeling of ear shapes.
* BigQuery: Advanced analytics on scan volumes, locations, and trends.
* Stripe: Payment integration via Firebase Cloud Functions.
* AppCheck: Ensures requests come from verified app clients.

\=== How to Add This Page to the Internal Wiki ===

1. Log into the Lux-Ear Internal Knowledge Base.

2. In the search bar or URL, go to:

`https://ikb.lux-ear.com/index.php?title=Luxear_data_architecture`

3. If the page does not yet exist, click "Create this page".

4. Copy and paste the entire content of this document.

5. Save the page.

6. To link this page from another, insert:

`[[Luxear_data_architecture|Data Architecture]]`

For example, from your main index or technical documentation section.

7. To upload the diagram:

* Go to "Upload file" in the left sidebar.
* Upload `LuxEar_Data_Architecture_Diagram.png`.
* Make sure the filename matches the one referenced in the `[[File:...]]` tag above.

\=== Author ===
Scott McGregor
Lux-Ear Founder and Product Strategy Lead

Template:LuxEarFooter

2025-05-12T20:10:34Z

Scott: added a line

<div style="border-top: 1px solid #ccc; padding-top: 8px; font-size: 80%; color: #777; text-align: center; margin-top: 30px;">
><hr /><b>Lux-Ear Company Confidential — Internal Use Only</b><br /><hr />
[[Main Page]] • [[Special:RecentChanges|Recent Changes]] • [[Special:AllPages|All Pages]]
</div>

Template:LuxEarFooter

2025-05-12T20:07:37Z

Scott:

<div style="border-top: 1px solid #ccc; padding-top: 8px; font-size: 80%; color: #777; text-align: center; margin-top: 30px;">
<b>Lux-Ear Company Confidential — Internal Use Only</b><br /><hr />
[[Main Page]] • [[Special:RecentChanges|Recent Changes]] • [[Special:AllPages|All Pages]]
</div>

Template:LuxEarPage

2025-05-12T19:59:33Z

Scott: fixed footer placement

<div class="luxear-page">

{{LuxEarHeader}}
== Summary ==
<ul>
<li><b>Author:</b> {{{author|}}}</li>
<li><b>Start Date:</b> {{{start|Not set}}}</li>
<li><b>Due Date:</b> {{{due|Not set}}}</li>
<li><b>Assessment Criteria:</b> {{{assessment|Not defined}}}</li>
<li><b>Action Items:</b>
<ul>
{{{actionitems|<li>None</li>}}}
</ul>
</li>
</ul>

== Content ==
{{{content|<i>No content provided.</i>}}}

== Sources ==
{{{sources|<small>No sources cited.</small>}}}

</div>

{{LuxEarFooter}}

Template:LuxEarHeader

2025-05-12T19:55:34Z

Scott: alignment

<div style="border-bottom: 2px solid #000; padding-bottom: 6px; margin-bottom: 10px;">
<div style="display: flex; align-items: flex-start; gap: 12px;"><div style="line-height: 1;">[[File:Luxear square logo_150.png|64px|link=Main Page]]</div><div style="line-height: 1.2; font-size: 90%; text-align: left; align-self: flex-start;"><span style="font-size: 140%; font-weight: bold; display: block;">Lux-Ear Internal Knowledge Base</span><span style="font-size: 80%; font-style: italic; display: block;">Authorized personnel only</span><span style="font-size: 80%; font-style: italic; display: block;">Company Confidential Intellectual Property</span>
</div>
</div>
</div>

Template:LuxEarHeader

2025-05-12T19:28:57Z

Scott: alignment edit

<div style="border-bottom: 2px solid #000; padding-bottom: 6px; margin-bottom: 10px;">
<div style="display: flex; align-items: flex-start;">
<div style="line-height: 1; vertical-align: top;">
[[File:Luxear square logo_150.png|64px|link=Main Page|class=logo-icon]]
</div>
<div style="font-size: 140%; padding-left: 20px; line-height: 1.2;">
<b>Lux-Ear Internal Knowledge Base</b><br>
<i>Authorized personnel only<br>
Company Confidential Intellectual Property</i>
</div>
</div>
</div>

Template:LuxEarFooter

2025-05-12T19:09:38Z

Scott: Bolded footer

<div style="border-top: 1px solid #ccc; padding-top: 8px; font-size: 80%; color: #777; text-align: center; margin-top: 30px;">
<b>Lux-Ear Company Confidential — Internal Use Only</b><br />
[[Main Page]] • [[Special:RecentChanges|Recent Changes]] • [[Special:AllPages|All Pages]]
</div>

Template:LuxEarPage

2025-05-12T19:06:20Z

Scott: Added headers and footers

<div class="luxear-page">

{{LuxEarHeader}}
== Summary ==
<ul>
<li><b>Author:</b> {{{author|}}}</li>
<li><b>Start Date:</b> {{{start|Not set}}}</li>
<li><b>Due Date:</b> {{{due|Not set}}}</li>
<li><b>Assessment Criteria:</b> {{{assessment|Not defined}}}</li>
<li><b>Action Items:</b>
<ul>
{{{actionitems|<li>None</li>}}}
</ul>
</li>
</ul>

{{LuxEarFooter}}

== Content ==
{{{content|<i>No content provided.</i>}}}

== Sources ==
{{{sources|<small>No sources cited.</small>}}}

</div>

Template:LuxEarHeader

2025-05-12T18:55:00Z

Scott: changed logo file

<div style="border-bottom: 2px solid #000; padding-bottom: 6px; margin-bottom: 10px;">
<div style="display: flex; align-items: center;">
[[File:Luxear square logo_150.png|150px|link=Main Page]]
<div style="font-size: 140%; font-weight: bold; padding-left: 20px;">
Lux-Ear Internal Knowledge Base
</div>
</div>
<div style="font-size: 85%; color: #666;">
<i>Authorized personnel only – Confidential Intellectual Property</i>
</div>
</div>

File:Luxear square logo.png

2025-05-12T18:53:02Z

Scott: Lux-Ear square logo 1024x1024

== Summary ==
Lux-Ear square logo 1024x1024

File:Luxear square logo 150.png

2025-05-12T18:48:56Z

Scott: Lux-Ear 150x150 square logo

== Summary ==
Lux-Ear 150x150 square logo

Main Page

2025-05-12T18:24:36Z

Scott: changed page to categorical order

== Lux-Ear Go-To-Market Pages ==

=== 1. Overview ===
* [[Executive Summary]]
* [[Market Overview]]
* [[GTM Strategy]]

=== 2. Technology ===
* [[Technology Platform]]
* [[Business Model]]
* [[Partnership Model Clarification]]

=== 3. Financials ===
* [[Revenue-Sharing Models]]
* [[Pricing Models]]
* [[Margin Analysis]]

=== 4. Operations and Partners ===
* [[Retailer and Brand Partner Outreach]]
* [[Marketing and Events]]
* [[Document Preparation]]

=== 5. Manufacturing and Logistics ===
* [[3D Printing Partners]]
* [[Established Ear-Tip Manufacturers]]
* [[Independent 3D Printing Facilities]]
* [[Local Delivery Services]]

=== 6. Hardware ===
* [[Ear Scanner Design and Manufacturing]]
* [[Components Bill of Materials (BOM)]]
* [[Potential Manufacturers]]
* [[3D Printing Equipment for Local Facilities]]
* [[Demonstration Systems for Funding]]
* [[BOM Elements Previously Mentioned]]
* [[Lux-Ear Ear Scanner Models]]
* [[Mobile Event Scanner]]
* [[Retail Kiosk Scanner]]

=== 7. Planning & Strategy ===
* [[Executive Summary (Bullet Points)]]
* [[Main Document: Lux-Ear Go-to-Market Plan]]
* [[Product Models]]
* [[Launch Plan]]
* [[Fulfillment Model]]
* [[Strategic Partnerships]]
* [[Hardware Overview]]
* [[Financial Considerations]]
* [[Milestones & Roadmap]]

Main Page

2025-05-12T17:23:03Z

Scott: This should contain links to all other pages

<strong>MediaWiki has been installed.</strong>

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Lux-Ear Go-To-Market Plan ==

=== 1. Overview ===
# [[Executive Summary]]
# [[Market Overview]]
# [[GTM Strategy]]

=== 2. Technology ===
# [[Technology Platform]]
# [[Business Model]]
# [[Partnership Model Clarification]]

=== 3. Financials ===
# [[Revenue-Sharing Models]]
# [[Pricing Models]]
# [[Margin Analysis]]

=== 4. Operations and Partners ===
# [[Retailer and Brand Partner Outreach]]
# [[Marketing and Events]]
# [[Document Preparation]]

=== 5. Manufacturing and Logistics ===
# [[3D Printing Partners]]
# [[Established Ear-Tip Manufacturers]]
# [[Independent 3D Printing Facilities]]
# [[Local Delivery Services]]

=== 6. Hardware ===
# [[Ear Scanner Design and Manufacturing]]
# [[Components Bill of Materials (BOM)]]
# [[Potential Manufacturers]]
# [[3D Printing Equipment for Local Facilities]]
# [[Demonstration Systems for Funding]]
# [[BOM Elements Previously Mentioned]]
# [[Lux-Ear Ear Scanner Models]]
# [[Mobile Event Scanner]]
# [[Retail Kiosk Scanner]]

=== 7. Planning & Strategy ===
# [[Executive Summary (Bullet Points)]]
# [[Main Document: Lux-Ear Go-to-Market Plan]]
# [[Product Models]]
# [[Launch Plan]]
# [[Fulfillment Model]]
# [[Strategic Partnerships]]
# [[Hardware Overview]]
# [[Financial Considerations]]
# [[Milestones & Roadmap]]

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

Template:LuxEarHeader

2025-05-12T08:59:25Z

Scott: changed logo

<div style="border-bottom: 2px solid #000; padding-bottom: 6px; margin-bottom: 10px;">
<div style="display: flex; align-items: center;">
[[File:luxear_square_logo_150.png|150px|link=Main Page]]
<div style="font-size: 140%; font-weight: bold; padding-left: 20px;">
Lux-Ear Internal Knowledge Base
</div>
</div>
<div style="font-size: 85%; color: #666;">
<i>Authorized personnel only – Confidential Intellectual Property</i>
</div>
</div>

Template:LuxEarHeader

2025-05-12T08:51:36Z

Scott: changed logo

<div style="border-bottom: 2px solid #000; padding-bottom: 6px; margin-bottom: 10px;">
<div style="display: flex; align-items: center;">
[[File:luxear_square_logo.png|150px|link=Main Page]]
<div style="font-size: 140%; font-weight: bold; padding-left: 20px;">
Lux-Ear Internal Knowledge Base
</div>
</div>
<div style="font-size: 85%; color: #666;">
<i>Authorized personnel only – Confidential Intellectual Property</i>
</div>
</div>

Template:LuxEarHeader

2025-05-12T07:43:07Z

Scott:

<div style="border-bottom: 2px solid #000; padding-bottom: 6px; margin-bottom: 10px;">
<div style="display: flex; align-items: center;">
[[File:luxear_square_logo.svg|150px|link=Main Page]]
<div style="font-size: 140%; font-weight: bold; padding-left: 20px;">
Lux-Ear Internal Knowledge Base
</div>
</div>
<div style="font-size: 85%; color: #666;">
<i>Authorized personnel only – Confidential Intellectual Property</i>
</div>
</div>

Template:LuxEarFooter

2025-05-11T07:21:02Z

Scott: Lux-Ear Footer

<div style="border-top: 1px solid #ccc; padding-top: 8px; font-size: 80%; color: #777; text-align: center; margin-top: 30px;">
Lux-Ear Company Confidential — Internal Use Only<br />
[[Main Page]] • [[Special:RecentChanges|Recent Changes]] • [[Special:AllPages|All Pages]]
</div>

Template:LuxEarHeader

2025-05-11T07:15:38Z

Scott: Llux-Ear Header

<div style="border-bottom: 2px solid #000; padding-bottom: 6px; margin-bottom: 10px;">
<div style="display: flex; align-items: center;">
[[File:Lux-ear_logo_wordmark.svg|150px|link=Main Page]]
<div style="font-size: 140%; font-weight: bold; padding-left: 20px;">
Lux-Ear Internal Knowledge Base
</div>
</div>
<div style="font-size: 85%; color: #666;">
<i>Authorized personnel only – Confidential Intellectual Property</i>
</div>
</div>

Template:LuxEarPage

2025-05-11T07:09:51Z

Scott: Template:LuxEarPage

<div class="luxear-page">

== Summary ==
<ul>
<li><b>Author:</b> {{{author|}}}</li>
<li><b>Start Date:</b> {{{start|Not set}}}</li>
<li><b>Due Date:</b> {{{due|Not set}}}</li>
<li><b>Assessment Criteria:</b> {{{assessment|Not defined}}}</li>
<li><b>Action Items:</b>
<ul>
{{{actionitems|<li>None</li>}}}
</ul>
</li>
</ul>

== Content ==
{{{content|<i>No content provided.</i>}}}

== Sources ==
{{{sources|<small>No sources cited.</small>}}}

</div>

Template:LuxEarPage

2025-05-11T07:04:29Z

Scott: Template:LuxEarPage

<div class="luxear-page">

== Summary ==
* '''Author:''' {{{author|}}}
* '''Action Items:''' {{{actionitems|None}}}
* '''Start Date:''' {{{start|Not set}}}
* '''Due Date:''' {{{due|Not set}}}
* '''Assessment Criteria:''' {{{assessment|Not defined}}}

== Content ==
{{{content|No content provided.}}}

== Sources ==
{{{sources|<small>No sources cited.</small>}}}

</div>