mdbase v0.3
Implementation support
mdbase v0.3 uses atomic profiles. Each row below names an artifact, version, evidence date, and the profiles it claims. Atomic profiles replace the legacy “Level 6” descriptions.
Conformance claims
| Artifact | Version | Profiles | Evidence |
|---|---|---|---|
| mdbase-rs Rust | 0.4.0-rc.3 | core_readcollection_semanticscelcel_matchcel_querylinkscore_writelifecyclewatch | 2026-07-29 The claim uses the machine-readable v0.3 atomic profiles. |
| mdbase TypeScript | 0.3.0-rc.4 | core_readcollection_semanticscelcel_matchcel_querylinkscore_writelifecycleOptional: view_records | 2026-07-29 The claim uses the machine-readable v0.3 atomic profiles. |
| mdbase-runtime-rs Rust | 0.3.0-rc.1 | core_readcelevent_action_interop/0.1runtime/0.2 | 2026-07-29 Durable Runtime 0.2; interoperability 0.1. |
| mdbase-interop TypeScript | 0.1.0-rc.2 | event_action_interop/0.1 | Reference ephemeral bridge; roles: event_source, event_consumer, action_caller, action_provider, bridge. |
Fixture coverage status
An implementation claim and the shared suite's coverage status answer different questions. The claim says what an artifact asserts it passes. The coverage ledger says whether the specification's maintainers consider the shared fixture set complete for that profile.
| Profile | Shared fixture coverage |
|---|---|
core_read | Coverage complete |
collection_semantics | Coverage complete |
cel | Draft coverage |
cel_match | Draft coverage |
cel_query | Draft coverage |
links | Draft coverage |
core_write | Draft coverage |
lifecycle | Draft coverage |
event_action_interop/0.1 | Draft coverage |
runtime/0.2 | Draft coverage |
watch | Draft coverage |
Runtime 0.2 has separate evidence.
The mdbase-runtime-rs row claims runtime/0.2 for durable admission, exact bindings, recovery, and timers. The mdbase-rs row remains a collection-engine claim; installing the collection crate alone does not imply workflow execution.