demo outline.txt

Caliper Credential POC

Demonstrating Trusted Learning Context, Consent, and Controls

1. Executive Objective

Demonstrate how learning activity data can be transformed into trusted credentials and selectively shared using verifiable presentations, enabling controlled and consent-based workflows across institutions, platforms, and AI systems.

The demonstration will show:
	•	Learning activity captured via Caliper
	•	Transformation into Verifiable Credentials
	•	Aggregation into a Comprehensive Learner Record
	•	Selective disclosure via Verifiable Presentations
	•	User consent and governance controls
	•	Verification by a receiving system

The key message:

Learning data can become trusted, portable, and controllable learning context.

⸻

2. Demo Narrative (Executive Story)

Scenario: Internship Readiness Review

A learner participates in a course using multiple tools integrated via LTI.

These tools generate Caliper events.

The system transforms those events into trusted Caliper Credentials that describe:
	•	participation
	•	progress
	•	competencies
	•	achievements
	•	engagement evidence

Over time, these credentials accumulate into the learner’s Comprehensive Learner Record (CLR).

An employer or advisor requests proof of internship readiness.

The learner consents to share only relevant evidence.

The system generates a Verifiable Presentation containing:
	•	selected achievements
	•	competency evidence
	•	activity summaries
	•	issuer verification
	•	consent metadata

The verifier validates the presentation and accepts it as trusted evidence.

⸻

3. Demo Workflow

Step 1 — Activity Happens

Learning tools generate events such as:
	•	AssignmentSubmitted
	•	AssessmentCompleted
	•	ResourceViewed
	•	ForumPosted

These arrive as Caliper envelopes.

Example:

Learning Tool
   ↓
Caliper Event
   ↓
Caliper Envelope API


⸻

Step 2 — Event Transformation

The system transforms raw Caliper events into Caliper Credentials.

A credential represents a verified claim derived from activity evidence.

Example:

Credential: Assignment Completion

Subject: learner DID
Issuer: institution DID
Evidence: Caliper events
Context: course / LTI session

The credential is signed by the issuing platform.

⸻

Step 3 — Session Grouping

Events are grouped using:

federatedSessionId

This allows the system to build meaningful units such as:
	•	assignment attempts
	•	learning sessions
	•	course activities
	•	module completions

Grouped activity forms the basis for credentials.

⸻

Step 4 — CLR Assembly

The system can assemble credentials into a Comprehensive Learner Record.

The CLR contains:
	•	achievements
	•	competencies
	•	credentials
	•	activity evidence
	•	learning context

This becomes the persistent learning record.

Learner Record
   ├── Achievement VC
   ├── Competency VC
   ├── Activity VC
   └── Participation VC


⸻

Step 5 — Evidence Request

A verifier requests proof.

Example request:

Provide evidence of internship readiness.

The request specifies required claims such as:
	•	data literacy competency
	•	course completion
	•	collaboration evidence

⸻

Step 6 — Consent and Controls

The learner is presented with a consent screen.

They approve:
	•	who is requesting the data
	•	what information will be shared
	•	purpose of use
	•	duration of access

Example controls:

Control	Example
Audience	Employer
Purpose	Internship screening
Data scope	Competencies + achievements
Expiration	30 days
AI usage	Allowed


⸻

Step 7 — Verifiable Presentation Generation

The system creates a Verifiable Presentation containing selected credentials.

Example structure:

Verifiable Presentation
   ├── Achievement VC
   ├── Competency VC
   └── Activity Evidence VC

The presentation includes:
	•	holder signature
	•	consent metadata
	•	issuer verification

⸻

Step 8 — Verification

The receiving system verifies:
	•	issuer trust
	•	credential signatures
	•	schema validity
	•	revocation status
	•	consent scope

The verifier sees a trusted learning profile rather than raw activity logs.

⸻

4. Demo Screens (Very Important for Execs)

The POC should show four visual stages.

⸻

Screen 1 — Learning Activity

Show a timeline of events.

Example:

Learner Activity Timeline

10:02 Assignment started
10:15 Resource viewed
10:30 Forum discussion
11:10 Assignment submitted

Label this:

Learning Activity (Caliper Events)

⸻

Screen 2 — Trusted Credentials

Show events transformed into credentials.

Example:

Generated Credentials

✓ Assignment Completion Credential
✓ Collaboration Participation Credential
✓ Data Literacy Competency Credential

Label this:

Trusted Credentials Generated

⸻

Screen 3 — Consent and Sharing

Show learner approving data sharing.

Example:

Share learning evidence with:

Employer: TechCorp

Sharing:
✓ Data Literacy Competency
✓ Course Completion
✓ Collaboration Evidence

Not shared:
✗ Discussion history
✗ Full activity logs

Label this:

Learner Controlled Data Sharing

⸻

Screen 4 — Verification

Show the verifier view.

Example:

Verified Learning Evidence

Issuer: University
Status: Verified

Achievements
• Data Literacy Certificate
• Applied Analytics Course Completion

Evidence
• Assignment Completion
• Team Collaboration Activity

Label this:

Trusted Evidence Verified

⸻

5. Technical Architecture (Minimal POC)

Learning Tools
      │
      │ Caliper Events
      ▼
Caliper Ingestion API
      │
      ▼
Event Processing Service
      │
      ▼
Credential Builder
      │
      ▼
Credential Store
      │
      ▼
CLR Assembly Service
      │
      ▼
Presentation Service
      │
      ▼
Verifier UI


⸻

6. Required APIs

Caliper Ingest

POST /caliper/events

Accepts:

CaliperEnvelope


⸻

LTI Context Ingest

POST /lti/context

Creates context credentials.

⸻

Query CLR

GET /learner/{id}/clr

Returns assembled record.

⸻

Create Presentation

POST /presentation/create

Input:

{
  "learnerId": "...",
  "request": "internship-readiness",
  "audience": "employer"
}

Output:

VerifiablePresentation


⸻

Verify Presentation

POST /presentation/verify


⸻

7. What the POC Proves

This demonstration proves that learning data can become:

Trusted

Evidence is cryptographically verifiable.

Portable

Credentials move between systems.

Controlled

Learners control disclosure.

Governed

Policies determine what is shared.

AI-Ready

Trusted learning context can be safely provided to AI systems.

⸻

8. Key Executive Message

Your closing statement should be:

This architecture allows learning activity to become trusted digital evidence that can be shared selectively and safely across institutions, employers, and AI systems while preserving learner control.