sapho-structured-artifact-bundle-upgrade

You can generate structured internal bundle files by running an upgrade flow that derives curator.json, findings.jsonl, facts.jsonl, and validation artifacts alongside your existing compatibility markdown outputs without altering public-facing behavior.

Structured artifact bundles are internal files like curator.json and lineage.json that provide explicit claim-evidence mappings. You need them when article packages require improved validation, lineage tracking, and auditability for deterministic validator checks.

Yes, you can add structured internal bundle files without changing public-facing article outputs. The upgrade process preserves existing markdowns like article.md while emitting internal artifacts alongside them after synthesis and before final writes.

Build lineage tracking for Sapho article packages by running an upgrade that derives structured records from micro outputs to construct lineage.json with explicit claim-evidence mappings, strengthening article packaging for Sapho-native workflows.

Yes, structured artifact bundle generation works for both kept and discarded articles. The process provides deterministic structured outputs for validators across all article lifecycle outcomes without altering Daily Rail behavior.

A key limitation is that upgrading article packages to emit structured internal bundle files is intended exclusively for Sapho-native workflows, meaning it may not suit non-Sapho environments seeking to alter public-facing Daily Rail behavior.