Skip to content
GRUNUSS

Deployments

v1.0 · 2026

Operational sites
and platform
deployments.

A public register of where the Grunuss platform is in operation, the scope of each deployment, and the institutional terms under which it operates.

§ 01 / Premise

GS-2026 / SECT_01

Deployment is the field record of validated capability.

A platform claim is not closed until the platform operates somewhere. This register lists the sites at which Grunuss platform capabilities are deployed, the scope of each deployment, and the institutional terms under which it operates.

Deployments are not announced before they are operational. Announcements of intent are not deployments and do not appear on this register. The discipline is the same as for research outputs: observed before stated.

§ 02 / Anchors

GS-2026 / SECT_02

Every deployment rests on two prerequisites.

A deployment exists only where both anchors are present. A platform capability without a constituted partnership is a demonstration, not a deployment. A partnership without a validated capability to deploy is a relationship, not a deployment.

A.01
Constituted partnership
The deployment operates under a partnership that has cleared the four-dimension alignment filter (see Partnerships, § 02). Without an active governing partnership, deployment is not initiated.
A.02
Validated platform capability
The deployment carries a platform capability that has cleared institutional validation (see Technical Architecture). Speculative or pre-validation capabilities are not field-deployed.

§ 03 / Categories

GS-2026 / SECT_03

Three categories of deployment.

D.01

Research deployment

Platform capability deployed within an academic or research-institute environment as part of an active collaboration. Outputs are scientific: published methods, validated material predictions, instrument-paired measurement campaigns.

D.02

Pilot deployment

Platform capability deployed under industrial conditions as a bounded pilot. Outputs are operational: process parameter sets, manufacturability envelopes, in-process metrology records. Pilot deployments are time-bounded and scope-defined.

D.03

Operational deployment

Platform capability embedded into a partner's ongoing operations under institutional terms. Outputs are continuous: production runs, deployed materials, observed-versus-predicted closure across operating cycles.

§ 04 / Lifecycle

GS-2026 / SECT_04

From request to closure.

Every deployment progresses through four discrete stages. Each stage must close before the next is authorised — the same discipline that governs research and partnerships applies here.

  1. L.01 · Stage 01

    Request

    Initial inquiry, scope definition, and identification of the governing partnership under which the deployment will operate. No commitment is made at this stage.

  2. L.02 · Stage 02

    Qualification

    Evaluation of site readiness, methodological requirements, and institutional terms. Includes alignment review against the partnership filter and deployment-specific risk assessment.

  3. L.03 · Stage 03

    Operation

    The deployment is active. Operating terms apply continuously. Metrology and observed-versus-predicted closure are maintained throughout.

  4. L.04 · Stage 04

    Closure

    Formal end of the deployment. Documented through final qualification report, public record entry, and exit data handover under predetermined terms.

§ 05 / Terms

GS-2026 / SECT_05

How deployments are governed.

Every deployment operates under the same institutional terms, regardless of category. The terms protect institutional discipline at sites the institution does not directly control.

OT.01
Methodological integrity
Deployed simulations and predictions retain their parameter traces, model versions, and uncertainty bounds. Field use does not strip these.
OT.02
Observed-versus-predicted closure
Every deployment is configured to produce measurement against prior predictions. Deviations are recorded with the result, not discarded.
OT.03
Communication discipline
Joint announcements follow the institutional communication framework. Partner-side marketing language is not appended to Grunuss-side statements about deployment performance.
OT.04
Data governance
Data generated within a deployment is governed by terms established before deployment begins, with clear delineation of ownership, retention, and downstream use.
OT.05
Reversibility
Pilot deployments are configured for graceful termination at the end of their bounded scope. Operational deployments carry exit terms documented at agreement signing.

§ 06 / Disclosure

GS-2026 / SECT_06

What is published about each deployment.

Disclosure is the credibility surface of this register. Six commitments govern what is published, when it is published, and how it is preserved.

DS.01
Operational status is published
Every active deployment appears in the register with its current operational status. Status changes are reflected promptly.
DS.02
Qualification reports are published at closure
Each deployment closes with a documented qualification report — observed performance against predictions, deviations encountered, institutional learning. The report becomes part of the public record.
DS.03
Deviations are documented, not concealed
Where field results diverge from prior predictions, the deviation is recorded with the entry. Observed-versus-predicted closure includes the cases where closure was not achieved.
DS.04
Partner sites are named unless cause for withholding is documented
Partner identities are disclosed by default. Where a partner requires confidentiality, the deployment is registered with the reason category for withholding stated.
DS.05
Closure is noted in Insights when material
Closures of material institutional significance are reflected on the Insights page. Quiet termination is not used.
DS.06
Historical entries are preserved without revision
Once published, an entry remains visible indefinitely. Amendments append; the original record is never silently rewritten.

§ 07 / Register

GS-2026 / SECT_07

Register of deployments.

Each deployment carries a four-character code, a host site (institution or geography), a category (D.01–D.03), and an operational status. Entries are added by date of operational commencement, never by date of announcement.

Register of Grunuss platform deployments.
CodeSiteCategoryStatus
[The register opens with the first deployment. The schema above is stable; entries are added in operational order.]