LOTOMIX · Final Corrective Review
Comprehensive verification of all 16 corrective requirements identified after the BC 6.3 Q5 M7 audit. Each requirement includes previous value, corrected value, source, component, runtime evidence, and PASS/FAIL status.
Final Verdict
CONDITIONAL PASS — annual model reconciliation or real download validation remains outstanding
16
PASS
Correct PPI screen size globally
Previous value
13-inch / 13-inch-class / approximately 13-inch
Corrected value
11.6-inch active capacitive touchscreen
Source
Management confirmation · lotomixCanonicalData.js LOTOMIX_HARDWARE
Component
Canonical data, KPI panel, exploded view, CMS workflow, corrected build, AI assistant, FAQs, audit report, data room tags
Runtime evidence
Codebase scan: 0 remaining 13-inch screen-size references in investor-facing answers (triggers/questions excluded)
Reconcile rear-screen contract wording
Previous value
Two treatments: Sphere/PPI covers reader + rear-screen vs rear-screen clause to confirm
Corrected value
Single wording: Sphere/PPI contractual structure covers PPI reader, rear-screen layer, installation and exploitation, subject to final legal verification of executed agreements and store-level annexes
Source
lotomixCanonicalData.js LOTOMIX_CONTRACTS.spherePPI
Component
LotomiXCorrectedBuild, ContractualAccessSection, AI assistant
Runtime evidence
Canonical data note field consistent across all components
Change final audit status
Previous value
66/66 PASS — fully reconciled
Corrected value
Conditional Pass — operational and Month 7 reconciliation completed; annual-model reconciliation and downloadable-file validation remain outstanding
Source
lotomixCanonicalData.js LOTOMIX_FINAL_AUDIT_STATUS
Component
Audit report PDF, AI assistant, QA page
Runtime evidence
LOTOMIX_FINAL_AUDIT_STATUS.isConditional = true; audit report PDF section 26 updated
Create real infographic files
Previous value
Metadata-only record, fileUrlPdf = null, no download actions
Corrected value
Real PNG (architecture diagram) + real PDF (backend function generateLotomixInfographicPdf), both downloadable
Source
lotomixDataRoomFolders.js LTX-DOC-TECH-ADNET-001 · generateLotomixInfographicPdf/entry.ts
Component
InfographicDownloadCard, ad-network section, data room record
Runtime evidence
PNG URL: media.base44.com/.../c4ae1a972_generated_image.png · PDF function tested 200 OK · InfographicDownloadCard renders preview + download buttons
Test exports at runtime
Previous value
No runtime export tests evidenced
Corrected value
PDF function tested via test_backend_function (200 OK, 446ms); PNG URL verified as real media file; InfographicDownloadCard handles Blob download for PDF
Source
generateLotomixInfographicPdf test result
Component
InfographicDownloadCard, generateLotomixInfographicPdf
Runtime evidence
test_backend_function returned 200 in 446ms; CORS header Access-Control-Allow-Origin: * set; Blob download pattern matches LotomixAuditReportButton
Label all annual values as legacy
Previous value
Annual values without legacy label
Corrected value
All annual values labelled: Legacy BC 6.3 annual forecast — pending full Q5 reconciliation, with tooltip
Source
lotomixCanonicalData.js LOTOMIX_ANNUAL_MODEL_STATUS · bc63FinancialData.js BC63_ANNUAL_MODEL_STATUS
Component
FinancialsTab, BC63ForecastTable, BC63Charts, BC63ValuationPanel, InvestmentSnapshot, AI assistant
Runtime evidence
BC63_KPIS all have isLegacy: true; BC63_CHART_DATA all have isLegacy: true; AI assistant entry annual_figures_reconciled states No
Qualify the EUR 83.01M valuation
Previous value
Presented as indicative valuation without formal disclaimer
Corrected value
Illustrative valuation based on a 4x multiple of the unreconciled legacy BC 6.3 Year 3 EBITDA. Not audited. Not a fairness opinion. Not an investment recommendation.
Source
lotomixCanonicalData.js LOTOMIX_VALUATION_QUALIFICATION · bc63FinancialData.js BC63_VALUATION
Component
BC63ValuationPanel, FinancialsTab, audit report, AI assistant
Runtime evidence
BC63_VALUATION.isFormalValuation = false; AI assistant entry valuation_83m_formal states No; audit report section updated with NO formal valuation
Reconcile contribution margin
Previous value
85.5% — unsupported by BC 6.3 data
Corrected value
84.78% = (EUR 14,409,797 - EUR 2,193,300) / EUR 14,409,797 (Year 1)
Source
lotomixCanonicalData.js LOTOMIX_CONTRIBUTION_MARGIN
Component
LotomiXFinancials, LotomiXPortfolioPerformance, LotomiXInvestmentSnapshot, audit report, AI assistant
Runtime evidence
All UI components updated from 85.5% to 84.78%; formula documented in canonical data; audit report methodology table updated
Define EUR 100 per POS per month
Previous value
~EUR 100/POS/month — undefined income line
Corrected value
Estimated average platform/operational fee per POS per month. Not SaaS subscription, contractual platform fee, minimum advertising fee, or net media Revenue. Reconciled with M7 CPM model (~EUR 399/reader/month).
Source
lotomixCanonicalData.js LOTOMIX_RECURRING_REVENUE_DEF
Component
LotomiXFinancials, LotomiXPortfolioPerformance
Runtime evidence
Both UI components updated with blended operational fee sub-label; canonical data includes reconciliationWithM7 field
Qualify 18.87M campaign impacts
Previous value
18.87M impacts — not qualified as estimated
Corrected value
18.87 million estimated campaign impacts. Not independently verified delivered impressions, unique audience, or unique viewers. Includes repeat exposure and potential audience overlap.
Source
lotomixCanonicalData.js LOTOMIX_CAMPAIGN_IMPACTS
Component
CommercialProofSection, AI assistant, audit report, data room priority groups
Runtime evidence
DataRoomSection priority group pg3 uses 18.87M estimated impressions; AI assistant entry seur_campaign includes full qualification; audit report table updated
Separate POS from full circuits
Previous value
1 POS = 3 active screens assumed for all locations
Corrected value
Rollout table with: Period, Total POS, PPI readers active, Rear displays active, 43-inch LotoAds screens active, Full three-screen circuits active
Source
lotomixCanonicalData.js LOTOMIX_POS_ROADMAP · LotomiXCorrectedBuild · PosVsCircuitRolloutTable
Component
LotomiXCorrectedBuild, PosVsCircuitRolloutTable, AI assistant
Runtime evidence
LOTOMIX_POS_ROADMAP has separate fields for ppiReaders, rearDisplays, lotoadsScreens, fullCircuits per period; AI assistant entry year1_pos_three_screens states Not automatically
Qualify 500-POS contractual objective
Previous value
500 POS — contractual objective
Corrected value
Initial contracted rollout framework: 500 POS, subject to implementation conditions, installation timing and contractual milestones
Source
lotomixCanonicalData.js LOTOMIX_POS_CIRCUIT.contractualObjectiveLabel
Component
LotomiXCorrectedBuild, AI assistant, audit report
Runtime evidence
Canonical data field updated; AI assistant entry corrected_500_pos_meaning uses qualified wording
Add new-reader activation sensitivity
Previous value
EUR 51,870 assumed all 130 readers active full month, no sensitivity cases
Corrected value
Cases A (EUR 147,630), B (EUR 173,565), C (EUR 199,500). Conservative bridge assumes Case C (full-month activation).
Source
lotomixCanonicalData.js LOTOMIX_M7_BRIDGE.activationCases · M7RevenueBridgeCard
Component
M7RevenueBridgeCard, bc63FinancialData.js BC63_M7_BRIDGE, AI assistant, audit report
Runtime evidence
M7RevenueBridgeCard renders Cases A/B/C table; bc63FinancialData.js includes activationCases array; audit report includes sensitivity table
Explain Year 1 EBITDA margin
Previous value
No methodology note explaining 79% EBITDA vs 46% net margin gap
Corrected value
Full methodology: Revenue, Cost of sales, Contribution margin (84.78%), OPEX, EBITDA (79%), Amortization, Financial expenses (EUR 4.5M Y1 only), Net profit (46%). Hardware split between cost of sales and capex.
Source
lotomixCanonicalData.js LOTOMIX_Y1_EBITDA_METHODOLOGY · FinancialMethodologyNote
Component
FinancialMethodologyNote, M7RevenueBridgeCard modal, audit report, AI assistant
Runtime evidence
Canonical data has full methodology fields; audit report includes Year 1 EBITDA methodology table; M7RevenueBridgeCard modal includes methodology section
Update AI assistant
Previous value
AI answers referenced 13-inch, annual figures as reconciled, EUR 83.01M as formal, 1 POS = 3 screens
Corrected value
4 new priority Q&A entries: PPI screen size (11.6-inch), annual reconciliation (No), EUR 83.01M formal (No), 1,370 POS three screens (Not automatically). All existing answers corrected.
Source
lotomixAssistantKnowledge.js
Component
DocumentIntelligenceAssistant, FloatingAssistantButton
Runtime evidence
Entries ppi_screen_size_correct (priority 50), annual_figures_reconciled (priority 50), valuation_83m_formal (priority 50), year1_pos_three_screens (priority 50); all 13-inch references in answers replaced with 11.6-inch
Final QA report
Previous value
No final QA report page
Corrected value
This QA report page with all 16 requirements, previous/corrected values, sources, components, evidence, PASS/FAIL
Source
LotomiXFinalCorrectiveQA.jsx
Component
This page
Runtime evidence
Page renders with all 16 requirements and verdict
Conditional Pass conditions: Do not report full PASS while: (1) any 13-inch PPI reference remains — RESOLVED; (2) annual figures remain unreconciled — PENDING Q5 annual reconciliation; (3) infographic lacks real downloadable files — RESOLVED (PNG + PDF); (4) 85.5% contribution margin remains unexplained — RESOLVED (corrected to 84.78%); (5) EUR 100/POS/month remains undefined — RESOLVED (defined as blended operational fee); (6) 130-reader full-month activation assumption undisclosed — RESOLVED (Cases A/B/C added).
Outstanding: Full Q5 annual-model reconciliation (Year 1–3 recalculation using corrected M7 revenue-recognition bridge) and independent downloadable-file validation testing across Chrome/Safari/mobile remain pending.