Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 17 Packages Wiki Activity Actions 234
open-standards/wai/wai-quantum-cli/skills/wai-quantum/reference/install.md
Transaction Science 6ea7825ce4 wai-quantum: every MCP tool says what it answers, both servers and the command line report their versions, and the provider protocol has its schema 
- Both MCP servers: each tool carries its answer's schema as its
  outputSchema, standing alone (every reference resolved); the command
  line's own tools' answers in wai-quantum-cli/schemas/local-tools.v1.json,
  the job service's in wai-quantum-service/schemas/service-tools.v1.json, the
  rest the engine's. A test calls every tool and holds its answer to its
  outputSchema with no member the schema does not name; a tool with no
  outputSchema, or not called there, fails it.
- The local server's tool list is committed (docs/local-mcp.json) beside the
  service's (docs/service-mcp.json), both held to the live lists.
- initialize gives the versions under _meta["science.transaction.wai/versions"]
  (wai.quantum.versions/1): the engine's and the server's, every schema it
  writes, the protocols it speaks, and where the policy is. The job service
  also gives them in quantum_service_info and GET /v1.
- wai-quantum version [--json]: the same, from the command line.
- wai-quantum-qpu/schemas/provider.v1.json: the open provider protocol's
  messages, answers, program and errors; every message the client sends and
  every answer the reference provider gives, in each basis, held to it.
- The job service's job in each status held to the job schema; the energy
  figure as the worker's reading gives it held to the result's.
- The agent docs (llms.txt, llms-full.txt, the AGENTS.md block, the Agent
  Skill) say how to read the versions and where the policy and the
  deprecations are; regenerated. The smoke checks check the versions.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-27 23:44:27 -04:00

1.6 KiB
Raw Permalink Blame History

Installing wai-quantum

Where How
Any platform with Rust cargo install wai-quantum-cli (the binary is wai-quantum)
macOS or Linux, with Homebrew brew tap transaction-science/tap https://git.transaction.science/Transaction-Science/homebrew-tap, then brew install wai-quantum
Windows, with Scoop scoop bucket add transaction-science https://git.transaction.science/Transaction-Science/scoop-bucket, then scoop install wai-quantum
Anywhere a prebuilt archive from https://git.transaction.science/Transaction-Science/open-standards/releases, tagged wai-quantum-cli-v…, each with a .sha256 beside it

Then:

  • wai-quantum --version is the version installed, and wai-quantum version --json the engine's and each schema's beside it. Read them there, not from a page.
  • wai-quantum key prints the did:key of the key this user signs with. The key itself lives in $XDG_CONFIG_HOME/wai/quantum-key (or ~/.config/wai/quantum-key), made on first use and readable by its owner only. Never open it.
  • wai-quantum mcp config prints the local MCP server's entry. wai-quantum mcp install --file PATH merges it into the JSON configuration file an agent client reads. Give --command the full path of wai-quantum when the client does not search your PATH. A different entry under the same name is refused unless you pass --force.
  • wai-quantum setup-agent writes the instructions for coding agents into the project's AGENTS.md. --check exits 1 when the block is missing or out of date, for CI.
  • wai-quantum docs skill --out DIR writes this skill into DIR/wai-quantum/.