NENRIN opens AI agent logs to anyone with sha256

Oga's argument comes from his own background: he worked as a carpenter from age 15, became a site supervisor, and spent 30 years in construction, where he watched clients judge a quote by the size of a contractor's signboard. A signboard, he writes, guarantees nothing about the quote — only checking each line's quantity and unit price does. He applies the same standard to software, and to himself.

The mechanism he offers is deliberately unglamorous. Records pile onto the public JIDEC ledger and are never rewritten; when he finds an error, he adds a correction that cites the original. That happened today (2026-10-13), when he found his spec had misdescribed a figure about an MCP server — 93,983 search impressions and 0 calls were actually one listing site's admin panel views and calls via that listing. Because the spec is anchored to Bitcoin, it cannot be deleted, so he added correction #95 instead.

He names his own weak points: no outside company uses NENRIN in production, most ledger witnesses are still his own observations, and independent witnesses number only a few. He places NENRIN alongside TRACE for runtime proof, SINT for pre-execution permission control, and TrustChain for decentralized reputation, framing them as complementary rather than competing.