Explore in browser
The standalone WASM route is fully local: it reads an immutable Q42 demonstration volume and evaluates supported logic/query operations.
Start with no install: this page loads a committed Q42 volume and runs a real query engine in your browser's WASM sandbox. Native persistence is an optional, explicit next step—not a prerequisite for exploring the system.
This fetches the committed Schema.org Q42 volume, flattens its real Quin records, and calls the browser WASM query engine. It does not contact a daemon and does not send data off this page.
Runs the shipped query kernel locally after the Q42 volume has loaded.
Choose “Load Q42 + run in WASM” to begin. The first run downloads the demonstration data volume.
The standalone WASM route is fully local: it reads an immutable Q42 demonstration volume and evaluates supported logic/query operations.
Later, the CLI streams your own RDF into Q42 with an optional durable job. That native step creates a local artifact; it is not required for the demo above.
A paired native daemon is only for persistent graph and model operations. The browser reports that need rather than simulating it.
The local CLI makes progress observable and gives long imports a restartable identity. This is how a local dataset becomes a persistent artifact; the browser demo above deliberately does not pretend it has written to your machine.
> qualia-cli import ./data/clinic.n3 ./data/clinic.q42 --job-dir ./jobs/clinic --progress json
{"event":"source_detected","format":"n3"}
{"event":"checkpoint_written"}
{"event":"complete","output":"./data/clinic.q42"}
> qualia-cli ingest-job status ./jobs/clinic
> qualia-cli q42 verify ./data/clinic.q42 --level full
> qualia-cli verify-graph --input ./data/clinic.n3 --dataset ./data/clinic.q42 --memory-mib 32 --temp-gib 24
The output above illustrates the command sequence and event shape; use the CLI's emitted values as the authoritative result for your dataset.
Vibe makes the difference between a standalone value calculation and a persistent graph operation visible in the program's host capability. A Vibe workspace targeted at standalone WASM flags native-only operations before it runs them.
// Pure, exact in standalone WASM
using Math;
pure fn dosage_window(weight: f64) -> f64 {
return Math.min(weight * 2.0, 100.0);
}
// Persistent graph operation: requires a paired native daemon
using GraphDatabase;
fn find_protocols() -> Record {
return GraphDatabase.sparql("SELECT ?protocol WHERE { ?protocol a <https://example.org/Protocol> . }");
}
// wasm-standalone diagnostic: QDB0402 — GraphDatabase.sparql requires QualiaDB native engine
Pure math, RDF construction, and declared local operations run in the loaded module.
Graph reads and writes refer to an isolated browser snapshot—not a persistent native transaction.
SPARQL and model operations need a paired local daemon. Without one they are unavailable, not silently approximated.
This probe runs only after you choose it. It asks a development daemon for its public capability negotiation document; it never sends a token or a graph update.
A production daemon requires its local pairing token. Browser host invocation remains asynchronous by design; this probe demonstrates negotiation, not a shortcut around that boundary.
RDF and mapped-data import reference · live Q42 SPARQL showcase · browser scientific surface · Vibe-host bridge contract