PAIG · Open Technical Committee (community) · Convened by Cognita GRC

We must now govern AI that can apply force.

When AI gets a body, a hallucination is no longer a wrong answer — it is a physical action. PAIG is an open, community technical committee drafting vendor-neutral standards for autonomous embodied AI: a Force Continuum, an "ISO 42001 for Robotics," and the API that makes them provable.

Draft v0.1 · Request for Comment Open standard · CC BY 4.0 / Apache-2.0
Committee scope

Standardization of the governance of autonomous embodied AI — humanoids, general-purpose mobile manipulators, and any AI system that can move and apply force among people: how much force such a system may be authorized to apply, how much human control that force requires, the management system and technical controls that make the coupling real, and the vendor-neutral interface that makes it enforceable and provable after the fact.

In scope
  • A graduated force-authorization scale (PAFC-0…5) coupled to human-control tiers (HC-0…3)
  • A management system + six technical controls for embodied AI ("ISO 42001 for Robotics")
  • A governance API: identity, attestation, force-level authorization, tamper-evident logs, accountability
  • Mappings to ISO 10218:2025, ISO 13482, IEC 61508 / ISO 13849, the EU Machinery Regulation 2023/1230, the EU AI Act, and ISO/IEC 42001
Out of scope
  • Replacing or reissuing existing physical-safety standards — PAIG complements and extends them
  • Certification or conformity marks — these are drafts for comment, not a certification scheme
  • Weapons development — autonomous lethal force is prohibited by the standard itself (PAFC-5 / rule R4)
  • Legal advice
Latest July 2026 — v0.1 working drafts published (PAIG-0…3) Open now — call for participants; the Force Continuum (PAIG-1) is the first RFC

The gap

Real, current standards cover parts of the problem — and stop exactly where autonomous humanoids begin.

ISO 10218:2025 · ISO 13482

Govern industrial, collaborative, and gentle service robots — force limits, safety-rated stops. They assume defined tasks, not open-world autonomy taking real-time commands.

EU Machinery Reg. 2023/1230 · EU AI Act

From 2027, add AI & self-evolving-behaviour review and human oversight. A conformity regime — not a graduated force-authorization scale.

What's missing

How much force a machine may apply and how much human control it requires — and a universal, provable way to answer, after an incident, what it was told, what it decided, and who was accountable.

Structure — working areas

Four working areas, structured like a technical committee. Each maintains a living draft in the document register; every convenor seat is open.

WG-1 · CORE
The Force Continuum (PAFC)
Scope: a graduated force-authorization scale — PAFC-0…5 (Presence → Lethal) — coupled to mandatory human-control tiers and enforced in the machine.
Deliverable:
RFC — open for commentConvenor: open
WG-2 · STANDARD
Embodied AI Governance ("ISO 42001 for Robotics")
Scope: a management system + six mandatory controls — hardware e-stop, certified force limits, verifiable audit logs, digital identity, continuous monitoring, human accountability.
Deliverable:
Working DraftConvenor: open
WG-3 · INTEROP
Physical AI Governance API
Scope: the vendor-neutral interface that makes the standards enforceable — identity & attestation, force-level authorization, tamper-evident logs + offline verification, monitoring, accountability.
Deliverable:
Working DraftConvenor: open
WG-0 · PROCESS
Working Group & Governance
Scope: who we convene, the rough-consensus decision model, the first-session agenda, and the v0.1 → v1.0 roadmap.
Deliverable:
FormingConvener: Cognita GRC (steward, not owner)

Document register

Deliverables under development. Every document is an open draft — versioned in the repository, free to read, comment on, and implement.

Doc IDTitleWorking areaStageVersionLink
PAIG-1Physical AI Force Continuum (PAFC)WG-1 · Core RFC — open for commentv0.1
PAIG-2Embodied AI Governance Standard ("ISO 42001 for Robotics")WG-2 · Standard Working Draftv0.1
PAIG-3Physical AI Governance APIWG-3 · Interop Working Draftv0.1
PAIG-0Working Group & GovernanceWG-0 · Process Formingv0.1
Working Draft — being written in the working area RFC / Enquiry — published for public comment (Issue open ≥ 2 weeks) Ratified — adopted by working-group consensus, versioned release

A plain-language analogue of the ISO stage ladder (WD → CD/DIS → IS). "Forming" marks a process document awaiting ratification at the first session. Nothing here is a published ISO standard or a certification — these are community drafts designed to complement ISO 10218:2025, ISO 13482, the EU Machinery Regulation 2023/1230, the EU AI Act, and ISO/IEC 42001.

Documents

The living drafts, in full. Comments and pull requests welcome via the repository.

Loading…

Participation & membership

An open committee: participation is free and the process is public. Cognita GRC is the steward, not the owner — the standard text is CC BY 4.0 and the API specification is Apache-2.0. We're forming the working group now to take v0.1 to a citable standard.

RoboticistsFunctional-safety engineersStandards bodies (ISO/TC 299, IEC)RegulatorsLaw-enforcement & public-safetyAI-governance leadersEthicistsInsurers & liability

First deliverable: ratify the Force Continuum v0.1 (PAIG-1) as an RFC. How to join: open a GitHub Issue titled “Join: [your role]” with one line on your background, or contact Cognita GRC.

Join on GitHub ↗ Repository ↗ app.cognitagrc.io

Process & meetings

How the committee decides — rough consensus, evidence over opinion, public-safety first. The full process document is PAIG-0, to be ratified at the first session.

Decision flow
Draft RFC (Issue open ≥ 2 weeks) Working-group review Merge on consensus Versioned release

Material safety decisions require sign-off from ≥ 2 functional-safety and ≥ 1 regulatory participant. Substantive changes arrive as pull requests with a linked Issue + rationale.

First session — proposed agenda
  1. Ratify scope + principles.
  2. Force Continuum v0.1 (PAIG-1) — adopt/refine the PAFC levels + Force–Control Coupling as the first RFC.
  3. Assign leads per document.
  4. Decide the conformance/attestation model (self vs. third-party) and the minimal audit-log schema.
  5. Set cadence + the v0.2 milestone.
v0.1 — now

Drafts published; call for participants.

v0.2

Force Continuum RFC ratified; minimal audit-log schema; reference OpenAPI spec.

v0.3

Pilot with ≥1 robotics vendor; map to EU MR 2023/1230 + EU AI Act.

v1.0

Citable standard + open reference implementation.