AI Agent · Platform · Full-stack Engineering

Engineering work designed to be verified.

I design, build, and deploy AI agents and product systems across model/runtime integration, bounded tool execution, backend and web boundaries, infrastructure, and release evidence.

Current focus
Released AI systems and bounded local operations
Operating model
Evidence, contracts, automation, and recovery
Location
Rome, Italy

Selected engineering work

Four projects. Four distinct proof domains.

Each project owns one technical narrative. Shared standards apply across the portfolio, but featured status requires project-specific evidence.

v1.0.0 released · reproducible evidence

Prompt Enhancer

A local-first intent compiler with provider contracts, authenticated protocol boundaries, deterministic fallback, a 64-case corpus, and checksummed release evidence.

Review the engineering case
Public alpha · host execution explicitly bounded

SysOps Agent

A local-first operations agent with fail-closed classification, bounded commands, verification predicates, recovery loops, and redacted audit trails.

Review the engineering case
2.0 release candidate · external gates pending

AutoBlog CMS

A durable editorial product with database sessions, workspace RBAC, immutable revisions, optimistic concurrency, leased jobs, and bounded media/AI operations.

Review the engineering case
Main CI + security green · operator-managed

Authenticated Privacy Proxy

A containerized Mitmproxy–Privoxy–Tor chain with authenticated ingress, policy controls, DNSSEC-aware resolution, and portable host automation.

Review the engineering case

Operating principles

Professionalism is an evidence chain.

Architecture, product behavior, security, CI, deployment, and documentation must describe the same system.

01 / Claims

Evidence before adjectives

Metrics include their workload, environment, method, date, and reproduction command.

02 / Architecture

Contracts before providers

Cloud, data, storage, identity, queue, and AI vendors terminate at tested adapters.

03 / Operations

Failure is product behavior

Timeouts, retries, idempotency, migration, recovery, and rollback are designed explicitly.

DeployOps model

One artifact, progressively verified.

Portability comes from responsibility boundaries and contract tests, not duplicated application implementations for every provider.

  1. Source and tests
  2. Immutable artifact
  3. Provider adapters
  4. Ephemeral verification
  5. Observe and roll back
Deployment claims are tiered.

Reproducible, container-portable, platform-portable, provider-portable, and operationally verified are separate claims with separate evidence.

Technical discussion and opportunities

Start with the evidence.

Review the project cases, inspect the repositories, or contact me about engineering roles and product collaboration.