Technical portfolio · Andre Fitzgerald
I build systems that turn messy work into repeatable execution.
SignalRivet and BOSS were built independently over a concentrated period of weeks as working systems, not portfolio mockups. They combine IT administration, automation, process design, browser tooling, AI-assisted workflows, QA, documentation, and evidence-backed execution.
Selected work
Proof is more useful than a skills list.
These systems are live or documented in the SignalRivet build record. The emphasis changes by role, but the underlying work is the same: understand the problem, design the control surface, build the solution, and verify that it works.
BOSS control plane
Designed a durable orchestration layer that separates model reasoning from deterministic state, policy, task identity, replay safety, browser handoffs, and evidence receipts.
- Versioned command envelopes and allowlisted actions
- Exact task and batch scoping
- Durable receipts, recovery, and replay controls
- Compact operator state reduced one measured payload by 95.9%
Governed worker completion
Built a fail-closed completion architecture so a process exiting successfully cannot automatically claim the requested outcome was achieved.
- Structured completion contracts
- Machine-verifiable SOP companions
- Evidence and acceptance gates
- Explicit HOLD states when proof is missing
SignalRivet.com
Designed, built, iterated, and deployed the public SignalRivet product site as both a business surface and an operating interface.
- Astro + Netlify production site
- Operational review and document-input workflows
- Research notes, practical guides, and build chronicle
- Responsive UI, QA passes, accessibility, and production verification
Local execution infrastructure
Built a small-machine operating environment that combines deterministic software with AI workers, local execution, browser automation, task routing, and teardown discipline.
- Python and PowerShell automation
- SQLite, JSON, APIs, and local services
- Browser-driven workflows and file handling
- Resource-aware execution on constrained hardware
Execution density
A small environment can still operate with serious discipline.
I use automation to compress repetitive work, not to remove judgment. Research, drafting, coding, QA, browser execution, documentation, routing, and receipts can move through one connected workflow while consequential decisions remain explicit.
The result is higher execution density: more useful work can move through a small operating environment without pretending that every task needs AI or that every AI output is trustworthy by default.
"The technology underneath can be sophisticated. The experience of using it should not have to be."
Capability map
Where the work translates.
Systems that have to work
Windows administration, Microsoft 365, Active Directory, networking, troubleshooting, endpoint support, escalation, documentation, and root-cause thinking.
Repetitive work that should not stay repetitive
Python, PowerShell, APIs, JSON, SQLite, browser automation, workflow orchestration, structured data, and deterministic controls.
Fixes that have to stay fixed
SOPs, traceability, corrective action, QA gates, audit trails, process mapping, risk controls, verification, and continuous improvement.
Technical work people actually have to use
Astro, Netlify, responsive interfaces, forms, content systems, serverless workflows, iterative UX, deployment, and production QA.
Go deeper
The build record is public.
SignalRivet documents the architecture, failures, revisions, and operating principles behind the work. That record is intentionally more useful than a list of buzzwords.
For hiring teams and collaborators
If the work is relevant, I would rather show you the system than oversell it.
I am available for remote roles and technical work where systems thinking, troubleshooting, automation, process discipline, or cross-functional execution are useful.
Contact Andre