Community Deployment Lead — competency requirements
NGARi Corps Workforce Competency Framework v1.0 (2026-10-02)

Owns a place rather than a box: several sites in one region, the relationships, and the reporting a funder or a local government needs.

A candidate meets this role when they hold the following levels against the framework. Every level is backed by evidence in the candidate's own record:

  C-HW-1   Appliance ownership and provisioning — Practitioner
           Own, flash, configure and place a NGARi appliance, and hand it over to someone who will use it without you.
  C-SOV-1  Sovereign AI foundations — Practitioner
           Explain where the model runs, where the data goes and who can switch it off — and tell an air-gapped node apart from a dedicated tenant.
  C-CLI-1  The data-privacy conversation — Practitioner
           Answer "we can't put our data in the cloud" with a demonstration instead of a promise — and know which three claims you must never make.
  C-COM-1  Scope, price and support a deployment — Practitioner
           Scope a small on-premises deployment, price it against the published ladder, and write down what maintenance includes.
  C-OPS-1  Node operations — Practitioner
           Load a model on your own node, run a metered call, and read the audit entry it wrote.

Evidence the framework accepts, per level: a timestamped attestation in the candidate's NGARi Corps record, a metered inference call on their own tenant, a paid appliance, or a NGARi-issued credential. Self-declared only, up to Practitioner; Verified requires a NGARi-issued credential.

Day to day:
  - Run several sites in one region and keep them all reachable.
  - Translate site problems into a maintenance and replacement plan.
  - Report measured usage and outcomes to a funder, from the record.
  - Train the next maintainer for the region.

Framework and candidate verification: https://ngari.ai/corps/competencies
Machine-readable: https://ngari.ai/api/corps/competencies