<?xml version="1.0" encoding="UTF-8" ?> <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel> <title>Reconstruction-Grade eDiscovery</title><description>Public draft of a vendor-independent conformance standard for assessing preservation and reproduction of modern collaborative evidence with point-in-time fidelity, relationship integrity, and bounded evidence handling.</description><link>https://rgrstandard.org/</link><atom:link href="https://rgrstandard.org/feed_rss_created.xml" rel="self" type="application/rss+xml" /> <docs>https://github.com/cloudficient/reconstruction-grade-ediscovery-standard</docs><language>en</language> <pubDate>Wed, 08 Apr 2026 12:30:43 -0000</pubDate> <lastBuildDate>Wed, 08 Apr 2026 12:30:43 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.17.9</generator> <image> <url>None</url> <title>Reconstruction-Grade eDiscovery</title> <link>https://rgrstandard.org/</link> </image> <item> <title>The Dog, the Tail, and the Staircase</title> <author>Peter Kozak</author> <category>Conformance</category> <category>Context Gap</category> <category>Craig Ball</category> <category>Industry Response</category> <category>Linked Attachments</category> <category>Preservation Gap</category> <category>RG-Aware</category> <category>Reconstruction-Grade</category> <category>Standard Development</category> <category>eDiscovery</category> <description>Craig Ball says collect linked attachments first, worry about versions later. We agree—and introduce RG-Aware, a pre-conformance tier for the preservation gap.</description> <link>https://rgrstandard.org/blog/the-dog-the-tail-and-the-staircase/</link> <pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate> <source url="https://rgrstandard.org/feed_rss_created.xml">Reconstruction-Grade eDiscovery</source><guid isPermaLink="true">https://rgrstandard.org/blog/the-dog-the-tail-and-the-staircase/</guid> </item> <item> <title>I Tried to Break the Preservation Gap Argument. Here&#39;s What&#39;s Left.</title> <author>Peter Kozak</author> <category>AI in Legal</category> <category>Collaboration Platforms</category> <category>Context Gap</category> <category>ESI Protocol</category> <category>FRCP Rule 37(e)</category> <category>Industry Analysis</category> <category>Litigation Hold</category> <category>Microsoft 365</category> <category>Preservation Gap</category> <category>Reconstruction-Grade</category> <category>eDiscovery</category> <description>We used Claude and ChatGPT Pro in an adversarial AI dialogue to stress-test the Preservation Gap under Rule 37(e). Two failure modes, a limiting principle, and four questions any eDiscovery practitioner can raise in their next ESI protocol.</description> <link>https://rgrstandard.org/blog/i-tried-to-break-the-preservation-gap-argument-heres-whats-left/</link> <pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate> <source url="https://rgrstandard.org/feed_rss_created.xml">Reconstruction-Grade eDiscovery</source><guid isPermaLink="true">https://rgrstandard.org/blog/i-tried-to-break-the-preservation-gap-argument-heres-whats-left/</guid> </item> <item> <title>What FRCP Rule 37(e) Means for Modern Collaboration Platforms</title> <author>Brandon D'Agostino</author> <category>Collaboration Platforms</category> <category>FRCP Rule 37(e)</category> <category>Industry Analysis</category> <category>Microsoft 365</category> <category>Preservation</category> <category>Reconstruction-Grade</category> <category>eDiscovery</category> <description>How FRCP Rule 37(e) reasonable steps is evolving for collaboration platform evidence — case law from Epic v. Google to Carvana&#39;s capability testing.</description> <link>https://rgrstandard.org/blog/what-frcp-rule-37e-means-for-modern-collaboration-platforms/</link> <pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate> <source url="https://rgrstandard.org/feed_rss_created.xml">Reconstruction-Grade eDiscovery</source><guid isPermaLink="true">https://rgrstandard.org/blog/what-frcp-rule-37e-means-for-modern-collaboration-platforms/</guid> </item> <item> <title>The Simplest E-Discovery Test Most Tools Would Fail</title> <author>Peter Kozak</author> <category>Benchmarking</category> <category>Industry Analysis</category> <category>Microsoft 365</category> <category>Modern Attachments</category> <category>Reconstruction-Grade</category> <category>eDiscovery</category> <description>Why most eDiscovery tools fail a basic modern attachment test: resolving the correct as-sent document version from a SharePoint link in Microsoft 365 email.</description> <link>https://rgrstandard.org/blog/the-simplest-e-discovery-test-most-tools-would-fail/</link> <pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate> <source url="https://rgrstandard.org/feed_rss_created.xml">Reconstruction-Grade eDiscovery</source><guid isPermaLink="true">https://rgrstandard.org/blog/the-simplest-e-discovery-test-most-tools-would-fail/</guid> </item> <item> <title>Sedona Identified the Problems. Here&#39;s the Architectural Answer.</title> <author>Peter Kozak</author> <category>Collaboration Platforms</category> <category>Industry Analysis</category> <category>Reconstruction-Grade</category> <category>Sedona Conference</category> <category>eDiscovery</category> <description>How The Sedona Conference&#39;s 2025 Commentary on collaboration platforms aligns with the RGR Standard&#39;s architectural answers for eDiscovery challenges.</description> <link>https://rgrstandard.org/blog/sedona-identified-the-problems-heres-the-architectural-answer/</link> <pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate> <source url="https://rgrstandard.org/feed_rss_created.xml">Reconstruction-Grade eDiscovery</source><guid isPermaLink="true">https://rgrstandard.org/blog/sedona-identified-the-problems-heres-the-architectural-answer/</guid> </item> </channel> </rss>