Skip to content
View bart1208's full-sized avatar

Block or report bart1208

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
bart1208/README.md

Bartolomeo Pasquale

Software engineer. Twenty years of shipped production systems — public administration, enterprise, advertising, gaming, regulated betting. Now building the infrastructure that lets AI agents do real engineering work.

Both halves matter, and only together. "Twenty years of delivery" describes a senior generalist in a crowded market; "works with AI" is the most common and least verifiable claim on the internet in 2026. The uncommon part is the conjunction — someone who shipped a consular services portal for the Italian Ministry of Foreign Affairs, led the React front end of an enterprise ordering platform at Fujitsu, and spent six years inside regulated sports-betting data, and who now runs a self-hosted multi-agent system with version control, encrypted secrets, scheduled integrity checks and cross-machine deployment.

What I work on now

Agent infrastructure. One instruction layer, one memory store and one tool registry, shared by five different coding agents. MCP has no common configuration format, so the registry is the source of truth and each agent's config is generated from it.

Knowledge systems agents can be trusted with. A schema'd, git-versioned vault with typed pages, an enforced lifecycle, append-only operation logs, and a linter that runs on a timer. Agents write it; the linter is what keeps them honest.

Identity, credentials and secrets discipline. git-crypt for personal data, pointer-only credential documentation, per-machine credential activation tracked explicitly rather than assumed, and conventions written down after each way it went wrong rather than before.

Self-hosting. A Hetzner VPS running the *.fenrir.it services on plain systemd — no Docker, no PaaS, no managed anything.

Public work

  • linkedin-portability — read your own LinkedIn data from the command line through the EU Digital Markets Act portability API. The README covers what the official documentation leaves out: API version pinning, pagination that cannot be trusted, and why the Snapshot endpoint is not a live read of your profile while the Changelog is.
  • fenrir.it — personal site and manifesto. Hand-written, trilingual, no framework and no build step. Source.

Elsewhere

Based in Sevilla. Italian native, Spanish and English at professional working proficiency.

fenrir.it · LinkedIn

Popular repositories Loading

  1. fenrir.it fenrir.it Public

    Personal site and manifesto at fenrir.it — hand-written trilingual static HTML, no framework, no build step

    HTML

  2. linkedin-portability linkedin-portability Public

    Read your own LinkedIn data from the CLI via the EU Digital Markets Act portability API

    Shell

  3. bart1208 bart1208 Public

    GitHub profile README

  4. brain-mcp brain-mcp Public

    MCP resource server over a personal knowledge vault: OAuth 2.1, RFC 9728, RFC 8707 audience-bound tokens, scopes derived from git-crypt classification

    Go