<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>opentine blog</title>
    <link>https://opentine.com/blog</link>
    <description>Git-shaped provenance for agent runs: capture, import, verify, fork, attest, synchronize, and export portable execution history.</description>
    <language>en-us</language>
    <item>
      <title>opentine v0.5.0: provenance across the agent ecosystem</title>
      <link>https://opentine.com/blog/opentine-v0-5-0</link>
      <guid isPermaLink="true">https://opentine.com/blog/opentine-v0-5-0</guid>
      <pubDate>Fri, 31 Jul 2026 22:45:00 GMT</pubDate>
      <description>OpenTelemetry GenAI export, shell-level trace import, stable JSON output, and live LangChain/LangGraph capture connect durable provenance to the stack you already run.</description>
    </item>
    <item>
      <title>opentine v0.4.0: distinct IDs for divergent portable forks</title>
      <link>https://opentine.com/blog/opentine-v0-4-0</link>
      <guid isPermaLink="true">https://opentine.com/blog/opentine-v0-4-0</guid>
      <pubDate>Fri, 31 Jul 2026 16:35:00 GMT</pubDate>
      <description>Distinct portable fork identities, signed fork provenance, deterministic cached replay, and a permanent v0.3 compatibility gate—without a format bump.</description>
    </item>
    <item>
      <title>opentine v0.3.0: git-shaped provenance for agent runs</title>
      <link>https://opentine.com/blog/opentine-v0-3-0</link>
      <guid isPermaLink="true">https://opentine.com/blog/opentine-v0-3-0</guid>
      <pubDate>Thu, 30 Jul 2026 14:00:00 GMT</pubDate>
      <description>Verified v3 repositories, signed provider-neutral billing, normalized traces, MCP workflows, and a bounded self-hosted remote join the portable .tine format.</description>
    </item>
    <item>
      <title>Trusting long-running agents</title>
      <link>https://opentine.com/blog/trusting-long-running-agents</link>
      <guid isPermaLink="true">https://opentine.com/blog/trusting-long-running-agents</guid>
      <pubDate>Wed, 08 Jul 2026 14:00:00 GMT</pubDate>
      <description>Autosave, budgets, signing, verification, and field-level diffs turn a long agent run into an artifact you can operate with confidence.</description>
    </item>
    <item>
      <title>Migrating .tine artifacts from v1 to v2</title>
      <link>https://opentine.com/blog/migrating-tine-v1-to-v2</link>
      <guid isPermaLink="true">https://opentine.com/blog/migrating-tine-v1-to-v2</guid>
      <pubDate>Thu, 02 Jul 2026 14:00:00 GMT</pubDate>
      <description>How automatic in-memory migration, dry runs, verified sources, and one-way re-saves work in opentine 0.2.</description>
    </item>
    <item>
      <title>opentine v0.2.0: trusted, searchable agent artifacts</title>
      <link>https://opentine.com/blog/opentine-v0-2-0</link>
      <guid isPermaLink="true">https://opentine.com/blog/opentine-v0-2-0</guid>
      <pubDate>Mon, 29 Jun 2026 14:00:00 GMT</pubDate>
      <description>Format v2, safe migrations, signing, search, budgets, autosave, and field-level diffs make local agent artifacts operational infrastructure.</description>
    </item>
    <item>
      <title>Replay as a primitive</title>
      <link>https://opentine.com/blog/replay-as-a-primitive</link>
      <guid isPermaLink="true">https://opentine.com/blog/replay-as-a-primitive</guid>
      <pubDate>Wed, 13 May 2026 14:00:00 GMT</pubDate>
      <description>Replay is not just a debugging feature. Cache replay, explicit rerun, and diff form a reusable development primitive.</description>
    </item>
    <item>
      <title>The missing layer beneath every agent framework</title>
      <link>https://opentine.com/blog/the-missing-layer-beneath-every-agent-framework</link>
      <guid isPermaLink="true">https://opentine.com/blog/the-missing-layer-beneath-every-agent-framework</guid>
      <pubDate>Wed, 06 May 2026 14:00:00 GMT</pubDate>
      <description>Frameworks orchestrate execution. A portable local artifact layer preserves the history that should outlive any framework.</description>
    </item>
    <item>
      <title>The terminal isn&apos;t a demo</title>
      <link>https://opentine.com/blog/the-tui-isnt-a-demo</link>
      <guid isPermaLink="true">https://opentine.com/blog/the-tui-isnt-a-demo</guid>
      <pubDate>Wed, 29 Apr 2026 14:00:00 GMT</pubDate>
      <description>Why the CLI became opentine&apos;s first working product surface: the shortest path between an artifact and the project that produced it.</description>
    </item>
    <item>
      <title>Observability shows the run. State lets you act on it.</title>
      <link>https://opentine.com/blog/langsmith-is-observability-opentine-is-state</link>
      <guid isPermaLink="true">https://opentine.com/blog/langsmith-is-observability-opentine-is-state</guid>
      <pubDate>Wed, 22 Apr 2026 14:00:00 GMT</pubDate>
      <description>Tracing explains what happened. A portable run artifact adds verification, cache replay, forking, and scoped resumption.</description>
    </item>
    <item>
      <title>Introducing opentine</title>
      <link>https://opentine.com/blog/introducing-opentine</link>
      <guid isPermaLink="true">https://opentine.com/blog/introducing-opentine</guid>
      <pubDate>Thu, 09 Apr 2026 14:00:00 GMT</pubDate>
      <description>Every agent run should be a first-class artifact you can verify, inspect, fork, replay, and share.</description>
    </item>
    <item>
      <title>Why I made run graphs content-addressed</title>
      <link>https://opentine.com/blog/content-addressed-runs</link>
      <guid isPermaLink="true">https://opentine.com/blog/content-addressed-runs</guid>
      <pubDate>Tue, 07 Apr 2026 14:00:00 GMT</pubDate>
      <description>Content addressing gives agent steps stable identities, reusable graph prefixes, cache provenance, and integrity checks.</description>
    </item>
    <item>
      <title>The forked_debug pattern</title>
      <link>https://opentine.com/blog/forked-debug-pattern</link>
      <guid isPermaLink="true">https://opentine.com/blog/forked-debug-pattern</guid>
      <pubDate>Sun, 05 Apr 2026 14:00:00 GMT</pubDate>
      <description>Inspect the failure, fork from a known-good step, rerun through the right runtime, and diff the branch.</description>
    </item>
  </channel>
</rss>