Research · implementation

WDBX Specimen separates architecture, runtime profiles, and proof

WDBX Specimen combines a provenance-aware architecture specification with explicit browser and native runtime profiles, then uses conformance tests to make a bounded subset of the design executable.

AIWDBXSEAGPUMCPTUI

Specification with provenance

The architecture specification separates source-backed statements, recommended design choices, and open questions. It also maintains a contradiction register and contributor provenance so unresolved design tension remains visible instead of being flattened into one apparently settled narrative.

Acceptance cases are written as requirements for an implementation, not retroactive proof that every requirement is already satisfied. That distinction makes the document useful as both an architectural map and a research agenda.

Two honest runtime profiles

The browser profile emphasizes deterministic prompt features and seeded sampling without claiming online weight training or learned generation. The native profile documents an initial Rust implementation whose lexical processing and persistence behavior are narrower than unrestricted semantic intelligence.

Native conformance tests exercise the implemented profile. Together, the profiles show how one specification can support multiple runtimes while requiring each runtime to state exactly which semantics and proofs it provides.

Limitations

Source citations are withheld because the underlying repository is private and cannot be verified by public readers.
WDBX Specimen is an independent design-and-conformance project, not evidence for every capability of the canonical WDBX storage substrate.
Specification requirements, browser demonstrations, native conformance, performance measurements, and production readiness are separate evidence layers.

All implementations Abbey capability claims as an executable ledger Deterministic research exports with citation gates

Research index

AI overview

The track note this case sits under.