HIRI Passport

HIRI Passport, as described by its author, is a holder-controlled digital identity system intended to allow users to manage credentials, selectively disclose information, and verify claims without surrendering personal data. The project is presented as a Synthetic Demo built during the OpenAI Build Week hackathon, which does not process real identity data or connect to production systems.

The author states that HIRI Passport aims to support cryptographic subject binding, selective disclosure, proof of possession, credential status evaluation, and organizational identity evidence — all within a framework designed to separate trust questions (e.g., issuer authority vs. signature validity) rather than aggregate them into a single badge.

What changed: The project began as conceptual design work and evolved into a mobile-first Progressive Web App (PWA) using React, TypeScript, and Vite. It includes deterministic core logic and test coverage but remains in a synthetic, non-production state, with no real credentials or holder keys generated.

Single most important open question: Is the author’s vision of a holder-controlled digital identity system technically feasible and aligned with current standards for cryptographic identity systems? The lack of any real-world implementation or user feedback prevents assessing whether this is more than an engineering exercise.

The description states that HIRI Passport is:

• A mobile-first Synthetic Demo built with HTML, JavaScript, TypeScript.
• A Progressive Web App (PWA) using React and Vite.
• Deployed via GitHub Pages as a static site.
• Built entirely with generated sample data, not real identity information.
• Does not create real holder keys, accept real credentials, or contact production resolvers.
• Designed to explore the holder journey without requiring users or judges to trust it with personal data.

The author notes that this is an honest first implementation of a desired experience, not a production-ready system.

The description states: “The public application is a mobile-first Synthetic Demo built entirely with generated sample data.”

The author positions HIRI Passport as a user-controlled digital identity solution, distinct from platforms that centralize identity. It is described as:

• A portable, holder-controlled passport.
• Intended to let users receive credentials, understand their evidence, and decide what to disclose.
• Designed to never turn a valid cryptographic signature into a misleading claim that all trust questions have been answered.

The author emphasizes that the system separates cryptographic validity from real-world authority, and that honest unknown states should be visible rather than hidden behind a green badge.

The description states: “It should never turn a valid cryptographic signature into a misleading claim that every other trust question has been answered.”

This is an evolution from traditional identity systems where a single credential may imply full trust, toward a model where multiple independent questions are evaluated separately.

The author does not explicitly define the target customer or ideal customer profile (ICP). However, based on the product’s positioning and intended use case:

• The system is designed for holders of digital identities, who want control over their credentials.
• It is aimed at users who are concerned about data privacy and centralized identity management.
• The system is not yet production-ready, so it does not target actual end-users or institutions.

The description states: “The intended product is a portable, holder-controlled passport in which people can receive credentials...”

There is no evidence of specific personas, use cases, or institutional adoption plans.

No business model or pricing information is provided. The project is described as a Synthetic Demo and not a commercial offering.

The description states: “The OpenAI Build Week submission is an honest first implementation...”

There is no indication of monetization, licensing, or revenue streams.

The author provides technical details:

• Built with React, TypeScript, Vite, and deployed via GitHub Actions.
• Uses a deterministic Core with injected external dependencies.
• Includes 82 deterministic Core tests, 188 PWA unit/integration tests, and 240 conformance-trace mappings.
• Separates the Synthetic Demo from the Real Holder Preview via compile-time composition.
• Uses IndexedDB migration, local authentication, and encrypted portfolio state in the preview side.
• The system is designed to be fail-closed for production activation.

The description states: “The working application is a React and TypeScript progressive web app built with Vite...”

There is no evidence of real-world deployment, performance metrics, or scalability considerations beyond the demo.

No traction or maturity signals are evident. The project is described as:

• A Synthetic Demo.
• Not a production-ready system.
• Not connected to any real identity providers or verifiers.
• Not used by any end-users or institutions.

The description states: “The public application...accepts no real credentials, contacts no production resolver, and performs no production identity verification.”

There is no evidence of revenue, customers, usage data, or adoption.

No competitive landscape is described. The author does not mention existing systems (e.g., DID frameworks, SSI platforms, or digital identity ecosystems) that HIRI Passport might compete with or integrate with.

The description states: “No competitive context is provided.”

This is a self-contained project without reference to external systems or market positioning.

• No production readiness: The system is explicitly not production-ready and does not process real data.
• Lack of user feedback or adoption: No evidence of real-world usage or testing.
• Unverified claims: All descriptions are self-reported, with no third-party validation.
• Limited scope: The demo only explores the holder journey; it does not include issuer or verifier functionality.
• Dependency on automation: The author used Codex to implement parts of the system, but this was not presented as a production authorization.

The description states: “Codex created deterministic resource candidates...but did not pretend to be the external human reviewer.”

1. What are the specific cryptographic standards or protocols that HIRI Passport intends to support?
2. How does the system plan to handle real-world credential issuance and verification by authoritative institutions?
3. What is the timeline for transitioning from the Synthetic Demo to a production-ready system?
4. Are there any partnerships or integrations planned with existing identity ecosystems or platforms?
5. How will the system ensure that holder keys are truly protected in a production environment?
6. What mechanisms are in place to validate the authority of issuers and verifiers?