Receive
Adapters accept telemetry, redacted documents, images, maps, sensor batches, and route signals.
A limited, evolving layer for structured inputs and reviewable outputs. Product adapters have different stages, data paths, and safeguards; this page does not imply that every product is active or protected.
The QI pilot demonstrates a bounded flow: accept a structured input, route it to an available product adapter, return an explainable result, and leave consequential actions in human hands. Provider access depends on configuration and per-run consent.
QI uses a protected server route when configured. Provider requests are redacted, rate-limited, correlated with a request ID, and kept out of browser logs. Current-service questions receive a read-only health check; private Gmail, Stripe, filing, and account data still require their own approved connector.
Local analysis ready
Provider mode sends only this redacted pilot input through the protected gateway. Local fallback sends nothing.
Active: server-side key handling · secret-pattern redaction · origin allowlist · request IDs · bounded recommendations · human-review flag · in-memory rate limit · consent and dry-run safeguards.
Run the active lanes with synthetic metadata only. No files, credentials, telemetry, or personal data are sent. DeepFake Shield is local-preview only; LegacyVault is dry-run only with two-person approval and signed metadata receipts.
Some controls are implemented in the limited QI pilot path. Trusted workspaces with validated tenant isolation, durable audit and retention, product connectors, and deterministic golden evaluations remain release gates as listed below. These status statements are not an independent security review or certification. Paid access is not generally available; confirm the signed scope and account status for any invited workspace.
QI keeps a redacted preview, result signal, confidence, adapter, and request ID in this browser for up to 30 days. Raw pilot input is not kept in local run history. Cloud workspace memory is a separate, unchecked opt-in.
Every product gets a narrow skill, while Qurmmius provides the shared controls around it.
Adapters accept telemetry, redacted documents, images, maps, sensor batches, and route signals.
A domain registry selects the right product adapter and the smallest model or local rule set that fits.
The adapter returns a structured signal, confidence, source trail, and a bounded recommendation.
People approve consequential actions, while policy checks and an audit record stay attached.
Each milestone turns one part of the pilot into a reviewable production capability. The next gate is secure access and durable audit history—not more surface area.
The shared request path is working end to end.
Make QI safe for a small invited team.
Operate QI as a paid, observable service.
These narrow interfaces keep future integrations reviewable and prevent product pages from handling provider credentials.
Read the aggregate-data provider selection and activation contract →
Live catalog for invited workspaces. Checkout is available only after signed workspace access and explicit acknowledgement of the versioned terms and refund policy.
Each paid plan is tied to a signed workspace, a versioned terms record, a Stripe webhook, durable audit, and human-reviewed entitlement changes.