NIGEL ANDRÉ / ONE YEAR / BUILT IN PUBLIC

I build things, and break them, to understand how they really work.

I’m a finance and operations executive—CFO, Treasurer, and GM. My experience spans three industries—fleet leasing, distribution, and payments.

I spent a year putting AI to work across support, engineering, and reporting—different models, different applications—and building and stressing the infrastructure and networks underneath it to find where the boundaries hold.

This site is the record: the projects are the evidence, and the decisions, failures, and recoveries are what they taught.

Latest insights

View all insights →

The projects are evidence. The learning is the product.

The site is organized around decisions rather than technologies: what problem existed, what was known, what was assumed, where the boundary failed, and what became reusable afterward.

What that produces for a business is judgment in five places:

  • what AI and LLM systems can safely be trusted to do
  • engineered controls that sit in the operating path
  • audit transparency that survives inspection
  • stronger work across organizational and technical seams
  • a complete operating-model view of how decisions move through a business

SYSTEM MAP

See how the pieces connect.

The projects are connected by three recurring questions: where something runs, who may act, and what information moves.

ENVIRONMENT Where it runs Compute, network, identity, power, and recovery make the applications possible. Applications HomeLabRemote Arcade Hub Services Identity DNS Containers Storage Infrastructure Compute Network Power Recovery Applications What you use Services What they depend on Infrastructure What it runs on OPERATIONS Who may act Identity, permission, and delegation meet at the point where a decision becomes an action. Operator Team Automation Trust boundary HomeLabRemote Access and control Operator Confirmation Validate and authorize Policy • Audit • Accountability Systems Data Actions INFORMATION What moves Transport, retention, generation, and interpretation are separate boundaries. Capture iMessage Locker Transport Secure channels Retain Storage and policy Generate Processing and context Interpret The Quiet Governor Boundaries by design ACROSS ALL THREE SAME QUESTIONS. DIFFERENT ANGLES.

Explore the infrastructure →

The year in review

From isolated experiments to a connected operating system.

Foundations

Recovery is part of the design.

Running servers, virtualization, storage, backups, and power protection made one lesson concrete: resilience comes from recovery paths built before they are needed.

See compute and operations →

Network

A route is also a decision about authority.

Segmentation, DNS, VPNs, and remote access made boundaries visible: what may communicate, what resolves, who can enter, and where trust stops.

AI

Capability matters less without a boundary.

Local models and constrained prompts turned privacy into an operating choice: admit only what is needed, keep generation on the device, and leave the final action with the person.

See iMessage Locker →

Product

A working artifact sharpens the question.

Games, operating tools, and application prototypes converted abstract ideas into choices that could be used, inspected, rejected, and improved.

Explore the applications →

Mental models

The ideas that survived contact with reality.

Preserve options

Design the way back before it is needed.

Backups, high availability, short-lived credentials, explicit exclusions, and rollback paths serve the same purpose: they keep one bad assumption from becoming an irreversible decision.

See compute and operations →

Facts before answers

Confidence should follow evidence.

A passing build, a healthy container, and a documented design prove different things. Repository snapshots, source records, focused tests, live checks, and clearly labeled unknowns keep the conclusion inside the evidence.

Review the evidence records →

Boundaries create trust

A system earns trust by showing where it stops.

iMessage Locker keeps message access on demand and generation local. HomeLabRemote transports an approved request while PAM, SSSD, Polkit, and the host runner retain final authority. The boundary is part of the feature.

Handoffs reveal the system

The transfer is where ownership becomes visible.

Failures often collect between a plan and its execution, an application and a host, or a recommendation and the person acting on it. Naming the handoff reveals who owns the next decision and how the system recovers when it fails.

The point was never to know everything.

It was to become better at finding the boundary, testing the assumption, and building a path back when the first answer was wrong.

If that way of working is useful to you, the background is on the About page and I am glad to talk.

I let AI name the product suite. In retrospect, Blame Machine should have been a warning.