← Protocol Engine

Client portal

Client GB-001

Your verifiable history. Every version is hash-stamped and chained to the one before it — proof that nothing changed silently.

Jordan A. Sample

PII vault · AES-256-GCM

Name and DOB live only inside an encrypted blob. The database row never stores plaintext PII.

Encrypted at rest
vault.inspect
$ cat client.profileVault # raw column
sJENCPyG6uWO/n8/:c6zm970N+PREuwT4I1GQHw==:CuXXCN9Vz2i5bPXx0kaRIs…
$ vault --decrypt # authorized portal context
name: Jordan A. Sample

Latest version v2 is a DRAFT — not for clinical use until a clinician signs off.

Verifiable history
?
Every version stores a sha256 hash computed from its contents plus the previous version’s hash. Because each link depends on the one before it, you can re-run the check and prove that no version was edited or back-dated after the fact.

Version 1

Signed · Dr. A. Reyes, MD6 recs

sha256: 599dc475855f428b1f508a421589f5c858c1b5528fe682cbae1b6c0f12a22988

prev: GENESIS

Signed 8/6/2026, 12:48:34 AM

Version 2

Draft5 recs

sha256: d0f8e934071889951ee5ac68ad4d5b84eae1f0404b6e61c4eb10c2e4a9d443f5

prev: 599dc475855f428b1f508a421589f5c858c1b5528fe682cbae1b6c0f12a22988

chain.verify
$ verify-chain --client cmsgss35…
v1 599dc475855f428b1f508a42… ← GENESIS
v2 d0f8e934071889951ee5ac68… ← 599dc475…
OK — 2 versions verified, no silent edits
← Protocol detailWhat changed (v1 → v2)

Not medical advice. Protocol Engine is an educational, explainable decision-support demo. Every recommendation cites a source, but nothing here replaces a licensed clinician. Drafts are marked not for clinical use until a clinician signs off.