QAISS is building a neutral quantum-AI coordination layer. Follow the public roadmap and verify every claim.

Community

Contribute code, data & research.

The goal is a community that builds evidence — not one that only amplifies posts.

Official channels

Verified links only

Channels appear here only after the project owner confirms them. Treat any other account claiming to be QAISS with suspicion.

X / Twitter

Not yet published

Telegram

Not yet published

Discord

Not yet published

GitHub

Not yet published

Email

Not yet published

Documentation

OfficialOpen

Contributor pathways

Ways to help

Become a developer contributor

Adapters, schema work, simulators, tests. Accepted contributions and evaluation criteria will be published.

Planned

Monthly benchmark challenges

Reproduce, extend, or refute published benchmarks using the open protocol.

Planned

Educational content

Explainers, notebooks, and translations for the Learning Hub.

Planned

Research grants

Small grants for useful adapters and open research. Rules and outcomes published in full.

Planned

Contribute today

Five things you can do now

  1. Most wanted

    Run the GPU parity test

    Have an NVIDIA GPU on Linux? Install the connector’s GPU extra and run python -m unittest discover -s tests. A pass turns cuStateVec from “untested” into “verified” — with your device recorded.

    GPU path
  2. Code

    Add a gate

    Extend the gate grammar (e.g. S, T, SWAP) in both src/scripts/qsim.ts and the Python connector, add fixtures, and keep browser ↔ Python parity exact.

    Adapter spec
  3. Data

    Benchmark your device

    Run the protocol on a phone, laptop or workstation and share the downloaded record so devices can be compared with matching metadata.

    Benchmark Lab
  4. Education

    Improve the Learning Hub

    Propose a clearer definition, a missing term or a translation. Every definition must stay honest about open questions.

    Learning Hub
  5. Review

    Challenge a claim

    Every important statement on this site is in the claim ledger with its source. If one is wrong or stale, tell us — corrections are logged publicly.

    Claim ledger

Contribution rules

  • npm run check and the Python parity tests must pass.
  • No new claim without a source and an entry in the claim ledger.
  • Status changes (planned → prototype → live) need public evidence and a changelog entry.
  • No third-party logos, screenshots or partnership language without written permission.

Community votes and signals are not legal governance until a governance model is defined, written down, and reviewed.

Release notes

Engineering updates,
not hype.

Research drafts, releases, and every change to a public claim. No price talk.

Subscriptions open once the project publishes its privacy policy and mailing endpoint.