Space Duck Trust Framework
Trust is earned through verification. Each tier unlocks more capabilities across the Space Duck ecosystem.
Trust Tiers
T0
Basic Account
Email verified. You exist in the system but haven't proven anything yet.
- ✅ Account created
- ✅ Email verified
- ❌ No birth certificate
- ❌ Cannot approve pecks
- ❌ No agent bonding
T1
Verified Duckling
Phone number verified via OTP. Birth certificate issued. Core platform features unlocked.
- ✅ Everything in T0
- ✅ Phone number verified (OTP)
- ✅ Birth certificate issued
- ✅ Can approve peck requests
- ✅ Agent bonding enabled
- ❌ Bulk operations unavailable
T2
Trusted Identity
Legal name and address provided. Highest trust level. Bulk operations and priority routing available.
- ✅ Everything in T1
- ✅ Legal name verified
- ✅ Address on record
- ✅ Bulk peck operations
- ✅ Priority peck routing
- ✅ Extended audit access
Feature Access by Tier
How Peck Trust Works
A peck is a permission request from an AI agent to its bonded duckling. The duckling's trust tier determines which pecks can be processed:
- T0 ducklings cannot approve any pecks — no cert means no peck authority.
- T1 ducklings can approve standard pecks and normal-priority requests.
- T2 ducklings can approve all pecks, including bulk and urgent requests.
- Every peck resolution — whether approved, denied, or expired — creates an audit log entry.
- Peck beak keys are validated on every request, regardless of prior approval history.
Verification Standards
Audit Trail
Every significant action across the Space Duck platform is logged in an immutable audit trail:
CERT_ISSUED — birth certificate created for a new duckling
PECK_REQUESTED — agent submitted a peck to its duckling
PECK_RESOLVED — duckling approved or denied the peck
AGENT_BONDED — new agent connected via beak key
TRUST_TIER_CHANGED — duckling moved to a higher trust tier
KEY_ROTATED — beak key rotated by operator
Audit records are retained for a minimum of 7 years and cannot be deleted or modified.

