Connect learning events through an explicit contract

A connector maps platform activity into versioned GDP events. Tenant, identity, idempotency, signing, source lineage, permission, and deletion are part of the API contract.

Integration protocols

Standard event inputs with one governance boundary

xAPI, Caliper, Webhook, and OAuth adapt source systems while AlphaEDU keeps a stable connector and event contract. LTI 1.3, OneRoster, W3C VC, Open Badges, CLR, consortium-chain adapters, and AEDU contribution events are part of the public standards and governance contract.

Active protocol 01

Learning activity vocabulary

Mapped into a versioned GDP event

xAPI

Register connector

Event model

The minimum event envelope

Raw content stays inside a controlled source boundary. The growth lineage receives a scoped, identity-mapped, and versioned learning event.

eventIdStable idempotency key

tenantRefOpaque organization or platform boundary

userRefMapped learner identity, never a browser access token

occurredAtSource event time with timezone

activityTyped learning action

evidenceRefsSource-owned evidence references

mappingVersionVersioned GDP mapping contract

Event example

{
  "eventId": "evt_01J...",
  "tenantRef": "tenant_opaque",
  "userRef": "learner_opaque",
  "occurredAt": "2026-07-26T09:30:00Z",
  "activity": "learning.activity.completed",
  "evidenceRefs": ["source:activity/4821"],
  "mappingVersion": "gdp-event/1"
}

Operating requirements

Failure must recover; replay must have no side effect

Connector health, rate limits, error codes, and deletion outcomes enter the control plane. Events deduplicate by idempotency key and isolate by tenant and identity mapping. AI draft and human confirmation follow ingestion; permission governs use.