human-integrity-protocol-primary-sources-2026-05-12

Human Integrity Protocol primary sources

Collected: 2026-05-12 UTC

Primary sources reviewed

• https://hipprotocol.org/
  • Official protocol site
  • Used to confirm the project’s self-description as a human-origin attestation protocol and its public-facing positioning around verification, on-chain anchoring, and open tooling
• https://github.com/human-integrity-protocol/hip-protocol
  • Official protocol repository
  • Used to confirm the Bitcoin-rooted genesis design, public verification path, proof-bundle/spec layout, HUMAN-PROOF framing, implementation split between protocol and products, and the claim that any tool can produce or verify HIP attestations
• https://github.com/human-integrity-protocol/hip-protocol/blob/main/specs/HIP_HP-SPEC-v1.md
  • Official HUMAN-PROOF credential mechanics spec
  • Used to confirm credential lifecycle states, Trust Index composition, point-of-use liveness, classification access gating, compromise handling, and the statement that Trust Index is an internal protocol instrument rather than a public ranking of humans
• https://github.com/human-integrity-protocol/hip-protocol/blob/main/specs/HIP_PATHWAY-SPEC-v1.md
  • Official pathway-governance spec stub
  • Used to confirm pathway tiering, PHI monitoring, pathway states, declassification logic, contingency pathways, and the explicit split between credential mechanics and pathway-governance policy

Notes

• HIP clears the intake bar because it is not simply a creator badge or anti-AI marketing layer. Its main mechanism is the decomposition of human-origin attestation into credential issuance, pathway governance, liveness, behavioral history, and portable proof artifacts.
• The strongest reusable comparison hook is the split between the credential layer and the pathway layer. A creator may hold a credential, but the pathway that issued it can later be reviewed, suspended, or declassified, which makes issuer governance an explicit part of provenance.
• The Bitcoin genesis inscription matters analytically because HIP is trying to ground later attestations in a public, independently verifiable origin event rather than only in a hosted API or SaaS operator.
• The protocol is still early and partially published. The repository explicitly notes several finalized-but-not-yet-published companion specs, and the current PATHWAY spec is a scope stub rather than the full completed spec.
• No standalone whitepaper PDF was confirmed in this pass.