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

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>