Skip to content

Integration Catalog

Universal Manifest is designed to work across any domain that needs portable identity, credentials, and consent. The manifest structure — subject, shards, pointers, claims, consents, TTL — is intentionally generic. Integration lanes show how specific industries and use cases map their concepts onto this common structure.

Each integration lane is non-normative guidance. The core specification stays the same regardless of domain. A healthcare manifest and a smart home manifest share the same required fields, the same TTL model, and the same unknown-field tolerance. The lanes below describe conventions for shard names, pointer keys, consent keys, and claim keys that make adoption easier in each domain.

This catalog organizes integration lanes by category. Existing lanes link to their documentation pages. Planned lanes are marked for contribution. If your domain is not listed, the template and authoring guide make it straightforward to create a new lane.


Portable identity, profile projection, and social graph interoperability.

LaneStatusDescription
Social/ProfilePublishedWeb profile pages, public identity views, ActivityPub pointers
ActivityPub/FediversePlannedNative ActivityPub actor integration and federated identity
Professional NetworksPlannedLinkedIn-style professional profiles and endorsements
Dating PlatformsPlannedPrivacy-first dating profiles with consent-gated disclosure
Gaming ProfilesPlannedCross-platform gaming identity, achievements, and reputation

Proof of identity, personhood, and trust attestation across providers.

LaneStatusDescription
Proof of PersonhoodPublishedMulti-provider personhood credentials (World ID, Gitcoin Passport, BrightID)
OMATrustPublishedOpen Media Attestation trust lifecycle and proof-based services
KYC/AMLPlannedKnow-your-customer and anti-money-laundering credential portability
Age VerificationPlannedPrivacy-preserving age attestation without revealing birthdate
Academic CredentialsPlannedDegree and certification verification (see Education category)

Cross-world identity, AR overlays, spatial computing, and immersive experiences.

LaneStatusDescription
MetaversePublishedCross-world avatar, inventory, and social graph portability
RP1 Spatial FabricPublishedSpatial computing identity and GeoPose-aware manifest projection
Smart Glasses ARPublishedAR social overlays, face-visibility consent, recording permissions
VR SocialPlannedVR-specific social presence, voice consent, and avatar rights
Digital TwinsPlannedPhysical-to-digital asset representation and sync
Location-Based ServicesPlannedGeofenced consent and location-aware manifest behavior

Device identity, household policy, and machine-to-machine manifest exchange.

LaneStatusDescription
Reference RuntimePublishedVenue display devices, edge issuance, push-pull transport
Smart HomeNewHousehold privacy policy, device onboarding, automation rules
WearablesPlannedFitness trackers, health monitors, and biometric consent
AutomotivePlannedVehicle identity, driver profiles, and connected car consent
Industrial IoTPlannedFactory device identity, safety policy, and supply chain attestation

Decentralized identity, on-chain credentials, and Web3 wallet integration.

LaneStatusDescription
Chia DID/VCPublishedChia blockchain DID and Verifiable Credential attestation
Ethereum ENSPlannedENS name resolution and Ethereum-based identity binding
Solana DIDPlannedSolana-native decentralized identifiers and credential anchoring
IPFS-Backed ManifestsPlannedContent-addressed manifest storage and retrieval via IPFS

Patient consent, health data portability, and clinical system interoperability.

LaneStatusDescription
Healthcare Patient ConsentNewPatient consent, allergy alerts, emergency contacts
Health Records PortabilityPlannedFHIR-compatible health record references and consent-gated access
Fitness DataPlannedWorkout logs, biometric readings, and wellness goal sharing

Loyalty programs, payment preferences, and merchant trust.

LaneStatusDescription
Loyalty ProgramsPlannedCross-merchant loyalty point portability and reward redemption
Payment PreferencesPlannedPreferred payment methods and billing address consent
Merchant TrustPlannedMerchant reputation and consumer protection attestations
Supply ChainPlannedProduct provenance, certification, and chain-of-custody tracking

Digital identity, civic credentials, and cross-border interoperability.

LaneStatusDescription
Digital IDPlannedGovernment-issued digital identity document portability
Voting EligibilityPlannedPrivacy-preserving eligibility attestation without revealing identity
Permits & LicensesPlannedProfessional and activity permits with verifiable status
Cross-Border CredentialsPlannedInternational credential recognition and mutual trust frameworks

Academic credentials, learning records, and skill attestations.

LaneStatusDescription
Education CredentialsNewDegrees, certifications, learning records, skill attestations
Learning RecordsPlannedMicro-credentials, course completions, and competency tracking
Skill AttestationsPlannedEmployer-issued and peer-validated skill endorsements

Content licensing, creator attribution, and rights management.

LaneStatusDescription
Content LicensingPlannedMedia license terms, usage rights, and distribution consent
Creator AttributionPlannedProvenance and authorship claims for digital content
Rights ManagementPlannedDRM-free rights assertions and royalty split references

Want to add an integration lane for your domain? The process is template-driven and designed to be followed by AI agents or human contributors with zero additional context.

  1. Read the authoring guide: Integration Lane Authoring Guide — step-by-step instructions, naming conventions, and quality checklist.
  2. Copy the template: TEMPLATE.md — fill-in-the-blank template that produces a complete, valid integration document.
  3. Create your lane: Fill in the template for your domain, write an example fixture, and validate it against the v0.1 schema.
  4. Submit for review: Place the file in integrations/ and it will be reviewed.

The template covers: overview, normative boundary, use cases, manifest structure (shards, pointers, consents, claims), consumer/issuer behavior, example fixture, proof coverage, and implementation checklist.