Tegrity.AITEGRITY.AI / INDUSTRY-REFERENCE-GROUP · v1.0


AI Integrity Management — Industry Reference Group

Sponsors, Patrons, Contributors & Members. A focused industry group for organisations building, operating and governing AI-enabled systems.

Document status

Participation programme · open

Convened by

Tegrity.AI
The Integral Management Society

Programme

AI Integrity Management

Date

Updated September 2026

The Integral Management Society (IMSV) is a Swiss non-profit association based in Geneva and the institutional home of Tegrity.AI. The Group’s specific focus is the structural management of AI integrity under real-world indeterminacy and finite resources: how to preserve trustworthy operation without assuming perfect knowledge or unlimited control.

Participation and support do not confer technical influence, certification or standards endorsement.

§ 01

What is distinctive about our approach

  • Structural indeterminacy — unknown, unresolved and out-of-frame conditions are treated as part of the architecture, not as exceptional failures.
  • Integrity through sufficiency and optimisation — integrity remains the objective; controls, oversight, evidence and resources are designed to achieve declared integrity objectives without maximalist overload that can itself undermine integrity.
  • Operational integrity — reliability, safety, security, ethics and compliance, continuity, human oversight and emergency response are treated as operating constraints of the same system, not as disconnected checklists.
  • Epistemic integrity — the system maintains a sound and explicit posture about what is known, uncertain, inherited or unresolved; explanation should reflect justified knowledge rather than provide explainability without epistemic substance.

§ 02

Why participate?

For technology and product companies

  • Product strategy — map the product against emerging integrity and control functions to decide what to build, expose, delegate or keep intentionally out of scope.
  • Standards intelligence & contribution — understand what international groups are actually discussing and, where there is substantive fit, contribute requirements, interfaces or implementation evidence while the work is still open.

For enterprise users and operators

  • Challenge-to-case — take a real operating challenge and map it against international research, pre-standardization work and comparable architectures.
  • Minimum Sufficient Control — rationalise observation, coordination, human intervention, evidence and controls toward the minimum apparatus sufficient to achieve the declared objective.

For standards and industry-affairs teams

  • Roadmap alignment & early visibility — map emerging pre-standardization work against the organisation’s own standards positions and technologies, and follow drafts, commits, cases and interfaces while they are still being shaped.
  • Contributor participation — bring requirements and implementation evidence into relevant open technical work and create a public contributor trace where the external process allows it.
International working session in Geneva.

§ 03

Examples of value delivery

  • Technical working sessions — turn one concrete challenge into a contribution-ready case, use case or technical object.
  • Product & architecture mapping — make covered, externally dependent, unresolved and out-of-scope functions explicit.
  • Challenge / case testing — use frozen cases to map and stress-test developing technologies against common technical questions.
  • Standards & research intelligence — focused interpretation of live technical work, not a generic standards newsletter.
  • Visibility — badges or recognition for real participation, contribution or support by sponsors, patrons, contributors and members; not product certification or standards endorsement.
  • Consortium opportunities — where there is technical fit, relevant contributors may join research, standards-facing or funded consortium initiatives.

§ 04

Architecture mapping, not certification

The Group does not score or certify products. Mapping is used to understand what an architecture already covers, what it delegates, what remains externally dependent and what remains unresolved or intentionally out of scope.

§ 05

Participation

Open to sponsors, patrons, contributors and members — including individuals, practitioners, companies and institutions of any size. Interaction normally starts with one architecture, use case, standards question or operational challenge. Support increases the Group’s research and coordination capacity while technical conclusions remain independent. The Group provides architecture mapping and contribution pathways; it does not certify or rank products.

Want to interact with us? Write to us.

Contact the Group