Blog
Technical writing on content authenticity, digital asset integrity, and API design.
Building a Legible World: Our Vision for the Future of Verified Data
Truth should be easy to read. In an era of deepfakes and supply chain opacity, the ability to verify the provenance of any digital asset in seconds is the infrastructure the modern economy needs.
What the MIT Data Provenance Initiative Found — And the Gap That Remains for Enterprise AI Training Data
The MIT Data Provenance Initiative audited 1,800+ AI training datasets and found pervasive consent violations and broken provenance chains. They diagnosed the problem. Here is the infrastructure required to fix it continuously.
Beyond the UI Label: EU AI Act Article 50 and the Engineering Requirements Most Compliance Checklists Miss
Article 50 requires machine-readable AI content disclosure — a UI label alone does not satisfy the requirement. Here is the engineering implementation guide, and what most compliance checklists miss.
Microsoft's Blueprint for Proving What's Real Online — And Why It Validates the Ledgible Approach
Microsoft evaluated 60 content verification methods and published a gold standard for proving what's real online. The architecture they recommend is exactly what Ledgible already does. Here is what they found — and the gap they did not fill.
What Pharma, ESG, and Media Teach Us About Enterprise Provenance — And Where the Gaps Still Are
Three industries independently built provenance infrastructure and hit the same wall. Here is what MediLedger, Unilever's GreenToken, and the NYT News Provenance Project got right — and what gaps remain for enterprise content pipelines.
Why SHA-256 Alone Is Not Enough for Asset Provenance
Hashing proves integrity — it tells you a file has not changed. But it tells you nothing about who created it, when, or under what circumstances. Provenance requires signing.
Introducing the Ledgible Ingest API
One endpoint, two required fields, and your asset is signed. Here's a walkthrough of the design decisions behind the v1 ingest API.
How We Built an Append-Only Provenance Ledger
Immutability is easy to claim and hard to enforce. We'll walk through the schema constraints, application-level guards, and audit tooling that make our ledger actually append-only.
Verifying AI-Generated Content at Scale
When your pipeline produces thousands of AI-generated assets per day, you need provenance that is automatic, not manual. Here's how teams are using Ledgible to close that gap.
The Trust Deficit in Supply Chain Compliance — And Why Tracking Is Not the Same as Verifying
Tracking records that something moved. Verifying proves who authorized it. Here is the architectural difference — and why DSCSA final enforcement phases require the latter.
Digital Product Passports Are Becoming Law — Here Is What the ESPR Requires and How Provenance Infrastructure Delivers It
The EU's Ecodesign for Sustainable Products Regulation mandates Digital Product Passports for batteries, textiles, and electronics. Here is what the regulation actually requires and where most ESG data approaches fall short.
HMAC vs. Asymmetric Signing: Tradeoffs for Asset Provenance
Both approaches can produce tamper-evident records. We chose HMAC-SHA256 for v1 — here is the full reasoning, and where asymmetric signing fits better.
Get new posts in your inbox
No spam. Unsubscribe anytime.