The question and the oracle
++ Draft 2020-12 schemas define neutral fixtures, run requests, adapter + descriptions, transcripts, and evidence. Every expected transcript + lives beside its scenario. +
+Portable testbed 0.1
++ One neutral suite tests TypeScript, Rust, plugins, desktop services, + and future implementations through a process boundary. Products keep + their own architecture; users get comparable evidence. +
+ +The black-box boundary
++ Each scenario starts a fresh adapter process. Only stable facts cross + the boundary; generated IDs, database keys, and wall-clock timing stay + inside. +
+describe
+ run
+ + Draft 2020-12 schemas define neutral fixtures, run requests, adapter + descriptions, transcripts, and evidence. Every expected transcript + lives beside its scenario. +
++ An adapter drives public collection, bridge, provider, runtime, and + store boundaries. It reduces observations to stable facts; it does + not reimplement the feature. +
++ Passing proves behavior, not permission. A transcript cannot grant + access, register a provider, publish an event, or authorize a side + effect. +
+15 scenarios · 3 rings
++ Small scenarios isolate failures. Application scenarios then repeat + the critical paths with real product contracts and providers. +
+{ring.summary}
+{id}
+ {description}
+ Fresh process per scenario
++ The runner launches an executable directly—never through a shell—and + validates both sides of every exchange before comparing observations. +
++ A passing run can emit a machine-readable evidence document containing + the implementation identity, scenario IDs, profile names, and canonical + transcript digests. Attach it to a conformance claim to make the tested + behavior reproducible. +
++ A complete profile claim still runs every normative conformance test + for that profile. The testbed adds cross-language behavioral evidence; + it does not silently widen the claim. +
+