{
  "$schema": "https://themachinepress.com/schemas/story-v1.schema.json",
  "schema_version": "1.0.0",
  "document_type": "machine_press_story",
  "story": {
    "story_id": "mp-2026-08-23-014",
    "source_story_id": "tmp-story-shieldfs-confidential-storage",
    "edition_id": "mp-2026-08-23-morning-0045",
    "edition_url": "https://themachinepress.com/edition/2026-08-23",
    "position": 14,
    "story_type": "dispatch",
    "section": "infrastructure",
    "editorial_classification": "editorial",
    "headline": "The Trusted Enclave Still Needed a Fresh Disk",
    "slug": "the-trusted-enclave-still-needed-a-fresh-disk",
    "dek": "ShieldFS extends ZFS so a hostile storage stack cannot silently roll back, replay or fork persistent state.",
    "summary": "ShieldFS extends ZFS so a hostile storage stack cannot silently roll back, replay or fork persistent state.",
    "body_text": "The design keeps succinct commitments inside trusted execution environments and a lightweight registry, while authenticating the write-ahead log and storage pool with hash chains and an embedded Merkle tree. Reads verify freshness and integrity without application changes; the paper reports performance comparable to other evaluated filesystems, but the security claim remains conditioned on its confidential-computing threat model and trusted registry.",
    "why_it_matters": "ShieldFS extends ZFS so a hostile storage stack cannot silently roll back, replay or fork persistent state.",
    "limitations": [],
    "importance": 8,
    "canonical_url": "https://themachinepress.com/story/mp-2026-08-23-014/the-trusted-enclave-still-needed-a-fresh-disk",
    "json_url": "https://themachinepress.com/story/mp-2026-08-23-014.json",
    "first_published_at": "2026-08-23T09:00:00.000-04:00",
    "modified_at": "2026-08-23T09:00:00.000-04:00",
    "content_status": "new",
    "is_carryover": false,
    "carryover_reason": null,
    "key_claims": [
      {
        "claim_id": "claim-mp-2026-08-23-014-001",
        "text": "ShieldFS extends ZFS so a hostile storage stack cannot silently roll back, replay or fork persistent state.",
        "source_ids": [
          "source-2026-08-23-014"
        ],
        "qualification": null
      }
    ],
    "source_ids": [
      "source-2026-08-23-014"
    ],
    "tags": [
      "confidential computing",
      "filesystems",
      "storage security"
    ],
    "image_url": null,
    "corrections": []
  },
  "sources": [
    {
      "source_id": "source-2026-08-23-014",
      "title": "arXiv preprint 2608.19924",
      "publisher": "arXiv",
      "url": "https://arxiv.org/abs/2608.19924",
      "canonical_url": "https://arxiv.org/abs/2608.19924",
      "source_type": "primary_research",
      "is_primary_source": true,
      "published_at": "2026-08-20T07:41:15.000-04:00",
      "accessed_at": "2026-08-23T08:27:00.000-04:00",
      "supports_claim_ids": [
        "claim-mp-2026-08-23-014-001"
      ]
    }
  ],
  "corrections": [],
  "publisher": {
    "name": "The Machine Press",
    "url": "https://themachinepress.com",
    "description": "A daily newspaper for the age of artificial intelligence."
  },
  "cite_this_report": {
    "title": "The Trusted Enclave Still Needed a Fresh Disk",
    "publisher": "The Machine Press",
    "published_at": "2026-08-23T09:00:00.000-04:00",
    "canonical_url": "https://themachinepress.com/story/mp-2026-08-23-014/the-trusted-enclave-still-needed-a-fresh-disk"
  }
}