<?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/contracts/rss.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>Acceptance criteria for a system that does not repeat itself</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;acceptance-criteria-non-deterministic-systems&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;acceptance-criteria-non-deterministic-systems&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>A fixed seed makes a best effort, not a guarantee. Acceptance shifts from exact output to declared task properties, a predeclared sampling rule, and uncertainty measured at the unit actually sampled.</description>
  </item>
  <item>
    <title>Staff augmentation, managed services, fixed-bid, outcome-based: where the risk sits</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;engagement-models-where-the-risk-sits&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;engagement-models-where-the-risk-sits&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Six engagement models fix four independent variables — who directs the work, how price is set, who owns continuing operation, and what transfers at the end. A label pins one and leaves three open.</description>
  </item>
  <item>
    <title>Escrow does not survive model deprecation</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;escrow-does-not-survive-model-deprecation&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;escrow-does-not-survive-model-deprecation&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Source escrow assumes the artifact is the source. Where behaviour depends on a hosted model the provider retires, the deposited package no longer reproduces the system.</description>
  </item>
  <item>
    <title>Full-stack IP ownership, work-for-hire, and licence-back</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;ip-ownership-work-for-hire-licence-back&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;ip-ownership-work-for-hire-licence-back&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Owning the copyright is not holding the file, and holding the file is not being able to run the system. Calling a contract work made for hire does not make it one.</description>
  </item>
  <item>
    <title>Liability after the last invoice</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;liability-after-the-last-invoice&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;liability-after-the-last-invoice&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Which obligations survive handover, which insurance responds to a model&#x27;s output, and why detection after transfer establishes nothing about when the defect arose.</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>
  <item>
    <title>Who owns the embeddings?</title>
    <link>https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;who-owns-the-embeddings&#x2F;</link>
    <guid isPermaLink="true">https:&#x2F;&#x2F;singular-state.com&#x2F;articles&#x2F;who-owns-the-embeddings&#x2F;</guid>
    <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
    <description>Indexes, embeddings, logs and fine-tuning corpora are created during the engagement and left out of the contract that governs it. Possession, ownership, licensed use and portability are four separate answers.</description>
  </item>
</channel>
</rss>
