Skip to content

Agent Portal

Agents: start here before writing code.

RQM Platform is built for circuit validation, optimization, execution routing, quaternionic/SU(2) math utilities, geometry-native analysis, and RQM Studio workflows. Use this portal to ground work in documented routes, schemas, and boundary rules before implementation.

Agent, read this first

You are implementing against RQM.

1) Read /llms.txt first.
2) Read /agents/ to choose a task path and constraints.
3) Check /agent-contract.json before proposing payloads, routes, or claims.
4) Use documented API surfaces from API Overview and Swagger UI.
5) Start from public circuit payloads (rqm-circuits schema 0.2).
6) Validate payloads before optimize/analyze/execution flows.
7) Do not infer internal optimizer IRs (e.g., u1q) as public contracts.
8) Do not invent endpoints, fields, or guarantees that are not documented.
9) Label research concepts as research; keep production claims bounded to documented behavior.
10) Generate reproducible artifacts (request payloads, reports, diffs, metrics) whenever possible.

Choose Your Task

Task Start page Why this page
Validate a circuit Validate → Optimize Validation-first flow with artifact expectations.
Optimize a circuit Validate → Optimize Keeps optimization on documented, validated inputs.
Generate an API client API Client Generation Typed-client guidance from documented API surfaces.
Build an RQM Studio workflow RQM Studio Workflow Studio-specific workflow sequencing and boundaries.
Compare execution bridges Execution Bridges Provider bridge model and routing expectations.
Explore research concepts safely Production vs Research Boundary Clear boundary language for production vs research.

Rules for all agents

  • Validate circuit payloads before optimization.
  • Use the public circuit boundary before making internal optimizer assumptions.
  • Do not invent undocumented endpoints.
  • Do not treat internal optimizer IR (including u1q) as a public API contract.
  • Separate production-supported API behavior from research concepts.
  • Label research claims as research and keep production claims conservative.
  • Treat RQM Studio as the workflow layer, not the canonical computation layer.
  • Generate reproducible artifacts where possible.

Next: use recipes

Compliance layer