Adrian LopezWork built to serve

Catholic / Husband / Father / Marine veteran / Systems administrator / Builder

Build what serves.
Make it last.

I am Adrian Lopez. My Catholic faith shapes the work I choose: practical systems, honest craftsmanship, and repairable products that leave people more capable than I found them.

Explore the workRead the full manifesto
WORKSHOP LEDGEREST. IN SERVICE
01
PURPOSEHonor God by serving people well.
02
STANDARDBuy once. Understand it. Repair it.
03
METHODStart simple. Test honestly. Earn the next step.

Sometimes progress is a better machine. Sometimes it is a circular saw on a true track.

The truth key

Evidence before adjectives.

Working prototype

A functioning artifact exists and has been checked locally.

In formation

Active work exists, but the offer or proof is not complete.

Reported build

Part of my history, with supporting documentation still needed.

Proposed

A documented direction, not a finished product or promise.

My story

One thread connects the server room and the cabinet shop.

I have learned to look for the system behind the problem.

Sometimes the work is restoring order to technology. Sometimes it is building a cabinet, a jig, a prototype, or a decision system that another person can understand and maintain.

My instinct is to see the connected possibilities. My discipline is to ask a smaller question: what is the most honest next step that can serve someone now?

I am Catholic, a husband, father, Marine veteran, systems administrator, and hands-on builder. Those are not marketing categories. They are responsibilities that shape how I think about truth, stewardship, work, and the people who depend on it.

The build sequence

A large vision, held to a staged path.

NOWWorking software and service definition

Prove usefulness with prototypes, clear offers, and real conversations.

NEXTScanning and cabinet pilots

Deliver one bounded service well, document it, and learn from the work.

LATERRepairable tooling and production cells

Use qualified partners, safety gates, and measurable manufacturing proof.

HORIZONDistributed manufacturing and energy

Expand only when engineering, demand, safety, and economics earn it.

The project ledger

What exists. What is forming. What comes later.

Each entry names the evidence and the next honest step. The status matters as much as the idea.

PROJECT 01Working prototype

WorkTrade Local

A responsive, offline prototype exploring clearly scoped local work paid with cash, an agreed service, or a mix.

EVIDENCE

A functioning fictional-data prototype, desktop and mobile views, a written proposal, and automated browser checks exist.

BOUNDARY

It does not create accounts, send messages, collect money, form contracts, or represent a live marketplace.

NEXT HONEST STEP

Validate the problem with workers and customers, then complete legal, tax, identity, payment, privacy, and dispute review before any pilot.

WorkTrade Local fictional-data prototype shown on a desktop layoutWorkTrade Local fictional-data prototype shown on a phone layoutActual local prototype screenshots
PROJECT 02Working prototype

BuildRoster Local

A responsive, offline prototype for seeing job-ready provider profiles, sample checks, and the relationship between local demand and training.

EVIDENCE

A functioning fictional-data prototype, responsive screenshots, written decision material, and automated browser checks exist.

BOUNDARY

It performs no placement, credential verification, background check, licensing review, or real-world matching.

NEXT HONEST STEP

Interview employers, providers, and training programs to test which proof actually helps a hiring or work decision.

BuildRoster Local fictional-data prototype shown on a desktop layoutBuildRoster Local fictional-data prototype shown on a phone layoutActual local prototype screenshots
PROJECT 03Working prototype

Lumilia Home Base

An offline-first command center that keeps priorities, blockers, milestones, owners, and evidence close to the work.

WHAT EXISTS

A runnable local Expo MVP, product specification, typed project snapshot, and automated checks.

NEXT

Replace private development data with a fictional demo and design a safe import path before any public distribution.

PROJECT 04Working source prototype

Lumilia Approvals

A local software pattern for keeping a visible human decision between a proposed action and execution.

WHAT EXISTS

Mobile and local bridge source with a tested safety boundary.

NEXT

Create fictional public data and complete signed-device testing before presenting it as a deployable product.

PROJECT 05In formation

Scanning service

A scanning and digitization service line now being defined, intended to move a customer from careful intake to a clear quote, controlled work, review, and responsible return.

WHAT EXISTS

A starting brief and proposed privacy-first customer workflow. The first scanning modality has not been selected.

NEXT

Choose the first scanning offer, define its price and quality standard, and test the workflow using fictional materials.

PROJECT 06In formation

Cabinet service

A cabinet-work lane built around listening, measurement, clear approval, dependable fabrication, and an accountable handoff.

WHAT EXISTS

A starting brief and documented operating questions. No final offer, price, customer case study, or promised capacity exists.

NEXT

Select one bounded starter service and document the quoting, material, build, delivery, and aftercare standard.

PROJECT 07Reported prior build

College lap-board prototype

I report building a lap board by hand in college and later making a version with a gantry machine.

BOUNDARY

The build is part of my personal history, but photographs, drawings, dates, and disclosure records still need to be assembled.

NEXT

Document the artifact before making design, performance, or intellectual-property claims.

PROJECT 08Proposed

Repairable trades tooling

Begin with the simplest reliable interface: perhaps a familiar circular saw on an accurate track, with understandable parts and repeatable measurements.

TODAY

A product principle and proposed direction. No finished CAD, bill of materials, cost model, physical prototype, or safety record.

NEXT

Define one problem, one user, and one safe benchtop proof with a qualified engineering or manufacturing reviewer.

PROJECT 09Proposed

Cabinet production cell

A compact, integrated cell intended to cut, drill, label, and safely unload cabinet components for a smaller manufacturer.

TODAY

A non-confidential concept and draft technical material. No machine integration, physical prototype, validated throughput, or approved site.

NEXT

Begin with qualified integrators, proven commercial equipment, code review, guarding, dust control, and one measurable pilot.

PROJECT 10Long-range proposal

Mobile energy infrastructure

A deployable, two-level hub that could provide shade, stored power, and charging for vehicles, tools, or work sites.

TODAY

A documented aspiration. Engineering, prior art, safety, market, economics, code, and intellectual-property work remain open.

NEXT

Do not build this first. Earn the capability through smaller manufacturing and energy proofs.

The wider atlas

Additional systems on the path.

These projects complete the public map. Their order is deliberate: proof and service come before infrastructure.

PROJECT 11Working public framework

Adrian Decision Voice

A documented method for turning complex ideas into factual, humane, decision-ready communication while protecting dignity and ownership.

BOUNDARY

A public package exists. It is a communication framework, not evidence that an employer or outside organization has adopted it.

PROJECT 12Proposed

Build Passport and cabinet traceability

A vendor-neutral product record intended to connect a cabinet, its parts, repair instructions, replacement information, and lifecycle history.

BOUNDARY

No finished product, customer, costed specification, data standard, or pilot commitment exists.

PROJECT 13Proposed

Standardized cabinet starter product

One repeatable cabinet could become a test article for fit, actual cost, rework, component identity, repair instructions, and replacement-part lookup.

BOUNDARY

The product, materials, price, warranty, customer, and validation method are not selected.

PROJECT 14Proposed

Circular cabinet components

Explore recovered plastic or other circular materials for carefully selected, noncritical cabinet components.

BOUNDARY

No durability, structural, fire, sourcing, cost, or sustainability result has been established.

PROJECT 15Long-range proposal

Timber-to-cabinet microfactory network

A staged network connecting responsible material sourcing, local processing, modular production, installation, repair, and lifecycle records.

BOUNDARY

This is an aspirational architecture, not an operating supply chain or proven business model.

PROJECT 16Proposed

Indiana Trades Capacity Pilot

A bounded planning effort pairing the demonstrated workforce concepts with a separately scoped cabinet-tool feasibility track.

BOUNDARY

No host, partner, budget, cohort, government support, or outside endorsement is committed.

PROJECT 17Proposed

Community of Builders

A responsible, AI-assisted learning program where people define, prototype, test, document, and share lawful solutions.

BOUNDARY

It is not launched, accredited, funded, staffed, or outcome-tested.

PROJECT 18Parked proposal

Purpose-built trade vehicle

A later concept for modular trade bodies, protected material handling, repairable systems, and durable lifecycle records.

BOUNDARY

Supporting evidence is limited. It remains parked behind the service, tooling, and manufacturing proofs.

PUBLIC NOTE

Lumilia Tech and the project names on this page are working names. This portfolio does not claim incorporation, funding, patent protection, customer traction, safety certification, manufacturing partnerships, or endorsement by any person or organization.

The Steward's Workshop

Honor God. Serve people. Make what lasts.

I belong to the Lord God. My first purpose is to serve Him and glorify Him through the work of my hands, not through slogans or spectacle, but through truth, usefulness, stewardship, and care.

I will make things people can buy once, understand, maintain, repair, and pass down.

Read the full working manifesto

How I build

One useful thing, then the next.

  1. 01

    Listen

    Understand the real need before choosing the tool.

  2. 02

    Simplify

    Find the least complicated approach that can work well.

  3. 03

    Prototype

    Build the smallest honest version that can answer a question.

  4. 04

    Test

    Use real conditions, record failures, and make no promises beyond the evidence.

  5. 05

    Document

    Leave instructions, maintenance, ownership, and handoff clearer than before.

  6. 06

    Earn scale

    Partner or expand only after the proof supports the next step.

Start with the problem

Let's build one useful thing.

If you need a clearer system, want to discuss scanning or cabinet work, or can help test responsible manufacturing, tell me the problem. We will begin with the smallest honest next step.

Email Adrian
01Scanning project02Cabinet project03Systems and operations04Engineering or manufacturing