Implementation status uses a two-axis system to track both API coverage and verification level.
Unless specified:
How much of the API surface is implemented?
| Status | Description |
|---|---|
| Empty | Only namespace/placeholder, no API implementation |
| Partial | Some APIs implemented, some missing |
| Blocked | Most implementation complete, some blocked by dependencies |
| Complete | All APIs implemented |
How was the implementation created and verified?
| Status | Description |
|---|---|
| Verified | Implementation confirmed against reference binary |
| Generated | Auto-generated implementation, pending verification |
| Stubbed | Placeholder logic (returns default values or throws) |
Status can be expressed as: [Coverage] or [Coverage]-[Verification]
Complete implies Verified, so the verification suffix is omittedVerifiedExamples:
Complete: All APIs implemented and confirmed against referenceComplete-Generated: All APIs implemented but pending verificationPartial-Stubbed: Some APIs exist as placeholders only| Legacy Status | New Status Equivalent |
|---|---|
| Empty | Empty-Stubbed |
| WIP | Partial-* |
| Blocked | Blocked-* |
| Complete | Complete |