Customer Task Catalog

A buyer map from real-world problem shapes to QPC run families. One polycontextural stack. Domain encodings. Published reports with IBM and vendor job IDs. Circuit synthesis stays with QPC.

Evaluation and diligence Same stack · many domains Core IP protected

What “the same stack” means

One repeatable polycontextural pattern you operationalise across tasks: co-resident logics, one quantum job, rankings on raw counts.

Domain data (entities, tiers, weights, scenarios) → Structured graph / roles → Polycontextural pre-layers (context blocks) → Co-resident circuit (one job on the QPU) → Hardware shots → Rankings and metrics (thresholds, indices, JSON, job IDs)

Per domain you change: node semantics, coupling rules, context labels, and how metrics are explained. Public diligence uses published reports and auditable job IDs. Hands-on evaluation uses the bounded showcase JSON.

Published path and partner path

Procurement and integration proceed on published evidence. Circuit construction stays inside QPC.

Task catalog (public reports)

Each row maps a problem shape to a published QPC report. Current IBM Heron r2 desks sit first.

Domain Problem shape QPC run family Public report Typical inputs → outputs
Semiconductor lithography Six photomasks, six competing mask logics, one ranking Mask synthesis desk · 24 measured contextures · ibm_kingston Mask synthesis ICCAD-2013 panel → coupled ranking on raw counts (no-OPC 0.622, ILT 0.460) · job daas1burrl7c73860bd0
Pharma / ADMET Seventeen ADMET logics on one frozen lead panel ADMET Lead Desk · junction RYY · ibm_marrakesh ADMET desk · Pharma Atlas Frozen table → raw junction gap 0.185 · retention 0.749 · separable 0.184
Energy · pharma · credit · EO Multi-goal industry decisions: reliability/carbon/cost; efficacy/safety/population; profit/risk/fairness; cloud/priority/energy Real-world desks · one IBM job per desk Real-World Desks Open panels (eGRID, OpenFDA, German Credit, NASA POWER) → coupled rankings + public job IDs
Organizing / NVIDIA Three logics in one job vs a three-job hybrid path Organizing comparison · CUDA-Q on Kingston Desk 03 · CUDA-Q Same grid task → 3 jobs become 1 · 31 merge steps become 0 · job d9tp5ic98n5s7391u4m0
Architecture proof (IBM) Coupled job vs separable and intracontext controls ICC · Joint Structure Challenge · MCGS · PFQM Architecture · JSC · MCGS · PFQM Coupled vs control arms → raw ICC gaps, pre-registered pass criteria, job IDs
ESG / mobility / insurance (Heron) Multi-objective industry tasks; parallel contextures in one IBM submission Polycontextural industry pilots Heron trilogy · Cerrado · Traffic · Allstate Domain instance → decoder headline + auditable IBM job IDs
Finance / systemic risk Network of institutions; cascade and phase-transition readout Multi-context stress on graph Crash report Graph / weights → stress indices, ranked nodes, phase-style readouts
Portfolio / insurance Many assets, constraints, multi-objective framing Multi-context portfolio encoding · Classiq comparison QPC vs Classiq · Harel summary · Allstate pilot Asset set + rules → coupled score and ranking (Classiq: QPC 7.587 vs Classiq-cut 9.072)
HPC / cyber resilience Infrastructure nodes, tiers, lateral movement and storage contexts QPC-HTD-20Q (Garnet class) IQM HTD page · IBM + Aquila Fixed node map → θ, P(H≥θ), R, top dangerous nodes, JSON + job ID
Climate / policy (CO₂) Multi-regime, multi-stakeholder constraints Parallel / multi-contexture CO₂ architecture runs CO₂ results Scenario tags + architecture params → comparative quantum metrics across context counts
Supply chain / aerospace Discrete choices, couplings, capacity-style constraints, multi-OEM programs Structured operational graph on IBM Heron Supply chain · Aerospace pilot Chain encoding → sampled configurations, scored objectives, IBM job IDs
Geopolitical / crisis scenarios Scenario lists, ranked outcomes after the 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 Design Partner Option set + pairwise couplings → high-coherence combinations and indices
Relational structure in → out Graph → circuit → decode to relation RICT encode–decode RICT report Graph spec → measurements → reconstructed structure (F1-style metrics in report)
Platform compatibility Same portable job shape on vendor cloud Hardware smoke and full-width checks Pasqal, Origin, Azure, IQM QPC operator runs on vendor backends → JSON metrics, job IDs, uniqueness and depth stats

For partner evaluation, open the Design Partner page. Circuit synthesis stays with QPC under NDA.

Try QPC hands-on

The catalog maps domains to published evidence. For a run with your own parameter choices, use the showcase: 3 contextures, 8 parameters, one IBM Heron job.

Optimization showcase

Configure 3 contextures and 8 parameters, download JSON, email QPC, receive one IBM Heron job ID and a result summary.

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 for auditable job IDs.
  3. Hands-on: submit a showcase JSON request (3-contexture IBM run).
  4. Custom domain work: Design Partner under NDA.

How QPC reports