<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>AI Implementation Field Notes</title><link>https://intelligency.pro/blog/</link><description>Reviewed technical notes from real AI workflow implementation: delivery contracts, consent, integrations, operational failure modes, and production evidence.</description><language>en-US</language><item><title>A 200 response is not a delivered lead: design an acceptance contract</title><link>https://intelligency.pro/blog/lead-form-delivery-acceptance-contract/</link><guid>https://intelligency.pro/blog/lead-form-delivery-acceptance-contract/</guid><pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate><description>Treat lead capture as a delivery workflow, not a thank-you animation. The browser should show success only after the server has persisted the submission and at least one accountable destination has confirmed receipt.</description></item><item><title>Consent is a distributed state: keep browser and backend in agreement</title><link>https://intelligency.pro/blog/consent-state-browser-backend/</link><guid>https://intelligency.pro/blog/consent-state-browser-backend/</guid><pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate><description>A banner is not the consent system. The browser, request payload, backend policy, storage, and downstream integrations must all interpret the same decision and version.</description></item></channel></rss>
