KIDs overview

KID	Commentary	Contents	Status	Ownership/primary author
0000	X	Glossary, overview, how to use	on hold	henk+juan
0001	X	Prefixes, Derivation and derivation reference tables	incoming	seth
0002	X	Data model (field & event concepts and semantics)	incoming	tbd
0003	X	Serialization	strawman but PRs incoming (sam+charles)	charles
0004	X	Key Configuration (Signing threshold & key set)	strawman	michael
0005	X	Next Key Commitment (Pre-Rotation)	strawman	juan
0006	X	Seals	strawman (pending PR by Sam)	juan
0007	X	Delegation (pending PR by Sam)	strawman	juan
0008	X	Key-Event State Machine	tbd	tbd
0009	X	Indirect Mode & Witnesses	incomplete strawman	tbd
0010	tbd	Recovery/Consensus Algorithm (KAACE)	strawman	phil
0011	tbd	Database & Storage Considerations	on hold	tbd
0097	n/a	Non-Normative Implementation Guidance	on hold	tbd
0098	n/a	Use Cases	incoming	(Michael, Robert, Charles, and GLEIF?)
0099	n/a	Test Vectors and Normative Statement Index	on hold for final editorial review	tbd

Further Documentation waiting on stable code development

• KID0011 - Recovery/consensus Algorithm (KAACE)
  • Roles: Validator, Witness, etc
  • Normative API assumptions between all the reference implementations? (Leave for later? Decide how much of this is non-normative after WG-wide discussion :D )
• KID0012 - Databases
  • Right to erasure (see digest agility Issue)
• KID0097 - Non-Normative Implementation Guidance
  • Key Creation
  • Key Storage
  • Event Signing
• KID0099 - Test Vectors & Normative Statements
  • Validation table
  • Index of normative statements

Out of scope for now (incl. future/separate specs/work items)

• Implementation Details
  • Storage? Database mechanics specified?
  • Common API
    • KMS API assumptions
  • Discovery (KERI-Dehmlia)
    • GH Issue on delegation mechanics
    • “Layer above KERI” spec - work item for the future?
  • Transport
  • Extracting an event from an HTTP header? appendix?