Publicly auditable

The FDE Assurance Registry.

An append-only log of certified FDE engagements. Each entry references the SHA-256 of the previous one — a tamper-evident chain anyone can verify with shasum, no account and no external service.

4 certifications

Every claim, scored and chained.

CertificationClaimScoreSHA-256Date
genesis Registry genesis block — defines the canonical Trust Score formula and the chain hash algorithm. This entry has no predecessor. — a67f32d952a9040e… 2026-06-21
2026-06-21-saas-churn-93 Reduce SaaS churn by 18% via retention model with Trust Score 93/100 93 9ebd16a6f2b52704… 2026-06-21
2026-06-21-retail-forecasting-91 Reduce retail stockouts by 22% via demand forecasting with Trust Score 91/100 91 f7cbe0bf32f550c7… 2026-06-21
2026-06-21-fintech-fraud-93 Detect 95% of fintech fraud with <5% false positives via gradient boosting on structured features, Trust Score 93/100 93 e6da8077af00a11a… 2026-06-21

Verify it yourself

git clone https://github.com/selectess/fde-consultants-protocoles
cd fde-consultants-protocoles

# 1. re-hash each entry, compare to registry/index.json
for f in registry/*.json; do shasum -a 256 "$f"; done

# 2. run the executable gate (re-hash + prev_hash linkage)
bash modex/verify.sh --registry
Trust model, stated honestly. The hash chain gives tamper-evidence relative to a root you have already witnessed — it does not, on its own, defend against the registry operator. Real tamper-proofing needs an external anchor (Sigstore Rekor, a signed git tag, or a public timestamp). Until that is wired in, this is a publicly auditable log, not a “tamper-proof” one. See registry/README.md.

Get the certifier

# install the FDE Consultant skill in any Claude Code client
/plugin marketplace add selectess/fde-consultants-protocoles
/plugin install fde-consultant@fde-consultant
Proof, not promises

Certify your own work.

Install the Skill, run an engagement, and submit it to the registry.

Install the Skill →How it works