Lucio Durán
Technology director and product architect
22+ years architecting and shipping software products across healthcare, e-commerce, and marketplace verticals, from system design to production deployment. I lead engineering organizations where AI is not a feature but the core infrastructure layer. My work spans agentic AI systems, LLM integration patterns, full-stack development (React, React Native, Node, Python, iOS), and the strategic decisions that turn technical capabilities into revenue. I've built and scaled cross-functional teams across LATAM, the US, and Europe, owning the full product lifecycle: architecture decisions, CI/CD pipelines, cloud infrastructure, API design, and frontend performance. I operate at the intersection of hands-on engineering and executive technology strategy, I still read the PRs, and I still make the technical calls. Current focus: AI-augmented product development, agentic workflows, and building technology that compounds.
Featured projects
Citable Publication
Deterministic HTML, Markdown and JSON publishing from one corpus, with integrity verification before release and reproducible faults.
RAG Evaluation Workbench
Reproducible RAG evaluation with BM25, dense and hybrid retrieval, local CPU inference, and separate retrieval and answer metrics.
Agent Replay Runtime
Durable tool execution with event replay, idempotency keys and recovery after real process crashes. Includes effect traces and cases that stop instead of retrying automatically.
Agent Injection Evals
Reproducible prompt-injection evaluation with a pinned local model, simulated tools and separate metrics for task capability, attack attempts and realized effects.
MCP Contract Harness
Read-only MCP server and independent clients for checking stdio negotiation, pagination, errors and cancellation, with actual wire messages and reproducible reports.
LLM Serving Bench
CPU inference measured over HTTP/SSE: per-token arrivals, TTFT, TPOT, latency and memory. Eight SmolLM2 configurations with raw evidence and offline replay.
Citation Grounding Checker
Citation support checking with rules, FLAN-T5 and DeBERTa NLI. Predictions, abstentions and precision linked to each claim’s exact source passage.
Chunking Ablation Suite
Fixed, structural and semantic chunking ablations using the same MiniLM model. Measures complete retrieved evidence and indexing cost for code, tables and cross references.
Vector Search Portability
Real hnswlib and sqlite-vec comparison with identical vectors, filters and updates. Recall against exact search, concurrent read load and postfilter result loss.
Reranker Budget Router
Reranking router with hard pair budgets, development-fitted policies and a local MiniLM cross-encoder. Publishes quality, latency, decisions and routing errors.
Contents
Experience
Roles, companies, responsibilities and contributions.
Expertise
Areas of work, experience and related technologies, with individual records and references.
Education
Courses, institutions and credential links.
Biography
Career and personal history.
Blog
Technical publications, ordered by date.
Projects
Public software, source code and reproducible results.
Architecture decisions
Architectural context, decisions and consequences.
CV
Complete curriculum vitae, with print support.
Contact
Contact information and public profiles.
Complete index
Every page, including individual records.
Content access
Formats, sources and how this site works.
Privacy
Privacy policy.
Links
Built for machine reading
44 implemented controls help agents discover, retrieve and cite my content. Each control links to its implementation or technical documentation.
01 / Discovery06 controls
- Implemented: D01Public crawling
robots.txt allows public content and advertises the sitemap. robots.txt
- Implemented: D02XML publication map
The sitemap is built from the published catalog, including individual records. Sitemap
- Implemented: D03Index without JavaScript
Every page has an HTML link in an index organized by content kind. HTML
- Implemented: D04Paginated JSON catalog
Canonical URLs, kinds, languages, available dates and representation links. HTTP / JSON
- Implemented: D05llms.txt guide
Index for clients using this proposal. Generated from the same catalog. llms.txt
- Implemented: D06Discovery on every page
HTML and Link headers advertise alternate formats and the API catalog. HTML / Link
02 / Content and representations07 controls
- Implemented: F01Server-delivered content
Main text is in the initial HTML response, before JavaScript runs. HTML
- Implemented: F02Markdown by URL
Every page supports .md. The English root uses /index.md. Markdown
- Implemented: F03JSON by URL
Content, headings, sections, links, language and structured data in one document. HTTP / JSON
- Implemented: F04HTTP content negotiation
Accept selects explicit Markdown or JSON; Vary: Accept separates representations. Accept / Vary
- Implemented: F05One source for three formats
Markdown and JSON derive from HTML main, without a separate biography for bots. HTTP / JSON
- Implemented: F06Structure preserved
Lists, tables, code, links and image references survive serialization. Markdown
- Implemented: F07Decoration excluded from content
Navigation, controls and decorative seals are excluded from Markdown and JSON. HTTP / JSON
03 / Identity, attribution and citations06 controls
- Implemented: C01Canonical document URLs
HTML, Markdown, JSON and search results refer to the same publication. HTTP / JSON
- Implemented: C02Anchored sections
Headings have identifiers for linking a specific passage. HTTP / JSON
- Implemented: C03Consistent identity
Person uses a stable identifier and links to the author’s public profiles. JSON-LD
- Implemented: C04Content-specific structured data
Profile, articles, projects and credentials publish structured data alongside visible text. JSON-LD
- Implemented: C05Declared author and dates
Articles identify the author and preserve available publication and modification dates. JSON Feed
- Implemented: C06Project evidence and limitations
Projects link repositories, revisions and published results with their scope. Fuentes / Sources
04 / Retrieval and context05 controls
- Implemented: R01Search over published text
BM25 searches passages extracted from build HTML. Scores measure lexical relevance. HTTP / JSON
- Implemented: R02Explicit filters and pagination
Language, kind, offset, limit and next support bounded, repeatable traversal. HTTP / JSON
- Implemented: R03Results with citations and versions
Every result includes an excerpt, citationUrl and the indexed document’s contentHash. HTTP / JSON
- Implemented: R04Read individual sections
section selects a heading and its subsections, with its own hash and source hash. HTTP / JSON
- Implemented: R05MCP context windows
Reading supports limits and continuation by Unicode characters. The hash identifies the complete source. MCP
05 / Contracts and interfaces05 controls
- Implemented: I01RFC 9727 API catalog
A Linkset advertises endpoints and links their contracts and documentation. Linkset
- Implemented: I02OpenAPI 3.1 contract
Operations, parameters, limits, responses and errors are documented for HTTP clients. OpenAPI
- Implemented: I03Document and passage JSON Schema
The two response types have distinct schemas and a describedby header. JSON Schema
- Implemented: I04Read-only MCP
Tools to list, search and read using the official SDK and HTTP transport without persistent sessions. MCP / HTTP
- Implemented: I05RFC 9457 structured errors
Document, search, catalog, inventory and feed APIs return problem+json for handled errors. Problem Details
06 / Freshness and integrity05 controls
- Implemented: V01SHA-256 content identity
Documents explain which fields are hashed. It identifies a version, not the truth of its claims. HTTP / JSON
- Implemented: V02Build inventory
Paginated URLs and hashes, collection version and generation time for comparing snapshots. HTTP / JSON
- Implemented: V03Conditional reads
ETag and If-None-Match allow 304 responses without retransmitting unchanged documents. ETag / 304
- Implemented: V04Metadata without a response body
HEAD is available on documents, search, catalog, inventory and feeds. HEAD
- Implemented: V05Publication feeds
JSON Feed and Atom include article text; RSS publishes summaries. Dates and links come from source files. JSON Feed / Atom / RSS
07 / Reading and access05 controls
- Implemented: A01Explicit languages
HTML declares the content language; JSON and document responses preserve it. HTTP / JSON
- Implemented: A02Linked EN and ES versions
hreflang links available versions and declares x-default. HTML head
- Implemented: A03Native HTML semantics
main, headings, lists, tables and links express the content structure. HTML
- Implemented: A04Photo references, decorative seals
Photos are retained. Project seals are empty elements with aria-hidden. HTML / aria-hidden
- Implemented: A05Public APIs without sessions
HTTP read APIs support CORS and OPTIONS. No account, cookies or key required. CORS / OPTIONS
08 / Consistency and boundaries05 controls
- Implemented: B01Versioned profile
Pages and APIs use the same versioned professional profile snapshot. HTTP / JSON
- Implemented: B02Index generated from HTML
The build rejects missing or duplicate heading anchors and expected pages absent from the index. Build
- Implemented: B03Site-scoped reading
The reader accepts known public paths and bounds source size, time and redirects. Contrato / Contract
- Implemented: B04Content treated as source material
MCP tools identify document text as untrusted material for agent instructions. MCP instructions
- Implemented: B05Machine-readable checklist
This list and its JSON use the same registry. Each control has an identifier and evidence link. HTTP / JSON