wiki/projects/humankey-protocol/bridge-and-transport

Rendered from markdown source. Open raw source on GitHub.

Bridge and Transport

This seam holds the HumanKey transport, invite, and encrypted-backup material that sits around the core protocol drafts.

The documents here are operational companions rather than the protocol spine itself. They show how the trust-authentication family moves through manual messages, path invites, lane invites, and encrypted local backups, including the Abracadoo-adjacent variants that support the same transport story.

Current Shape

• 9 auxiliary transport and bridge records.

Representative Files

• ABRACADOO_HUMANKEY_ENCRYPTED_BACKUP.json
• ABRACADOO_HUMANKEY_MANUAL_MESSAGE bob.json
• ABRACADOO_HUMANKEY_MANUAL_MESSAGE alice.json
• ABRACADOO_HUMANKEY_PATH_INVITE bob.json
• ABRACADOO_HUMANKEY_LANE_INVITE bobby.json

Working Read

This is the transport edge of HumanKey: the place where encrypted state, manual delivery, and path invitations show up around the protocol core.

The page stays intentionally compact because these files are support evidence rather than the primary protocol drafts. They matter because they preserve the connective tissue between the app-side Abracadoo naming, the HumanKey message flow, and the trust-authentication lineage.

Related Links

• HumanKey Protocol
• Protocol Drafts and Submission
• Presentation Materials
• Abracadoo

Next Actions

1. Keep the core protocol and presentation tracks separate from the bridge records.
2. Add only the bridge material that clearly belongs to transport, invites, or encrypted local state.
3. Split again only if the transport layer develops a second durable seam.