feat: (core) Binding Documents Framework

[coodos]

Summary

Define a unified framework for creating, storing, verifying, and displaying binding documents that evolve an identity's trust level.

Supported binding document types

• PHYSICAL_ID
• PASSPHRASE
• PHOTO
• FRIEND

Canonical rules

• Every binding document must specify:
  • subject eName
  • issuer identity
  • signature(s)
  • created timestamp
  • revocation status
• FRIEND binding documents are invalid until countersigned by the subject.
• PASSPHRASE material is never readable and is only comparable via Protected Zone functions.
• All writes and overrides are auditable.

Storage rules

• Protected Zone (non-readable):
  • passphrase hash material
• Encrypted binding-doc sector:
  • physical id bindings
  • photo bindings
  • friend bindings
  • self-asserted profile bindings
• Append-only audit log sector:
  • records every write or override

Binding document model

classDiagram
 class BindingDocument {
 docId
 type
 subjectEName
 issuerId
 issuerType
 evidenceRefOrPayloadHash
 createdAt
 expiresAt
 revoked
 signature
 countersignRequired
 countersignSignature
 countersignedAt
 }

 class VaultSector {
 name
 accessPolicy
 }

 BindingDocument --> VaultSector : storedIn

Loading

Acceptance criteria

• A single binding document schema is used across all binding types.
• FRIEND binding documents are treated as invalid unless countersigned by the subject.
• PASSPHRASE hash material is stored only in the Protected Zone and is non-readable.
• All binding document writes, countersigns, revocations, and overrides emit audit events.
• Binding documents can be listed and verified deterministically using schema fields.