Grant Capability
Overview
Award a verified skill or capability to a human or agent based on demonstrated evidence. Every capability grant is cryptographically signed, provenance-tracked, and backed by evidence—making it verifiable and unforgeable.
Why Grant Capabilities?
Think of it like: Earning a certification, but it's backed by real work you've done, cryptographically verified, and follows you everywhere.
SDK Examples
REST API Example
POST /v1/capability-graph/grant
Content-Type: application/json
Authorization: Bearer {
"recipientDid": "did:human:alice-smith",
"capability": {
"name": "ai_safety_evaluation",
"category": "ai_safety",
"weight": 0.8
},
"evidence": {
"type": "task_completion",
"description": "Successfully completed 15 AI safety evaluations with 95% accuracy",
"metadata": {
"taskType": "safety_evaluation",
"tasksCompleted": 15,
"accuracyRate": 0.95,
"startDate": "2026-01-01",
"endDate": "2026-01-10"
},
"signedBy": "did:human:supervisor-bob"
}
}
Response (201 Created):
{
"capabilityId": "capability:human:a1b2c3d4...",
"recipientDid": "did:human:alice-smith",
"name": "ai_safety_evaluation",
"weight": 0.8,
"evidenceCount": 1,
"ledgerProof": "0x7b3f9a2c...",
"createdAt": "2026-01-10T12:00:00Z"
}
Types of Evidence
Capabilities require evidence to be granted. Here are the supported types:
| Evidence Type | Description | Example |
|---|---|---|
task_completion | Demonstrated through work | 50 data labeling tasks completed with 98% accuracy |
training | Academy courses or certifications | Completed "AI Safety Fundamentals" course |
credential | External credentials imported | AWS Solutions Architect certification |
peer_review | Endorsed by another human | 5 engineers vouch for your Python expertise |
manual | Admin/supervisor manual attestation | Manager attests to leadership capability |
Skill Recognition
Award capabilities after completing training courses or certifications
Performance Reviews
Grant capabilities based on demonstrated work quality
Agent Qualification
Define and grant specific capabilities to AI agents based on testing
Task Routing
Use granted capabilities to match qualified workers to tasks
Use Cases
1. Grant Capability After Training
Scenario: A human completes training in the HUMΛN Academy—automatically grant the capability.
2. Grant Capability After Task Completion
Scenario: A human completes multiple tasks in the Workforce Cloud—capability weight increases with demonstrated proficiency.
3. Import External Credential
Scenario: A human has an external credential (AWS cert, university degree)—import it as a capability.
Capability Weights
Capability weights range from 0.0 to 1.0, representing confidence/proficiency:
| Weight Range | Meaning | Example |
|---|---|---|
0.0 - 0.3 | Novice | Just started learning Python |
0.3 - 0.6 | Intermediate | Can complete routine Python tasks |
0.6 - 0.8 | Advanced | Expert-level Python development |
0.8 - 1.0 | Master | World-class Python expertise, mentors others |
DO
Require cryptographic proof of evidence before granting
Set appropriate confidence levels (weight) based on evidence quality
Anchor all capability grants to the provenance ledger
Implement expiry dates for time-sensitive capabilities
DON'T
Grant capabilities without verifiable evidence
Allow self-attestation without third-party validation
Over-inflate capability weights to game routing
Skip verification of the grantor's authority
Provenance
Every capability grant is permanently recorded:
{
"eventType": "capability_granted",
"recipientDid": "did:human:alice-smith",
"capabilityName": "ai_safety_evaluation",
"weight": 0.8,
"evidenceType": "task_completion",
"attestorDid": "did:human:supervisor-bob",
"ledgerSignature": "0x7b3f9a2c...",
"timestamp": "2026-01-10T12:00:00Z"
}
This creates an immutable capability history that can be verified by anyone.
Skill Recognition
Award capabilities after completing training courses or certifications
Performance Reviews
Grant capabilities based on demonstrated work quality
Agent Qualification
Define and grant specific capabilities to AI agents based on testing
Task Routing
Use granted capabilities to match qualified workers to tasks
DO
Require cryptographic proof of evidence before granting
Set appropriate confidence levels (weight) based on evidence quality
Anchor all capability grants to the provenance ledger
Implement expiry dates for time-sensitive capabilities
DON'T
Grant capabilities without verifiable evidence
Allow self-attestation without third-party validation
Over-inflate capability weights to game routing
Skip verification of the grantor's authority
Next Steps
---