Technical demo
A demo is a scoped evaluation walkthrough, not an open sandbox.
The demo path shows how HX-SDP maps a real stack to the structural data plane, which proof packet applies, and what must be true before private deployment.
Walkthrough agenda
What the technical demo covers.
| Step | Content |
|---|---|
| 1. Current stack map | Cache, vector DB, feature store, search, event/retention, gateway, observability |
| 2. Corpus profile | N, D, model/corpus, query distribution, recall tolerance, rebuild cadence |
| 3. Tier recommendation | fp32/fp64 exact, fp16 scale envelope, or Atlas-first calibration |
| 4. Proof review | Receipt preview, methodology, manifest, verifier, limitations |
| 5. Pilot boundary | GPU node, hx-gate, hx-engine, Redis, security ownership, data handling |
Sample flow
The five-verb surface stays simple; the diligence around it is precise.
evaluation sketch
hx.put(namespace, vectors, metadata)
hx.search(namespace, query, filters)
hx.query(namespace, query_vector, top_k=10)
hx.serve(namespace, key, target="gpu")
hx.verify(receipt, manifest, signature)Prerequisites
Bring enough context to avoid a generic demo.
The useful inputs are current vendors, vector count, embedding dimension, model/corpus class, target recall, concurrency needs, rebuild cadence, data-handling constraints, and whether the buyer needs proof-pack or security review first.