Customer Task Catalog

A buyer-facing map from real-world problem shapes to QPC run families: what stays the same (engineering stack), what changes per domain (encoding only), what you supply, what you receive, and what stays outside the public boundary so core IP remains protected.

Evaluation & diligence Same stack · many domains No core exposure

What “the same stack” means

Not one formula for every industry — one repeatable quantum–classical pattern you operationalise across tasks.

Domain data (entities, tiers, weights, scenarios) → Structured graph / rolesPolycontextural pre-layers (context blocks) → Variational or sampling core (domain Hamiltonian) → Hardware shotsClassical metrics (thresholds, indices, rankings, JSON)

Per domain you change: node semantics, coupling rules, context labels, and how metrics are explained. Buyers do not need Qiskit access or IBM tokens for public diligence — published reports carry auditable job IDs; hands-on evaluation uses the bounded showcase JSON only.

Security boundary (what buyers never need)

The catalog is designed so procurement and integration can proceed without access to proprietary synthesis.

Task catalog (public reports)

Each row maps a problem shape to a published QPC report. Circuit synthesis and operator commands stay under NDA.

Domain Problem shape QPC run family Public report Typical inputs → outputs
ESG / mobility / insurance (Heron) Multi-objective industry tasks; parallel contextures in one IBM submission Polycontextural industry pilots (Lane B) + architecture ICC (Lane A) Heron trilogy · Cerrado · Traffic · Allstate Domain instance → declared decoder headline + auditable IBM job IDs (industry); raw ICC witnesses (architecture)
Architecture proof (IBM) Is coupled quantum structure falsifiable vs separable multi-job merge? Separability ICC · Joint Structure Challenge · MCGS Architecture program · JSC · MCGS Coupled vs control arms → raw ICC gap, pre-registered pass criteria, job IDs
Finance / systemic risk Network of institutions; cascade or phase-transition narrative Multi-context + Ising / QAOA stress on graph Crash report Graph / weights → stress indices, ranked nodes, phase-style readouts
Portfolio / insurance Many assets, constraints, multi-objective framing Multi-context optimisation encoding Harel summary · Allstate pilot · Heron trilogy Asset set + rules → allocation-style quantum workflow outputs (per your published case)
HPC / cyber resilience Infrastructure nodes, tiers, lateral movement & storage contexts QPC-HTD-20Q (full-chip Garnet class) IQM HTD page Fixed 20-node map → θ, P(H≥θ), R, top dangerous nodes, JSON + job id
Climate / policy (CO₂) Multi-regime, multi-stakeholder constraints; QUBO / QAOA narrative Parallel / multi-contexture CO₂ architecture runs CO₂ results Scenario tags + architecture params → comparative quantum metrics across context counts
Supply chain / operations Discrete choices, couplings, capacity-style constraints QAOA on structured operational graph (IBM-scale demo) Highlights (supply chain) Chain encoding → sampled configurations and scored objectives (per script design)
Geopolitical / crisis scenarios Scenario lists, ranked outcomes after quantum pass Data-driven scenario quantum ranking Crisis final report Scenario payloads → ordered results, executive report linkage
Strategy / multi-option Discrete strategic options; synergies and conflicts as edges Same family as supply / portfolio: decision qubits + interaction Hamiltonian Custom briefings under NDA Option set + pairwise J → high-coherence combinations and indices (template)
Weather & forecast analytics Discrete regime bins, ensemble branches, or risk couplings — not replacing NWP PDEs Small Ising / sampling on user-defined discrete states No single named script yet — roadmap row; encode regimes like CO₂ / strategy rows Regime graph + weights → joint high-risk patterns in label space (supporting analytics only)
Relational structure in → out Graph → circuit → decode to relation RICT encode–decode RICT report Graph spec → measurements → reconstructed structure (F1-style metrics in report)
Multi-context depth (IBM) Many formal contexts in one hardware run PFQM family PFQM Context count + params → breadth demonstration on named backends
Platform compatibility Same portable job shape on vendor cloud Hardware smoke & full-width checks Pasqal, Origin, Azure, IQM QPC operator runs on vendor backends → JSON metrics, job IDs, uniqueness / depth stats (see published vendor pages; not a customer self-service path)

For partner evaluation, contact readytogo@quantumpolycontextural.ai. Circuit synthesis stays under NDA.

Try QPC hands-on (one public path)

The catalog maps domains to published evidence. For a single bounded evaluation run with your own parameter choices, use the showcase — not self-service scripts or SDK.

Optimization showcase

Configure 3 contextures and 8 parameters → download JSON → email QPC → receive one IBM Heron job ID and result summary (async, evaluation only).

Open optimization showcase →

How buyers use this for evaluation

  1. Pick the row closest to their problem shape (or combine two rows, e.g. strategy + risk).
  2. Read the linked public report and architecture program for auditable job IDs.
  3. Optional hands-on: submit a showcase JSON request (bounded 3-contexture run — not a full industry port).
  4. For custom domain work or PoC: contact QPC under NDA; circuit synthesis stays out of scope for first diligence if desired.

Honest limits (builds trust)