Humanitarian Service Marketplace – Credential Catalog

Industry-standard ACDC credential types for the humanitarian-service-marketplace ecosystem. Generated by /keri-c0-ecosystem. Schema fields define the ACDC a (attributes) block.

Credential Summary

Credential Details

State-Endorsed Digital Identity (sedi_identity)

Description: Government-issued digital identity credential backed by KERI protocols. The gold standard root of identity. Utah is leading adoption with multi-state expansion underway. Apple and Google wallets in talks for integration. Provides the foundational identity that all other credentials reference.

Issuer role: government_agency Holder role: individual Verifier roles: service_platform, grassroots_org, kyv_provider, credential_provider, government_agency Disclosure mode: selective

Schema Fields

Privacy Notes

• Supports selective disclosure via ACDC graduated disclosure. Verifiers receive only the fields they request.
• Holder can prove possession without revealing attribute values (compact disclosure).
• A volunteer matching a service need may only need to prove “is a verified person in this jurisdiction” without revealing name, address, or date of birth.

Know Your Volunteer Credential (kyv_credential)

Description: Composable credential attesting that a volunteer has been vetted to a specific standard. Built from component credentials (background checks, training certs, psych evals, etc.). Multiple KYV standards coexist — each with different compositions and trust levels. The ACDC chaining makes the composition transparent so verifiers can see exactly what went into it.

Issuer role: kyv_provider Holder role: individual Verifier roles: service_platform, grassroots_org, individual Disclosure mode: selective

Schema Fields

Credential Chaining

This credential chains from background_check. The issuer MUST hold a valid, unrevoked background_check credential. The edge block (e) of this ACDC references the chained credential’s SAID, creating a cryptographically verifiable provenance chain.

Privacy Notes

• Supports selective disclosure via ACDC graduated disclosure. Verifiers receive only the fields they request.
• A service requester may only need to verify “has valid KYV” without seeing which components were checked.
• Component credential details are available to verifiers who need deeper assurance.

Skill/Training Certificate (skill_credential)

Description: Credential issued by a training provider, trade school, or licensing body attesting to a specific skill or qualification. CPR certification, electrical license, painting certification, medical training, harassment awareness, etc. The issuing entity is also the verifier.

Issuer role: credential_provider Holder role: individual Verifier roles: service_platform, grassroots_org, individual, kyv_provider Disclosure mode: full

Schema Fields

Privacy Notes

• Full disclosure: all schema fields are revealed to verifiers on presentation.
• Skill credentials are generally non-sensitive and benefit from full transparency to build trust.

Verified Service Record (service_record)

Description: Credential attesting that a volunteer performed a specific service. Issued by the party that received the service or the platform that coordinated it. Accumulates over time to build portable reputation. Includes verification method metadata (geolocation, biometric, digital tool, manual attestation) so verifiers can assess proof strength.

Issuer role: service_platform Holder role: individual Verifier roles: service_platform, grassroots_org, government_agency, individual Disclosure mode: selective

Schema Fields

Credential Chaining

This credential chains from proof_of_service. The issuer MUST hold a valid, unrevoked proof_of_service credential. The edge block (e) of this ACDC references the chained credential’s SAID, creating a cryptographically verifiable provenance chain.

Privacy Notes

• Supports selective disclosure via ACDC graduated disclosure. Verifiers receive only the fields they request.
• Government agencies for tax reporting see aggregated hours without personal service details.
• Location and biometric data are highly sensitive — disclosed only when contractually required.

Equipment/Tool Availability (equipment_inventory)

Description: Self-asserted credential listing tools and equipment a volunteer has access to — from gloves and shovels to backhoes and heavy equipment. Can be endorsed by organizations that have witnessed the equipment in use, which increases trust.

Issuer role: individual Holder role: individual Verifier roles: service_platform, grassroots_org, individual Disclosure mode: full

Schema Fields

Privacy Notes

• Full disclosure: all schema fields are revealed to verifiers on presentation.
• Self-asserted with optional endorsements — verifiers can weigh trust accordingly.

Organization Membership (org_membership)

Description: Credential attesting that an individual is a member of a service organization or grassroots group. Enables cross-platform discovery and attribution tracking.

Issuer role: service_platform Holder role: individual Verifier roles: service_platform, grassroots_org, individual Disclosure mode: full

Schema Fields

Privacy Notes

• Full disclosure: all schema fields are revealed to verifiers on presentation.

Service Need Publication (service_need)

Description: Declarative credential publishing a need for service. Issued by an individual, grassroots org, or service platform. Uses selective disclosure to protect requester vulnerability — only qualified volunteers see full details. Publication scope follows the graduated model: friends/family, neighborhood, community, city, organizations. AI assists with formality gap-filling.

Issuer role: individual Holder role: individual Verifier roles: service_platform, grassroots_org, individual Disclosure mode: selective

Schema Fields

Privacy Notes

• Supports selective disclosure via ACDC graduated disclosure. Verifiers receive only the fields they request.
• Requester vulnerability is protected — “elderly person needs yard help” shows as “yard work needed in [area]” to unqualified viewers.
• Full details disclosed only to volunteers who meet the credential and KYV requirements.

Service Commitment Agreement (service_commitment)

Description: Contractual credential where a volunteer commits to meeting a published service need. Binds the volunteer to the terms of the service need. Forms the basis for proof-of-service verification — you cannot prove you did something you did not agree to do.

Issuer role: individual Holder role: individual Verifier roles: service_platform, grassroots_org, individual Disclosure mode: full

Schema Fields

Credential Chaining

This credential chains from service_need. The edge block (e) of this ACDC references the service need’s SAID, creating a cryptographically verifiable link between the commitment and the original need.

Privacy Notes

• Full disclosure: all schema fields are revealed to verifiers on presentation.
• Transparency in commitments builds trust and enables dispute resolution.

Proof of Service (proof_of_service)

Description: Automated or manual proof that service was rendered. Multi-modal verification: geolocation + barometric + biometric (phone KEL logs), digital tool interaction logs, or manual sponsor attestation. Each method produces a different verification strength. Chains from service_commitment.

Issuer role: verification_service Holder role: individual Verifier roles: service_platform, grassroots_org, individual, government_agency Disclosure mode: selective

Schema Fields

Credential Chaining

This credential chains from service_commitment. The issuer MUST reference the service commitment’s SAID. The edge block (e) of this ACDC references the chained credential’s SAID, creating a cryptographically verifiable provenance chain from need → commitment → proof.

Privacy Notes

• Supports selective disclosure via ACDC graduated disclosure. Verifiers receive only the fields they request.
• Location and biometric data are highly sensitive — disclosed only under contractual obligation.
• Government tax reporting receives only hours and verification strength, not raw location/biometric data.

Platform Registration (platform_registration)

Description: Government-issued credential recognizing a service platform as a registered nonprofit or service organization. Not required for grassroots participation but necessary for formal organizations seeking tax-exempt status and government reporting integration.

Issuer role: government_agency Holder role: service_platform Verifier roles: government_agency, service_platform, individual Disclosure mode: full

Schema Fields

Privacy Notes

• Full disclosure: all schema fields are revealed to verifiers on presentation.
• Public organizations benefit from full transparency of their registration status.

KYV Standard Definition (kyv_standard)

Description: Published definition of a Know Your Volunteer standard — specifying what component credentials are required, what verification methods are accepted, and what governance processes must be followed. Multiple standards coexist. Organizations can adopt existing standards or define their own.

Issuer role: service_platform Holder role: kyv_provider Verifier roles: kyv_provider, individual, service_platform Disclosure mode: full

Schema Fields

Privacy Notes

• Full disclosure: all schema fields are revealed to verifiers on presentation.
• Standards are public documents — transparency enables informed participation.

Interoperability Agreement (interop_agreement)

Description: Mutual credential between service platforms establishing cross-platform interoperability — shared service need publication, volunteer credential recognition, and service record portability. Defines which KYV standards each platform recognizes from the other.

Issuer role: service_platform Holder role: service_platform Verifier roles: service_platform, grassroots_org Disclosure mode: full

Schema Fields

Privacy Notes

• Full disclosure: all schema fields are revealed to verifiers on presentation.
• Interoperability agreements are public commitments between platforms.

Background Check Result (background_check)

Description: Credential issued by a verification service attesting to the results of a background check. A component credential that feeds into KYV credentials. Uses selective disclosure — the KYV provider sees what they need, but the full details are not exposed beyond that.

Issuer role: verification_service Holder role: individual Verifier roles: kyv_provider Disclosure mode: selective

Schema Fields

Privacy Notes

• Supports selective disclosure via ACDC graduated disclosure. Verifiers receive only the fields they request.
• Highly sensitive — only KYV providers who need it for composing KYV credentials should access this.
• The individual controls when and to whom this is disclosed.

Guardian Delegation Authority (guardian_delegation)

Description: Credential establishing a guardian’s authority to manage a delegated AID on behalf of a ward (minor, elderly, person with disabilities). The ward retains their own AID — the guardian’s delegated AID operates within a cryptographically bounded scope. May originate from the individual, a family agreement, or a court order. Revocable when the ward gains capacity.

Issuer role: individual Holder role: guardian Verifier roles: service_platform, grassroots_org, government_agency Disclosure mode: selective

Schema Fields

Privacy Notes

• Supports selective disclosure via ACDC graduated disclosure. Verifiers receive only the fields they request.
• The ward’s identity and the nature of their need for guardianship are highly sensitive.
• Platforms may only need to verify “this guardian is authorized to act for this AID” without details.

Service Attribution Agreement (attribution_agreement)

Description: Contractual credential between platforms defining how service hours are attributed when volunteers cross organizational boundaries. Based on the social graph of contribution — who published the need, who matched the volunteer, where credentials came from, who verified completion. Ensures fair recognition without double-counting.

Issuer role: service_platform Holder role: service_platform Verifier roles: service_platform, government_agency Disclosure mode: full

Schema Fields

Credential Chaining

This credential chains from interop_agreement. The issuer MUST hold a valid, unrevoked interop_agreement credential with the partner platform. The edge block (e) of this ACDC references the chained credential’s SAID, creating a cryptographically verifiable provenance chain.

Privacy Notes

• Full disclosure: all schema fields are revealed to verifiers on presentation.
• Attribution agreements are public commitments supporting fair hour recognition.

Credential Dependency Graph

Lists chaining relationships between credentials in this ecosystem.

background_check --> kyv_credential
proof_of_service --> service_record
service_need --> service_commitment
service_commitment --> proof_of_service
interop_agreement --> attribution_agreement

Next Steps

• Run /keri-c1-system to design services that issue, hold, and verify these credentials.
• Credential schemas are anchored in the ecosystem’s schema registry once C2 infrastructure is deployed.