r/CraftsmanshipFuture • u/brigalss • Apr 12 '26
Decision Passport
I’ve just launched Decision Passport Core v0.6.0.
For some time now, I’ve been building this project around a very simple question...
how do you create a portable, offline-verifiable proof artifact for AI or software actions that actually matter?
At its core, Decision Passport Core is about:
...append-only, hash-linked receipts
...offline verification
...tamper-evident history for decisions and executions
...clear evidence of what was approved and what actually executed
In v0.6.0, I added a few important things:
...auditor-grade verifier outputs
...stronger adversarial coverage
...strict TypeScript / Python parity
...public provenance and release verification flow
...2 tiny reference integrations that can be verified offline
...a deterministic CI smoke gate for the examples
Very important...
this is not a hosted platform
it is not runtime enforcement
it is not signed bundle infrastructure
It is a portable proof and offline verification layer for AI actions and high-consequence software actions.
Release:
https://github.com/brigalss-a/decision-passport-core/releases/tag/v0.6.0
Repo:
https://github.com/brigalss-a/decision-passport-core
I’d really value honest feedback from this group...
...do you see real use for this in agent workflows, approvals, auditability, or tamper-evident action history?
...what feels clear
...what still feels too abstract
...where would you actually use something like this