Skip to content

Ingest FriendR public claim/stamp/disclosure contract into SDK #31

Description

@KazanderDad

Summary

Ingest the FriendR unique-human-confidence public contract into the canonical public SDK without adding a new runtime integration package.

Owning coordination

  • Requesting issue: https://github.com/Cubid-Me/cubid-monorepo/issues/98
  • Parent release goal: https://github.com/Cubid-Me/cubid-monorepo/issues/95
  • Responding issue: this issue
  • Requested outcome: public constants, types, classification helpers, generated references, and safe documentation for the existing Cubid contract.
  • Expected handoff: reviewed SDK PR and exact released/merged contract evidence posted reciprocally to #98.
  • Status: open; SDK implementation remains owned here.
  • Blockers: none asserted by cubid-monorepo. SDK maintainers must validate current package surfaces before implementation.

Contract

  • Actor self-claim remains Cubid-owned as cubid_actor_type.
  • self_account_type_claim_v1 is a compatibility alias, not a mutable source of truth.
  • cubid_kyc_presence_v1 is coarse, UserInfo/disclosure eligible, and not ID-token eligible by default.
  • FriendR aggregate stamp type is friendr_unique_human_confidence_v1.
  • Redacted summary claim is friendr_unique_human_confidence, scoped to cubid:stamps, UserInfo/disclosure-only.
  • FriendR score effects appear only through existing consented cubid:score outputs.
  • Redirect parameters and default ID tokens must not carry FriendR-derived evidence.
  • Agent/organization evidence must not be represented as human personhood evidence.

Forbidden public modeling

Do not expose raw graphs, relationships, classifier/target identities, individual attestations, duplicate reports, contacts, XP, raw aggregate payloads, KYC provider details, or internal Cubid identifiers.

Acceptance

  • Add public constants/types and safe classification helpers in the canonical packages.
  • Document the scope/token/redirect boundaries.
  • Regenerate references and pass focused/full SDK validation.
  • Post the reviewed implementation handoff reciprocally to cubid-monorepo #98.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions