<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Pharos Production | Engineering Decision Guides]]></title><description><![CDATA[Pharos Production]]></description><link>https://pharosproduction.wixsite.com/software-development/blog</link><generator>RSS for Node</generator><lastBuildDate>Sun, 01 Nov 2026 14:37:57 GMT</lastBuildDate><atom:link href="https://pharosproduction.wixsite.com/software-development/blog-feed.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[How to Scope a Blockchain Integration Quote Across Four Acceptance Boundaries]]></title><description><![CDATA[A blockchain integration quote becomes easier to compare when it names four separate acceptance boundaries: obtaining network evidence, building a derived application view, reconciling that view with the business record and operating the resulting service. A supplier can deliver one boundary while leaving substantial work in another.]]></description><link>https://pharosproduction.wixsite.com/software-development/post/blockchain-integration-quote-acceptance-boundaries</link><guid isPermaLink="false">c0962a72-04c1-4cb0-ae57-e2dfa7223af0</guid><pubDate>Mon, 19 Oct 2026 19:19:54 GMT</pubDate><dc:creator>Dmytro Nasyrov</dc:creator></item><item><title><![CDATA[How to Accept a Document Update in a RAG Knowledge Assistant]]></title><description><![CDATA[A document update in a retrieval-augmented generation knowledge assistant is ready for acceptance when the intended audience can ask the agreed questions and receive answers supported by the correct, authorized source revision. A successful upload is only one observation along that route. It does not establish that retrieval, citations and saved answers have all adopted the change.]]></description><link>https://pharosproduction.wixsite.com/software-development/post/rag-document-update-acceptance</link><guid isPermaLink="false">b5d7df52-74dd-48eb-8587-5c306fc21dca</guid><pubDate>Mon, 19 Oct 2026 19:14:13 GMT</pubDate><dc:creator>Dmytro Nasyrov</dc:creator></item><item><title><![CDATA[Software Project Takeover: Prove the Incoming Team Can Run the Release]]></title><description><![CDATA[A software project takeover is ready for an ownership decision when the incoming team can explain which release it received, reproduce an agreed operating task and identify the dependencies that still require the outgoing supplier. Repository access alone cannot establish those facts.]]></description><link>https://pharosproduction.wixsite.com/software-development/post/software-project-takeover-build-proof</link><guid isPermaLink="false">548d6023-5537-42f5-9860-a15e0f2ffc74</guid><pubDate>Mon, 19 Oct 2026 19:07:56 GMT</pubDate><dc:creator>Dmytro Nasyrov</dc:creator></item></channel></rss>