Submissions Registry Reference
Registry Overview
The Quantum Advantage Tracker (QAT) maintains a unified registry of experimental results, categorized into three distinct pathways. Each submission is recorded as a structured entry within the project's data repository, allowing for programmatic comparison and validation against established classical benchmarks.
The registry is hosted as a collection of JSON files within the /data directory of the repository:
data/observable-estimations/submissions.jsondata/variational-problems/submissions.jsondata/classically-verifiable-problems/submissions.json
Common Submission Schema
While each pathway has specific validation requirements, all submissions share a base schema to ensure consistency across the tracker.
Submission Object
| Field | Type | Description |
| :--- | :--- | :--- |
| id | string | A unique identifier for the submission. |
| createdAt | string | ISO 8601 timestamp of the submission (YYYY-MM-DD). |
| institutions | string | A comma-separated list of participating organizations. |
| author | string | The primary contact or lead researcher for the experiment. |
| instanceId | string | The ID of the specific circuit or Hamiltonian instance used. |
| results | object | Pathway-specific experimental data (e.g., expectation values, energy levels). |
| citation | string | (Optional) Link to a published paper, preprint (arXiv), or technical report. |
Circuit & Instance Metadata
Submissions are mapped to predefined problem instances. The registry tracks these via the following structure:
export type CircuitInstance = {
id: string; // Unique identifier (e.g., "heavy-hex-27q-d10")
path: string; // Relative path to the circuit file in the repo
qubits: number; // Number of qubits used in the instance
gates: number; // Total gate count (depth/complexity metric)
};
Pathway-Specific Requirements
The registry enforces different validation logic depending on the chosen pathway.
1. Observable Estimations
Focuses on the precision of quantum computations.
- Requirement: Must report expectation values for specific observables.
- Validation: Submissions must include mathematically grounded error bars. The tracker validates that the reported value falls within provable confidence intervals.
2. Variational Problems
Focuses on finding the ground state of Hamiltonians.
- Requirement: Must report an upper bound on ground-state energy.
- Validation: Verified entries must provide evidence that the ansatz and optimization routine respect the variational principle.
3. Classically Verifiable Problems
Focuses on problems where the solution can be checked efficiently by a classical computer.
- Requirement: Must score solutions against known "gold standard" answers or checkable witnesses.
- Validation: Success is measured by the accuracy of the quantum output compared to the verifiable classical result.
Data Locations
When contributing or consuming registry data, refer to the following directory structure:
data/
├── classically-verifiable-problems/
│ ├── circuit-models.json # Available problem specs
│ └── submissions.json # Verified results
├── observable-estimations/
│ ├── circuit-models.json # Available circuit specs
│ └── submissions.json # Verified results
└── variational-problems/
├── hamiltonians.json # Available Hamiltonians
└── submissions.json # Verified results
Contributing to the Registry
Submissions are not added via direct PRs to the JSON files. Instead, contributors follow a structured workflow:
- Select an Instance: Choose an existing circuit model or Hamiltonian from the
/datafolders. - Execute Experiment: Run the instance on quantum hardware or simulators.
- Submit via Issue Template: Use one of the specialized GitHub Issue Templates.
01-submission-path-observable-estimations.yml02-submission-path-variational-problems.yml03-submission-path-classically-verifiable-problems.yml
- Validation: Maintainers review the issue for scientific rigor. Once approved, the data is automatically or manually ingested into the relevant
submissions.jsonfile.