← Back to What we build
QURMMIUS INTELLIGENCE LAYER

A shared AI pilot layer for reviewable product workflows.

QI Pilot v1 · provider + local fallback

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.

Run a product skill

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.

Sign in to QI accountChecking your shared QI session…

Structured result

Local analysis ready

Routed skill—
Confidence—
Signal—
Recommended next action—
Privacy mode—
Inputs / sources—

Provider mode sends only this redacted pilot input through the protected gateway. Local fallback sends nothing.

QI pilot controls

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.

0 pilot runs · 0 provider tokens this month
Protected pilot acceptance

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.

Invite testers →Send feedback →
No protected checklist run yet.
Production readiness

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.

Read readiness details →Billing activation checklist →
No golden evaluation run yet.
LOCAL PILOT HISTORY

Every run leaves a small trail.

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.

Recent runs

  • No pilot runs saved yet.

How the layer works.

Every product gets a narrow skill, while Qurmmius provides the shared controls around it.

01 · INGEST

Receive

Adapters accept telemetry, redacted documents, images, maps, sensor batches, and route signals.

02 · ROUTE

Choose

A domain registry selects the right product adapter and the smallest model or local rule set that fits.

03 · REASON

Explain

The adapter returns a structured signal, confidence, source trail, and a bounded recommendation.

04 · VERIFY

Review

People approve consequential actions, while policy checks and an audit record stay attached.

PRODUCT ADAPTERS

Focused intelligence, shared guardrails.

Telemetry & coaching PilotApex Academia turns lap and setup signals into explainable review cues. No medical or racing-outcome guarantees.
Privacy & handoffs PilotContextKey Shield reviews origin, credential, schema, and least-privilege risks without reproducing secrets.
Evidence & schemas PilotClearGrant maps verified, self-reported, stale, and missing evidence to a reviewer-ready next step.
Maps, worlds & form StagedQurmmius Palimpsest × EraWeaver and Fluid Fluidity preserve provenance, uncertainty, and study context.
Signals & stewardship StagedEcoEcho, SkySprout, and GridPulse aggregate useful trends without exposing individual histories.
Schema validation StagedSchemaForge flags mismatches and possible trackers using synthetic or redacted payloads.
NEXT DEFINED MILESTONES

Build the layer in proof-sized steps.

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.

Milestone 1 · Live now

QI Pilot v1

The shared request path is working end to end.

  • Provider gateway with local fallback
  • Three named pilot adapters
  • Redaction, rate limit, request ID, usage metadata
  • Local redacted run history
Milestone 2 · Next

Trusted workspace

Make QI safe for a small invited team.

  • Real login and tenant isolation
  • Durable audit records and retention controls
  • Telemetry and evidence ingest connectors
  • 20–50 golden evaluations per pilot adapter
Milestone 3 · Planned

Measured platform

Operate QI as a paid, observable service.

  • Per-tenant usage metering and Stripe plans
  • Admin cost, latency, and quality dashboard
  • Approval workflow for consequential actions
  • Staged adapters and tool calls for the remaining products

Connector contracts, ready for implementation.

These narrow interfaces keep future integrations reviewable and prevent product pages from handling provider credentials.

Telemetry ingest/api/qi/ingest/telemetry · normalize laps and quality flags
Evidence ingest/api/qi/ingest/evidence · preserve dates and provenance
Source search/api/qi/search/sources · return citations and uncertainty
Action verification/api/qi/verify/action · require approver and audit ID

Read the aggregate-data provider selection and activation contract →

QI AI-layer plans.

Live catalog for invited workspaces. Checkout is available only after signed workspace access and explicit acknowledgement of the versioned terms and refund policy.

$49/moStarter · 1 product skill
$149/moStudio · 3 product skills
$399/moPlatform · up to 10 skills

Each paid plan is tied to a signed workspace, a versioned terms record, a Stripe webhook, durable audit, and human-reviewed entitlement changes.