█   █  ███  ████  ████   ███  █   █ ████   ███  ████  ████
██ ██ █   █ █   █ █   █ █   █ ██  █ █   █ █   █     █ █   █
█ █ █ █████ █   █ ████  █████ █ █ █ █   █ █████  ███  █   █
█   █ █   █ █   █ █     █   █ █  ██ █   █ █   █     █ █   █
█   █ █   █ ████  █     █   █ █   █ ████  █   █ ████  ████

        SYSTEMS ONLINE // HUMAN AT THE CONTROLS

Founder · Systems Architect · U.S. Marine Corps Veteran · Cybersecurity Student
_{I turn scattered tools into owned, observable systems that do real work.}

leo@madpanda3d:~$ mission
Build the system I could not find.

leo@madpanda3d:~$ operating_model
AI expands execution bandwidth.
Judgment, ownership, and verification stay human.

leo@madpanda3d:~$ status
Founder mode: active.
Systems: online.
Work: compounding.

I did not arrive at software through a straight line.

I spent four years as an Aircraft Rescue Firefighter in the U.S. Marine Corps, then moved into telecom emergency-response and break/fix work supporting T-Mobile. That path eventually led to nearly two years in an AWS engineering role.

Every chapter taught me the same lesson:

A system is only impressive if it keeps working when conditions stop being ideal.

In early 2024, a 3D printer turned a long-running idea into MADPANDA3D. What began with 3D design and early commissions expanded into web development, Linux, cybersecurity, network defense, automation, private-cloud infrastructure, and agentic systems.

Today I run MADPANDA3D as a veteran-owned technology agency and operate as a solo systems architect with an AI agent stack around me. I do not use AI to avoid thinking. I use it to increase execution bandwidth across research, design, engineering, QA, deployment, documentation, and operations—while keeping a human accountable at every important boundary.

I am also enrolled in National University’s Cybersecurity program. The deeper I go into security, infrastructure, business, and the human side of systems, the more convinced I become that the real work is integration: connecting the parts, making state visible, and leaving behind something another person can actually operate.

MADPANDA3D is not a collection of disconnected experiments. The long-term mission is one owned operating stack.

flowchart TB
    L["LEO / operator"] --> M["MADPANDA3D / one operating stack"]

    M --> P["Products + marketplaces"]
    M --> A["Agentic systems + MCP"]
    M --> I["Private cloud + observability"]
    M --> B["CRM + automation + client delivery"]

    P --> K["Filesystem-first knowledge + memory"]
    A --> K
    I --> K
    B --> K

    classDef core fill:#0B1120,stroke:#E11D48,color:#FFFFFF,stroke-width:2px;
    classDef lane fill:#111827,stroke:#22D3EE,color:#FFFFFF;
    classDef knowledge fill:#111827,stroke:#F59E0B,color:#FFFFFF;

    class L,M core;
    class P,A,I,B lane;
    class K knowledge;

Some of my most ambitious work is private by design. These descriptions show the problems I am solving without exposing the infrastructure behind them.

The public lab also includes HOSTINGER-MCP, CF-MCP, GOOGLE-MCP, ARCH-KITTY-CONFIG, and HYPRLAND-THEMES.

• Own the stack. Critical workflows should be understandable, observable, replaceable, and under operator control.
• AI needs boundaries. Specialized agents get scoped tools, explicit routes, and human approval at high-risk edges.
• Reliability beats theater. Dry runs, tests, health checks, logs, readback, rollback paths, and honest failure states are product features.
• Build from the root cause. One fix at the shared boundary is better than patches scattered across every caller.
• Knowledge should compound. Decisions and evidence belong in durable systems—not trapped inside one chat, dashboard, or person’s memory.
• Ship the smallest complete unit. Working, verified, and maintainable beats impressive-looking complexity.

I work best on problems that cross boundaries:

• product + automation
• AI agents + governed tools
• software + infrastructure
• CRM + web + operations
• private cloud + observability
• scattered knowledge + one source of truth

I especially care about helping small businesses and veteran entrepreneurs gain ownership of their technology instead of inheriting another pile of subscriptions.

If your current stack is five tools, three spreadsheets, two automations, and no trusted source of truth, that is exactly my kind of problem.

BUILD THE SYSTEM // OBSERVE THE SYSTEM // OWN THE SYSTEM
_{MADNESS, DISCIPLINE & PANDA POWER.}