Concepts, prototypes, and active work are labeled separately.

Work ledger

Ambition, with the labels left on.

This page separates what Lumilia can responsibly offer now from work under development and ideas that still need engineering, customer, safety, or market proof.

Status legend

Words mean something here.

The label describes the maturity of the work, not its importance or potential.

Active

Ready to discuss

A present capability with a bounded scope. Specific availability and fit still require confirmation.

Working prototype

Built to learn

Some implementation exists and has been exercised in a defined setting. It is not automatically a supported customer product.

Concept

Not yet proved

An idea or design direction. No claim of production readiness, customer validation, funding, certification, or protected intellectual property.

Current ledger

What exists—and what it means.

Each entry names the useful truth and the boundary that keeps the claim responsible.

Active

Practical technology work

Lumilia can investigate a small-business or personal technology problem, map a workflow, identify risks, and define or build a focused next step.

Boundary: this is a capability statement, not a claim of a large consultancy, round-the-clock support organization, or certified security practice.

Working prototype

Lumilia Home Base

A private software implementation exists for organizing projects, operational context, and selected business records.

Boundary: it is an internal prototype, not a publicly launched product or proven multi-customer platform.

Working prototype

Repair and workspace tools

Internal software and browser-based prototypes have been built and tested for focused repair guidance and a garage digital-twin workflow.

Boundary: tests in a development environment do not establish commercial readiness, field accuracy, safety approval, or customer support.

In formation

Scanning and cabinet-making

A practical service direction is being defined around existing-condition scanning, cabinet workflow, repeatable measurement, and durable construction.

Boundary: no finished catalog, open order book, costed production system, or proven robotic factory is claimed.

Concept

Cabinet-production automation

The longer-range vision includes accessible automation that could help smaller makers produce accurately and repairably.

Boundary: this requires real engineering, guarding and safety review, cost modeling, customer discovery, interoperability work, and pilot evidence. It is not presented as invented, patented, funded, or operating.

Claim discipline

How a status moves forward.

  1. Write the claim

    State exactly what someone would need to believe.

  2. Name the evidence

    Point to the build, test, observation, customer input, or source that supports it.

  3. Record the limits

    Identify the environment, assumptions, failures, and questions that remain.

  4. Earn the next label

    Change the public status only when new evidence supports the change.

Useful scrutiny is welcome

Ask what is real.

If a claim is unclear, ask for its evidence or boundary. That is part of responsible work, not a distraction from it.