Uploaded November 2026 | Updated November 2026, 3 days ago
In this episode of AI Coding with Dr. Chuck, I work on making published Open Badges in Tsugi completely self-contained.
The existing badge implementation still depends on live course data, including Lessons content and other relational information. That creates a long-term problem: courses should eventually be retired, student activity should not be retained forever, and a published credential should remain valid even after the original course environment is gone.
The solution is deliberate denormalization. When a badge is published, Tsugi now captures the information needed to render and verify that badge into the badge record itself, including accomplishments and other evidence that previously came from live course data.
I also work through badge image preservation. Instead of depending indefinitely on an external image file, the system stores badge images separately using SHA-256 for deduplication and can transparently fall back to the stored image if the original file disappears.
The goal is an “air gap” between a published credential and the rest of the learning platform: the course, learner account, lesson structure, and original files can eventually disappear while the badge remains complete and verifiable.
Topics include:
Open Badges
Badge denormalization
Long-lived digital credentials
Credential portability
Learner privacy
Relational database design
Data retention
SHA-256
Binary image storage
Database BLOBs
Idempotent migrations
Backfilling existing records
Fallback image storage
Tsugi
Open Badges 3
LinkedIn credentials
AI-assisted software development
In this episode of AI Coding with Dr. Chuck, I work on making published Open Badges in Tsugi completely self-contained.
The existing badge implementation still depends on live course data, including Lessons content and other relational information. That creates a long-term problem: courses should eventually be retired, student activity should not be retained forever, and a published credential should remain valid even after the original course environment is gone.
The solution is deliberate denormalization. When a badge is published, Tsugi now captures the information needed to render and verify that badge into the badge record itself, including accomplishments and other evidence that previously came from live course data.
I also work through badge image preservation. Instead of depending indefinitely on an external image file, the system stores badge images separately using SHA-256 for deduplication and can transparently fall back to the stored image if the original file disappears.
The goal is an “air gap” between a published credential and the rest of the learning platform: the course, learner account, lesson structure, and original files can eventually disappear while the badge remains complete and verifiable.
Topics include:
Open Badges
Badge denormalization
Long-lived digital credentials
Credential portability
Learner privacy
Relational database design
Data retention
SHA-256
Binary image storage
Database BLOBs
Idempotent migrations
Backfilling existing records
Fallback image storage
Tsugi
Open Badges 3
LinkedIn credentials
AI-assisted software development










