<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">

    <!-- Homepage -->
    <url>
        <loc>https://rjl.pub/</loc>
        <lastmod>2026-10-21T22:16:49.903Z</lastmod>
        <changefreq>weekly</changefreq>
        <priority>1.0</priority>
        <image:image>
            <image:loc>https://rjl.pub/img/rjl-pub-preview.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey</image:title>
            <image:caption>Comprehensive guide to AI-assisted software development by RJ Lindelof</image:caption>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/1.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 1 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/ai-native.png</image:loc>
            <image:title>AI-native development reorganizes the full software lifecycle around how AI operates</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/ai-assisted-developer.png</image:loc>
            <image:title>Traditional development workflow versus the agentic workflow, and what AI excels at</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/ai-codes.png</image:loc>
            <image:title>AI codes, engineers build software</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/tool-evolution.png</image:loc>
            <image:title>Six-step staircase showing the tool evolution from chat to IDE chat, inline edit, multi-file agent, full-project agent and async fleet.</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/context-as-infra.png</image:loc>
            <image:title>Context as infrastructure: what context is, the cost of poor context, context ROI, context layers, and guardrail best practices</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/agents-vs-claude-md.png</image:loc>
            <image:title>Comparison of AGENTS.md as a concise cross-tool file and CLAUDE.md as a deep Claude Code file, with an agent that merges both.</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/intent-engineering.png</image:loc>
            <image:title>Intent engineering turns human intent into precise, reliable outcomes: clarify, structure, refine, optimize</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/six-failure-modes.png</image:loc>
            <image:title>Six cards naming the failure modes intent prevents: scope drift, runaway tool use, silent partial completion, missing escalation, success theater and irreversibility.</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/claude-code.png</image:loc>
            <image:title>Claude Code architecture and capabilities: every surface it runs on, core capabilities, and the 2026 operations layer</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/github-copilot-alternatives.png</image:loc>
            <image:title>GitHub Copilot in 2026: inline suggestions, multi-model picker, agent mode, coding agent, MCP support, and enterprise controls</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cursor-ai-first.png</image:loc>
            <image:title>Cursor and AI-first IDEs: the AI-first editor, the 2026 shift to managing agents, and Cursor-specific features</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/mcp-server.png</image:loc>
            <image:title>MCP, A2A and the protocol layer: agents, the MCP protocol, transports, and MCP servers for tools and data</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/model-routing.png</image:loc>
            <image:title>Flow diagram routing a task to a fast cheap model or a frontier model depending on complexity, with escalation on failure.</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/prompt-engineering-old.png</image:loc>
            <image:title>Prompt engineering is table stakes; work with agents like senior engineers</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/context-priority.png</image:loc>
            <image:title>Four-tier funnel ranking context from critical, always include, down to low priority, omit.</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/rag-pipeline.png</image:loc>
            <image:title>Two-row pipeline: index documents into chunks, embeddings and a vector store, then embed a question, retrieve nearest chunks, build a prompt and produce an answer.</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/cache-layers.png</image:loc>
            <image:title>Three stacked layers ordered by how often they change: always cached, cached per session, and never cached.</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/plan-act-verify.png</image:loc>
            <image:title>Loop diagram of plan, act, verify and correct, ending at done only when an independent check confirms all criteria are met.</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/async-fleet.png</image:loc>
            <image:title>Issue fanned out to three isolated branches, then through CI evals, then to human review.</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/what-problem.png</image:loc>
            <image:title>The reframing question: what problem are we trying to solve?</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/spec-source-of-truth.png</image:loc>
            <image:title>The spec loop: tasks, agent, review, and evals all point back to one spec</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/review-gates.png</image:loc>
            <image:title>Pull requests pass an AI review, a quality gate, and evals before a human applies judgment</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/lethal-trifecta.png</image:loc>
            <image:title>Venn diagram of private data, untrusted content, and external communication overlapping at danger</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/four-pillars.png</image:loc>
            <image:title>Four pillars of governance, security, ROI, and FinOps supporting sustainable adoption</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/data-boundary.png</image:loc>
            <image:title>Three options for where regulated data goes, from vendor API to self-hosted inside the security boundary</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/golden-path.png</image:loc>
            <image:title>A paved golden path with AI stages from scaffold to deploy beside a rough off-road trail</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/dora-four.png</image:loc>
            <image:title>The four DORA metrics as gauges: deployment frequency, lead time, change failure rate, and MTTR</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/hybrid-contract-pipeline.png</image:loc>
            <image:title>Contract pipeline: LLM extraction, a rules engine, and ML anomaly detection, with human review for low confidence</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/migration-at-scale.png</image:loc>
            <image:title>One intent spec fans out to parallel agents, passes through an eval gate, and either merges or escalates</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/ai-bottleneck.png</image:loc>
            <image:title>Speeding up coding relocates the bottleneck rather than removing it</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/judgment-expensive.png</image:loc>
            <image:title>AI made code cheap - judgment got expensive; architecture review, quality gates, and earlier decisions are the load-bearing wall</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/ai-adoption.png</image:loc>
            <image:title>What actually drives AI adoption on engineering teams</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/adoption-waves.png</image:loc>
            <image:title>Adoption spreading outward in waves from a hackathon through engineering, DevOps, and product</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/little-risk-why-wait.png</image:loc>
            <image:title>If the downside is this small, what are we protecting by waiting?</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/doer-vs-driver.png</image:loc>
            <image:title>A do-er executes the spec; a driver owns the outcome - in remote teams, judgment is the job</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/rasci-meetings.png</image:loc>
            <image:title>RACI meeting attendance: Accountable and Responsible attend, Consulted joins relevant topics, Informed reads the AI-generated summary</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/remote-teams.png</image:loc>
            <image:title>Two teams, one vague requirement, two different products - distance does not break teams, ambiguity does</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/multi-agent-team.png</image:loc>
            <image:title>A human owner over a supervisor agent coordinating backend, frontend, testing, and security agents</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/sections/context-intent-stack.png</image:loc>
            <image:title>Stack of model, context, and intent layers: table stakes, substrate, differentiator</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/2.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 2 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/3.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 3 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/4.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 4 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/5.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 5 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/6.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 6 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/7.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 7 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/8.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 8 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/9.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 9 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/10.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 10 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/11.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 11 of 12</image:title>
        </image:image>
        <image:image>
            <image:loc>https://rjl.pub/img/cover/12.png</image:loc>
            <image:title>RJL.pub - AI-Native Development Journey Cover 12 of 12</image:title>
        </image:image>
    </url>

</urlset>
