<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Singular State</title>
  <link>https:&#x2F;&#x2F;singular-state.com</link>
  <description>Advanced technical expertise for feasibility, prototyping and modernization. We build the working pilot and ramp up your team to take it forward.</description>
  <language>en-US</language>
  <atom:link href="https://singular-state.com/topics/transfer/rss.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>Boring technology, and the debt you write down</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;boring-technology-and-the-debt-you-write-down&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;boring-technology-and-the-debt-you-write-down&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Familiar means familiar to the receiving team, not old. And the ledger records what the code cannot do, including the debt nobody chose.</description>
  </item>
  <item>
    <title>Comprehension debt and the transfer that cannot happen</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;comprehension-debt-and-the-transfer&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;comprehension-debt-and-the-transfer&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Understanding is measured on the receiving side, against named tasks. A team that passes acceptance and cannot explain why a rule change moved an outcome has not received the system.</description>
  </item>
  <item>
    <title>The credentials that outlive the engagement</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;credentials-that-outlive-the-engagement&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;credentials-that-outlive-the-engagement&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Vendor accounts, service principals, API keys and cloud tenancy persist after the final invoice. Revocation is not one action, and absence from an inventory is not absence.</description>
  </item>
  <item>
    <title>Documentation-only handoff, and the three transitions that replace it</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;documentation-only-handoff&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;documentation-only-handoff&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Shadowing, reverse shadowing, and pairing transfer different things in a required order. Delivering documents and confirming receipt are two records, and neither is evidence of use.</description>
  </item>
  <item>
    <title>No capacity, no skills, no budget, no interest</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;no-capacity-skills-budget-interest&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;no-capacity-skills-budget-interest&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Four handover failures with four diagnostics and four remedies. A stalled transfer is an outcome, and it does not identify its own cause.</description>
  </item>
  <item>
    <title>Comparability, not documentation: how pharmaceutical technology transfer proves a handover</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;pharmaceutical-technology-transfer-comparability&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;pharmaceutical-technology-transfer-comparability&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>A regulated transfer completes when the receiving site independently reproduces the specified result against criteria agreed in advance. Assisted and unassisted execution answer different questions.</description>
  </item>
  <item>
    <title>Phoenix pay, HealthCare.gov, and NPfIT read through a transfer lens</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;phoenix-healthcare-gov-npfit-transfer-lens&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;phoenix-healthcare-gov-npfit-transfer-lens&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Three heavily documented programmes, re-examined for one question: what was handed over, to whom, and against what evidence. Plus the limits of reasoning from cases at all.</description>
  </item>
  <item>
    <title>Snagging lists, defects liability, and readiness ladders</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;snagging-defects-liability-readiness-ladders&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;snagging-defects-liability-readiness-ladders&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Construction separates practical completion from final acceptance and holds the builder liable across the gap. Four disciplines stage readiness; software handover has no equivalent structure.</description>
  </item>
  <item>
    <title>Sometimes the correct answer is never to transfer</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;sometimes-never-transfer&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;sometimes-never-transfer&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>The structure assumes handover is the goal. Where the receiving organisation has no path to the capability, forcing a transfer produces an orphan with an owner&#x27;s name on it.</description>
  </item>
  <item>
    <title>The receiving team is the deliverable</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;the-receiving-team-is-the-deliverable&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;the-receiving-team-is-the-deliverable&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Invert the frame: the software is the byproduct and the capability is the product. Every practice that eases transfer is a training programme with an artifact attached.</description>
  </item>
  <item>
    <title>The run-cost handoff nobody scheduled</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;the-run-cost-handoff&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;the-run-cost-handoff&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>A transferred system arrives with a bill and no budget line, because the fiscal year that funded the build did not fund the operation. Six things move on six different dates.</description>
  </item>
  <item>
    <title>Transition assistance clauses: the exit you negotiate at the start</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;transition-assistance-clauses&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;transition-assistance-clauses&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Termination for convenience is a settlement mechanism, not a free exit. And staff are participants with rights, not artifacts that transfer with the repository.</description>
  </item>
</channel>
</rss>
