AI Use Case Register
Purpose: A public, on-chain record of every AI tool and practice used at Future’s Edge. Updated continuously. Anyone can view it.
AI use case register entry template
Section titled “AI use case register entry template”Record ID: [Auto-generated on approval]
Status: ☐ Active ☐ Under review ☐ Suspended ☐ Retired
Basic information
Section titled “Basic information”Tool or practice name:
Plain-language description (what it does, in one sentence):
Category:
☐ Governance (voting, proposals, reputation)
☐ Learning (recommendations, feedback, assessment)
☐ Community (moderation, matching, communication)
☐ Operations (admin, scheduling, analytics)
☐ Economic (compensation, bounty calculation, verification)
☐ Content (generation, curation, translation)
Accountability
Section titled “Accountability”Named tool owner:
Name: _______________
Role: _______________
Contact: _______________
Human oversight mechanism:
☐ Manual review of all decisions
☐ Sampling-based review (frequency: _______________)
☐ Automated alerts for threshold events
☐ Regular audit trail review
☐ Other: _______________
Data and privacy
Section titled “Data and privacy”What data does this tool use?
Data retention period:
Can members view their data? ☐ Yes ☐ No
Can members request deletion? ☐ Yes ☐ No ☐ Partial
Bias and inclusion
Section titled “Bias and inclusion”Bias audit status:
Last audit date: _______________
Next audit due: _______________
Audit outcome: ☐ No disparities detected ☐ Disparities detected (see notes)
Performance tested across:
☐ Gender ☐ Language ☐ Geography ☐ Cultural background ☐ Socioeconomic status
Notes or remediation actions:
Impact assessment
Section titled “Impact assessment”CIA completed: ☐ Yes — Date: _______________
CIA Record ID: _______________
Ethics Circle approval date: _______________
Stakeholder groups affected:
☐ Youth members
☐ Under-served populations
☐ Emerging economy participants
☐ Small business / clients
☐ Partner organisations
☐ Local communities
☐ Staff / contractors
Member challenge pathway
Section titled “Member challenge pathway”Can affected people challenge decisions made by this tool?
☐ Yes — Process: _______________
☐ No — Justification: _______________
Number of challenges received to date: _______________
Number upheld: _______________
Version history
Section titled “Version history”| Version | Date | What changed | Why |
|---|---|---|---|
| 1.0 | Initial deployment | ||
Public notes
Section titled “Public notes”Space for the tool owner to add context, learnings, or updates:
Record created: _______________
Last updated: _______________
Next review due: _______________
Published: ☐ Yes — View at [URL]
On-chain record: [Blockchain transaction ID]