Coverage matrix
This matrix is a manually seeded public artifact. It distinguishes protocol specification, docs, executable reference behavior, tests, demonstration surfaces, and intentionally deferred scope.
| Concept / flow | Category | Specified | Documented | Implemented | Tested | Demonstrated | Status | Evidence |
|---|---|---|---|---|---|---|---|---|
Grant request, consent, token issue, and revocation Runnable in the reference stack; public demonstration is currently explanatory rather than a live hosted flow. | Protocol flow | Yes | Yes | Yes | Yes | Partial | Implemented | |
Grant-scoped stream and record query enforcement Reference behavior covers stream lists, record reads, projection, rejection, and trace evidence. | Protocol flow | Yes | Yes | Yes | Yes | Partial | Implemented | |
Owner self-export and owner-token reads Owner access is modeled separately from third-party grant access. | Protocol flow | Yes | Yes | Yes | Yes | Partial | Implemented | |
Provider discovery and protected-resource metadata Discovery is implemented for local/self-hosted instances; no public hosted instance is promised. | Protocol flow | Yes | Yes | Yes | Yes | No | Implemented | |
Lexical retrieval at /v1/search Dashboard evidence is operator-facing live state, not protocol documentation. | Retrieval extension | Yes | Yes | Yes | Yes | Partial | Implemented | |
Semantic retrieval at /v1/search/semantic The extension is intentionally experimental; coverage is honest about index and connector-field limits. | Retrieval extension | Yes | Yes | Partial | Yes | Partial | Partial | |
Collection manifest, connector run, STATE checkpoint, and runtime requirements Reference connectors exercise seeded, native, and polyfill-backed collection paths. | Collection profile | Yes | Yes | Yes | Yes | Partial | Implemented | |
Native source binding and connector identity Reference tests cover binding-aware enforcement and connector-visible source identity. | Collection profile | Yes | Yes | Yes | Yes | Partial | Implemented | |
Reference traces, grant timelines, and run timelines Reference-only diagnostics explain this implementation; they do not extend the protocol contract. | Reference control plane | N/A | Yes | Yes | Yes | Partial | Reference-only | |
Reference records, runs, and deployment diagnostics dashboard Dashboard pages are live/operator surfaces and are intentionally outside public protocol docs. | Reference control plane | N/A | Yes | Yes | Yes | Partial | Reference-only | |
Mock sandbox protocol walkthroughs End-to-end mock walkthrough covers request, owner consent, scoped query, revocation, and post-revocation refusal. Fixtures are fictional and the page never asks for real credentials. | Sandbox | N/A | Yes | Yes | Yes | Yes | Implemented | |
Semantic subset grants and predicate-in-grant Intentionally excluded from v0.1 to avoid unreviewable consent predicates. | Deferred scope | Partial | Yes | No | N/A | N/A | Deferred | |
Source writeback and event-driven collection triggers Future profiles may add these capabilities without changing current read-oriented grants. | Deferred scope | Partial | Yes | No | N/A | N/A | Deferred | |
Standardized cross-connector view names Current manifests may define views, but portable cross-connector view semantics are not standardized. | Deferred scope | Partial | Yes | No | N/A | N/A | Deferred |