AGmind Request a scope

Commercial

Qualification services

Each engagement answers one specific decision about an exact system under a frozen workload. You pay for a controlled process with pre-agreed pass conditions — not for a positive result.

What decision you are buying

A qualification engagement starts from the decision it must support: publish a claim, commit to a capacity envelope, buy hardware, ship a release, deploy offline. Scope, workload, versions and pass conditions are fixed before the first run, so the result is an evidence-backed answer to that decision — whichever way it goes.

Negative results are first-class deliverables. A verdict that a claim does not reproduce, or that a system fails its SLO at the intended load, is delivered with the same rigor as a pass: localized cause, reproduction recipe, and safe wording for what the system actually does. The fee is the same in both cases.

Services

Engagement modes

Every engagement runs in exactly one mode, agreed before the test plan is written. The mode determines who controls the conclusions and how the result may be presented. Funding is disclosed in every public report regardless of mode.

Independent commissioned test

The client funds the test; AGmind owns methodology, execution and conclusions.

  • Does: pre-registered test plan, frozen versions, verdict with limitations.
  • Does: disclose funding in any public report.
  • Does not: allow the client to edit conclusions or methodology.
  • Does not: include debugging or tuning of the system under test.

Commissioned engineering

AGmind works toward the client's goal: bring-up, patches, build recipes, tuning.

  • Does: deliver working recipes with before/after evidence.
  • Does: label every output as commissioned engineering.
  • Does not: produce an independent verdict about the same system.
  • Does not: get mixed with independent test results in one report.

Reference configuration

planned

A maintained, versioned stack release for an exact SKU, with an acceptance suite and a revalidation policy.

  • Does: separate validation cells from enablement work in the release notes.
  • Does: disclose the commercial relationship wherever results appear.
  • Does not: exist as a ready product — it is demand-gated (see below).
  • Does not: turn engineering output into an independence claim.

Process

  1. Step 1

    Scope call

    We establish the decision behind the engagement, the exact claim or workload, who owns the budget and the technical review, which versions are already frozen, and where the hardware is. If the decision itself is not yet clear, discovery comes before a statement of work.

  2. Step 2

    Test plan approval

    A pre-registered test plan fixes pass conditions, workload revision, SLO and quality floor before any run. The first part of the fee is tied to test-plan approval and reservation of the lab window.

  3. Step 3

    Frozen cells

    Scope is expressed in qualification cells: system revision × runtime revision × model artifact × workload revision × operating setting. Any material change after the freeze — another BIOS, driver, container digest, model file, context bucket or backend — is a change request, never a silent update.

  4. Step 4

    Execution

    Runs follow the approved plan. Failures, timeouts and errors stay in the record; repeats and endurance runs happen where the plan calls for them. Timelines pause when access, hardware or artifacts are blocked on the client side.

  5. Step 5

    Factual review round

    The client receives the draft and can correct factual errors — a wrong version string, a mislabeled artifact. The client cannot edit conclusions, verdicts or methodology. One factual review round is included in scope.

  6. Step 6

    Delivery

    The agreed deliverables are handed over: manifests, raw and derived data, verdict, limitations, reproduction recipe. The second part of the fee is tied to delivery. The fee never depends on the verdict.

Exclusions

  • No 24/7 operations or incident SLA. Qualification is a bounded engagement, not an operations contract.
  • No penetration testing. Security testing outside the agreed technical controls is out of scope.
  • No certification. AGmind never presents results in certification wording. Deliverables are evidence bundles with explicit scope and limitations.
  • No hosting of client inference. AGmind qualifies systems; it does not operate them in production for clients.
  • No compliance opinions. Air-gapped readiness checks cover technical controls only; a report is never a legal compliance statement.
  • No pay-for-positive. An engagement that requires a guaranteed favorable verdict is declined before it starts.

Disclosure options

Public

The client keeps the full private evidence bundle; AGmind publishes a redacted report with a funding disclosure. This is the baseline option and the one that builds the public research record.

Embargoed

The client holds the private bundle until an agreed date; publication follows after it. Useful around launches and procurement deadlines.

Private

Only the client receives the results; AGmind may state that the work happened only if permitted. Private-only work is priced above public work because it creates no public research asset — the difference is stated in the proposal.

Demand-gated future products

These offerings are built only when paid demand proves the need. They are listed here so the gate is public — they are not ready products and are not sold today.

Pricing

Pricing is scoped per engagement from the frozen cell count, the required repeats and endurance runs, and the chosen disclosure option. It is shared in the proposal, together with the payment split and the change-request terms. Shipping, insurance, customs, commercial licenses and cloud costs are billed separately at cost.

Start a scope conversation

Bring the decision you need to make, the exact claim or workload, and where the hardware lives. If versions are not frozen yet, that is fine — freezing them is the first step of the engagement.

Request scope Read the methodology