Product observations
Application observations and selected first-party release records from 17–18 October. This page does not represent a fresh operational audit.
Trust & transparency
Public evidence.
Clear boundaries.
A claim should have a source, a date and a defined scope. This is where to inspect the public records behind LUMA Quant.
Know what you are looking at
Different records.
Different questions.
Product observations describe an application at a particular time. A public source snapshot describes a bounded code release. Neither, on its own, certifies the whole production system.
Public component baseline
Six bounded component snapshots, with exact source bindings and dated check results. Separate from current production applications.
Product observations · 19 October
Three entry points.
These descriptions retain the dates and limits of the published record. For present offers and access requirements, check the application itself.
Research & analysis
AI Platform
The October record confirms a public application response. Authenticated features and credit redemption were not revalidated by that documentation update.
Open AI Platform ↗Cooperative play
Playground
LUMA Rooms was described as two-player co-op in English and German, with missions, quizzes, word groups, clue puzzles, estimate rounds and optional duels.
The recorded access check required a finalized wallet holding of at least 3,787.878787 LUMA. In that recorded release, playing did not spend LUMA; game points had no token or cash value.
Open Playground ↗Utility & community
Token & NFTs
The October record reports enabled checkout and optional NFT-mint configurations. Each spending or minting action needs its own explicit approval.
Open Token & NFTs ↗Source: 19 October product status and observation scope. Availability and offers can change.
Recorded product functions
Understand each action.
Configuration readiness is not proof that every payment, mint, delivery or redemption will succeed.
Token checkout & delivery
The 19 October public configuration enabled USDC checkout and reported LUMA wallet delivery as ready. Check the current offer for the payment amount and token delivery before approval.
The status update did not perform a new purchase or revalidate payment finality and delivery transactions.
View the current checkout configuration ↗Forge visuals & optional NFTs
The 18 October Forge release generates three static previews. Saving a visual and minting an on-chain NFT are separate actions. That recorded release does not charge the user for Forge generation.
Optional minting is enabled in the recorded Solana Mainnet configuration. It requires separate wallet approval and variable SOL mint and network costs. Visual uniqueness, collection visibility and irreversible metadata freezing are not guaranteed.
Explore NFT Forge ↗LUMAKeys & AI credits
The dated key release supports independent credit codes without requiring a wallet-to-AI-account link. Buying a LUMAKey spends LUMA; redeeming its code for credits is a separate action.
Check the current price and credit amount before approval. Historical purchase assignments are not themselves redeemable codes. A new purchase-and-redemption flow was not revalidated for the status report.
View LUMAKeys ↗Ongoing development
Additional token uses, integrations and research applications remain development work until a specific release describes them as available. Questions and product feedback are welcome on Discord; security reports have a separate private contact below.
Join the discussion ↗Function descriptions and limits: dated product and release summary.
Recorded checks · not a live dashboard
Evidence within its scope.
The following table describes the published status record. It does not turn historical checks into new certifications.
| Record | What the source reports | Boundary |
|---|---|---|
| Repository inventory | Six public component repositories and the central Master Index. | Component heads matched the August release bindings. |
| Master Index checks | Index and status validation, tests and a full-history Gitleaks scan passed. | 19 October workflow ↗ |
| Component CI | The latest recorded run per workflow succeeded at the bound heads. | August runs, except the AI frontend's scheduled CodeQL run on 12 October. |
| CodeQL readback | Zero open alerts recorded across the six public reference repositories. | The Master Index has no CodeQL analysis. This is not a new scan of private production code. |
| Legal review | Recorded as open in the August index. | The October update establishes neither completion nor regulatory approval. |
| Independent audit | No completed independent third-party platform audit established. | No audit opinion is claimed. |
| Prospective E4 evidence | A separate commitment-and-reveal milestone. | Completion is not established by the update. |
| Reference-package actions | Real payments and automatic token delivery disabled in the public reference packages. | Historical package flags do not describe current live-product switches. |
Six bounded public components
Inspect the source.
These August snapshots are not verified mirrors of today's production. Public visibility does not change each repository's stated licence.
| Component | Scope | Reference date |
|---|---|---|
| Engine Evidence ↗ | Selected development history, contracts and verification records. The proprietary production engine is outside this public boundary. | 13 Aug 2026 baseline |
| AI Frontend ↗ | A sanitised frontend snapshot with build and test evidence. Complete parity with the current authenticated application is not established. | 13 Aug 2026 baseline |
| Token Portal ↗ | A reference portal and dated token facts. This package does not execute live payments, token delivery, NFT mints or key redemption. | 13 Aug 2026 baseline |
| Platform API ↗ | A limited executable reference adapter and public API contract. It does not publish or certify the proprietary production backend. | 13 Aug 2026 baseline |
| Corporate Site ↗ | The published corporate-site candidate and its validation boundary. Subsequent website updates are not proof of deployment parity. | 13 Aug 2026 baseline |
| GitHub Profile ↗ | Navigation and an overview of the official public repository landscape. Subsequent product observations belong to the Master Index. | 13 Aug 2026 baseline |
A practical verification path
From claim to source.
01 · Identify
What kind of claim?
Use product-status records for runtime observations and release descriptions. Use the component index for source-code claims.
02 · Locate
Which version and date?
Read the exact commit, observation time and manifest. Historical packages do not establish current production behaviour.
03 · Evaluate
What was actually checked?
Inspect the workflow, source boundary and validation scope. Automated checks, configuration readiness and independent assurance are different kinds of evidence.
Technical transparency has limits.
The linked records do not establish legal or regulatory approval, a completed independent platform audit, predictive or financial guarantees, complete publication of proprietary code, current production parity, success of every transaction, guaranteed NFT uniqueness or rights clearance, or completion of the prospective E4 milestone.
Responsible reporting
Keep security
reports private.
Use the dedicated contact for vulnerabilities or security concerns. Never post credentials, redemption codes or wallet secrets in community channels.
The owner record attests that the mailbox is active, monitored and has received a test message. Independent mailbox verification and a response-time SLA are not claimed.