Lucio Durán

Technology director and product architect

Chief Technology Officer · LOi · San José de Mayo · Uruguay

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.

All projects

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.

Publication system / checklistHTML / MD / JSON

Built for machine reading

44 implemented controls help agents discover, retrieve and cite my content. Each control links to its implementation or technical documentation.

44 controls / 08 areasEN / ES

01 / Discovery06 controls

  • Implemented: D01
    Public crawling

    robots.txt allows public content and advertises the sitemap. robots.txt

  • Implemented: D02
    XML publication map

    The sitemap is built from the published catalog, including individual records. Sitemap

  • Implemented: D03
    Index without JavaScript

    Every page has an HTML link in an index organized by content kind. HTML

  • Implemented: D04
    Paginated JSON catalog

    Canonical URLs, kinds, languages, available dates and representation links. HTTP / JSON

  • Implemented: D05
    llms.txt guide

    Index for clients using this proposal. Generated from the same catalog. llms.txt

  • Implemented: D06
    Discovery on every page

    HTML and Link headers advertise alternate formats and the API catalog. HTML / Link

02 / Content and representations07 controls

  • Implemented: F01
    Server-delivered content

    Main text is in the initial HTML response, before JavaScript runs. HTML

  • Implemented: F02
    Markdown by URL

    Every page supports .md. The English root uses /index.md. Markdown

  • Implemented: F03
    JSON by URL

    Content, headings, sections, links, language and structured data in one document. HTTP / JSON

  • Implemented: F04
    HTTP content negotiation

    Accept selects explicit Markdown or JSON; Vary: Accept separates representations. Accept / Vary

  • Implemented: F05
    One source for three formats

    Markdown and JSON derive from HTML main, without a separate biography for bots. HTTP / JSON

  • Implemented: F06
    Structure preserved

    Lists, tables, code, links and image references survive serialization. Markdown

  • Implemented: F07
    Decoration excluded from content

    Navigation, controls and decorative seals are excluded from Markdown and JSON. HTTP / JSON

03 / Identity, attribution and citations06 controls

  • Implemented: C01
    Canonical document URLs

    HTML, Markdown, JSON and search results refer to the same publication. HTTP / JSON

  • Implemented: C02
    Anchored sections

    Headings have identifiers for linking a specific passage. HTTP / JSON

  • Implemented: C03
    Consistent identity

    Person uses a stable identifier and links to the author’s public profiles. JSON-LD

  • Implemented: C04
    Content-specific structured data

    Profile, articles, projects and credentials publish structured data alongside visible text. JSON-LD

  • Implemented: C05
    Declared author and dates

    Articles identify the author and preserve available publication and modification dates. JSON Feed

  • Implemented: C06
    Project evidence and limitations

    Projects link repositories, revisions and published results with their scope. Fuentes / Sources

04 / Retrieval and context05 controls

  • Implemented: R01
    Search over published text

    BM25 searches passages extracted from build HTML. Scores measure lexical relevance. HTTP / JSON

  • Implemented: R02
    Explicit filters and pagination

    Language, kind, offset, limit and next support bounded, repeatable traversal. HTTP / JSON

  • Implemented: R03
    Results with citations and versions

    Every result includes an excerpt, citationUrl and the indexed document’s contentHash. HTTP / JSON

  • Implemented: R04
    Read individual sections

    section selects a heading and its subsections, with its own hash and source hash. HTTP / JSON

  • Implemented: R05
    MCP context windows

    Reading supports limits and continuation by Unicode characters. The hash identifies the complete source. MCP

05 / Contracts and interfaces05 controls

  • Implemented: I01
    RFC 9727 API catalog

    A Linkset advertises endpoints and links their contracts and documentation. Linkset

  • Implemented: I02
    OpenAPI 3.1 contract

    Operations, parameters, limits, responses and errors are documented for HTTP clients. OpenAPI

  • Implemented: I03
    Document and passage JSON Schema

    The two response types have distinct schemas and a describedby header. JSON Schema

  • Implemented: I04
    Read-only MCP

    Tools to list, search and read using the official SDK and HTTP transport without persistent sessions. MCP / HTTP

  • Implemented: I05
    RFC 9457 structured errors

    Document, search, catalog, inventory and feed APIs return problem+json for handled errors. Problem Details

06 / Freshness and integrity05 controls

  • Implemented: V01
    SHA-256 content identity

    Documents explain which fields are hashed. It identifies a version, not the truth of its claims. HTTP / JSON

  • Implemented: V02
    Build inventory

    Paginated URLs and hashes, collection version and generation time for comparing snapshots. HTTP / JSON

  • Implemented: V03
    Conditional reads

    ETag and If-None-Match allow 304 responses without retransmitting unchanged documents. ETag / 304

  • Implemented: V04
    Metadata without a response body

    HEAD is available on documents, search, catalog, inventory and feeds. HEAD

  • Implemented: V05
    Publication 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: A01
    Explicit languages

    HTML declares the content language; JSON and document responses preserve it. HTTP / JSON

  • Implemented: A02
    Linked EN and ES versions

    hreflang links available versions and declares x-default. HTML head

  • Implemented: A03
    Native HTML semantics

    main, headings, lists, tables and links express the content structure. HTML

  • Implemented: A04
    Photo references, decorative seals

    Photos are retained. Project seals are empty elements with aria-hidden. HTML / aria-hidden

  • Implemented: A05
    Public APIs without sessions

    HTTP read APIs support CORS and OPTIONS. No account, cookies or key required. CORS / OPTIONS

08 / Consistency and boundaries05 controls

  • Implemented: B01
    Versioned profile

    Pages and APIs use the same versioned professional profile snapshot. HTTP / JSON

  • Implemented: B02
    Index generated from HTML

    The build rejects missing or duplicate heading anchors and expected pages absent from the index. Build

  • Implemented: B03
    Site-scoped reading

    The reader accepts known public paths and bounds source size, time and redirects. Contrato / Contract

  • Implemented: B04
    Content treated as source material

    MCP tools identify document text as untrusted material for agent instructions. MCP instructions

  • Implemented: B05
    Machine-readable checklist

    This list and its JSON use the same registry. Each control has an identifier and evidence link. HTTP / JSON