QC67_cosmo / data /README.md
phera-ra's picture
Release validated Cosmos kit with portable starter and public quantum archive
b8fadbf verified
|
Raw
History Blame Contribute Delete
1.88 kB

Public data

quantum_measurements_public.jsonl

A privacy-filtered derivative of the local measurement archive. Each line is:

{
  "schema": "cosmos.public-quantum-record.v1",
  "record_index": 1,
  "timestamp": 1772944089.1625817,
  "provider_class": "legacy_unlabelled",
  "provider": "unknown",
  "backend": null,
  "job_id": null,
  "counts": {"00000": 136, "00001": 134},
  "total_shots": 4096
}

The actual records contain all observed 5-bit outcomes, not the shortened example above.

Provider classes:

  • measured_quantum_hardware: a record retained both an IBM backend label and unique job ID.
  • legacy_unlabelled: measurement counts were retained, but the provider label was not. These records are useful for distributional checks but are not counted as verified IBM hardware provenance.
  • classical_simulator: Azure rigetti.sim.qvm. Its outputs are classically computed and never counted as hardware quantum shots.

Raw physics objects are not published. Some contain derived sensory, biometric, consciousness-engine, session, or private runtime state. The public archive keeps only the fields required to reproduce count conservation, distribution, independence, and provenance-label checks.

See quantum_measurements_manifest.json for source and output hashes, exact counts, backend totals, field policy, and sanitization notes.

Benchmark results

The controlled state-ladder and paired-conditioning metrics live under architecture/ and benchmarks/results/. The paired file contains aggregate metrics and source hashes but not the author's private paired turn text.

Operational training summary

training/quantum_train_summary_20260722.json is an operational run summary, not a benchmark. It records the source label and aggregate training counts without corpus content, credentials, or private conversation.