QODIQA Master Index
Reader's Guide

Deterministic Runtime Consent Enforcement for Artificial Intelligence Systems

April 2026

QODIQA-IDX-2026-001  ·  Version 1.0

Navigation reference, corpus hierarchy, reading paths by audience, and consolidated glossary for the standard corpus.

Scroll
Contents
Abstract

The QODIQA standard corpus comprises twenty-nine documents spanning five normative tiers. Each document addresses a defined aspect of deterministic runtime consent enforcement for artificial intelligence systems. The corpus is internally coherent and cross-referenced throughout, but it does not contain a navigational instrument that orients a new reader, defines the reading order appropriate to a given role, or provides a consolidated reference for terms used across documents.

This document, the Master Index and Reader's Guide, fills that structural gap. It provides a complete inventory of all corpus documents with their normative status and tier classification, four role-specific reading paths, a cross-reference map of document dependencies, and a consolidated glossary of all defined terms drawn from their authoritative definitions across the corpus.

#How to Use this Document

This document is a navigational instrument, not a normative specification. It does not introduce new requirements, does not modify any existing normative statement in the corpus, and does not supersede any document it references. Its sole function is to make the corpus accessible.

If you are reading the QODIQA corpus for the first time, begin with Section 4 (Reading Paths). Identify the path that corresponds to your role and follow it. Return to Section 3 (Complete Document Index) when you need to locate a specific document, and to Section 6 (Consolidated Glossary) when you encounter an undefined term.

Readers who are already familiar with the corpus and are seeking a specific document or term may proceed directly to Section 3 or Section 6 respectively.

#Purpose of this Document

A technical corpus of twenty-nine documents presents a navigational challenge that is distinct from the challenge of understanding any single document within it. Individual documents are self-contained. The corpus as a whole is not. Dependencies between documents are declared through cross-references but are not visualized. The normative hierarchy is implied by document type but is not summarized in any single location. Terms are defined where they first appear but are not consolidated. Reading paths appropriate to specific professional roles are not described.

These omissions do not impair the correctness of the corpus, but they impose a non-trivial orientation cost on any new reader. An implementation engineer who begins with the wrong document will acquire correct but poorly-sequenced knowledge. A regulator who encounters an undefined term must search across twenty-nine documents to locate its authoritative definition. An executive seeking a strategic overview has no indicated starting point.

Scope of this Document

This document provides: (i) a complete inventory of all corpus documents with normative tier and status classification; (ii) a visual hierarchy of document dependencies; (iii) four role-differentiated reading paths; (iv) a cross-reference map identifying which documents must be read before which; and (v) a consolidated glossary of all defined terms drawn from their authoritative source documents. It does not introduce any normative requirement and does not modify any existing document in the corpus.

This document is issued as a companion instrument to the corpus and should be made available wherever the corpus is distributed. It is classified as informative and carries document identifier QODIQA-IDX-2026-001.

#Corpus Overview

2.1 Corpus Statistics

The QODIQA standard corpus at Version 1.0 (April 2026) consists of twenty-nine documents. These documents are distributed across five normative tiers, from foundational conceptual documents through governance and legal instruments. The corpus is versioned as a unit under the QODIQA Governance Charter; individual documents carry their own version numbers but are released and amended as part of the corpus as a whole.

Table 1. Corpus composition by tier
TierClassificationDocument CountStatus
Tier IFoundational2Normative
Tier IINormative Technical8Normative
Tier IIIOperational7Normative
Tier IVGovernance and Legal5Normative
Tier VInformative7Informative

2.2 Normative Hierarchy

The corpus establishes a strict normative hierarchy. In the event of apparent conflict between documents, the following precedence order applies: Tier I documents take precedence over all others; within Tier II, the Core Standard (QODIQA-CORE-2026-001) takes precedence over all other Tier II documents; Tier IV governance documents take precedence over Tier III operational documents on matters of governance and process. Informative documents (Tier V) carry no normative force and cannot override any normative statement.

Conflict Resolution Precedence: Normative Order
1QODIQA Technical Whitepaper (QODIQA-WP-2026-001): conceptual foundation
2QODIQA Core Standard (QODIQA-CORE-2026-001): primary normative instrument
368-Point Enforcement Framework (QODIQA-68P-2026-001): detailed control specification
4Tier II technical specifications: architecture, security, conformance
5Tier III operational documents: implementation, deployment, failure handling
6Tier IV governance instruments: charter, license, change log
7Tier V informative documents: no normative force

#Complete Document Index

The following index lists all twenty-nine documents in the QODIQA corpus, organized by tier. Each entry includes the document identifier, full title, normative status, and a brief functional description. Documents are listed in the recommended reading order within each tier.

3.1 Tier I: Foundational Documents

Tier I documents establish the conceptual and definitional foundation of the QODIQA framework. All other corpus documents presuppose familiarity with these two documents. They should be read first by any reader approaching the corpus for the first time.

Tier I Foundational: read first
QODIQA-WP-2026-001
Consent as Infrastructure for Artificial Intelligence Technical Whitepaper
Normative
QODIQA-CORE-2026-001
Core Standard for Deterministic Runtime Consent Enforcement
Normative

3.2 Tier II: Normative Technical Specifications

Tier II documents specify the technical architecture, control framework, security profile, conformance requirements, and threat model of the QODIQA enforcement system. These documents expand the normative requirements established in the Core Standard into implementable technical detail. Readers undertaking implementation should read all Tier II documents after completing Tier I.

Tier II Normative Technical Specifications
QODIQA-68P-2026-001
68-Point Enforcement Framework for Deterministic Runtime Consent Enforcement
Normative
QODIQA-ARCH-2026-001
Reference Architecture for Deterministic Runtime Consent Enforcement
Normative
QODIQA-SEC-2026-001
Security and Cryptographic Profile for Runtime Consent Enforcement
Normative
QODIQA-CTS-2026-001
Conformance Test Suite Specification for Deterministic Runtime Consent Enforcement
Normative
QODIQA-CVS-2026-001
Conformance Verification Specification
Normative
QODIQA-TM-2026-001
Threat Model and Abuse Case Specification
Normative
QODIQA-ETM-2026-001
Extended Adversarial Threat Model
Normative
QODIQA-GEI-2026-001
Global Enforcement Invariants for Deterministic Runtime Consent Enforcement
Normative

3.3 Tier III: Operational Documents

Tier III documents provide the operational guidance required to implement, deploy, and maintain a QODIQA-conformant system. They address implementation patterns, failure handling, reference stack specification, system boundaries, deployment constraints, and non-compliance conditions. These documents are intended for engineering, operations, and assurance teams undertaking active implementation.

Tier III Operational: implementation and deployment guidance
QODIQA-IMPL-2026-001
Implementation Playbook for Deterministic Runtime Consent Enforcement
Normative
QODIQA-RIS-2026-001
Reference Implementation Specification - Minimal Deterministic Enforcement Stack
Normative
QODIQA-FHS-2026-001
Failure Handling and Recovery Specification
Normative
QODIQA-NCC-2026-001
Non-Compliance Conditions and Failure Modes
Normative
QODIQA-SBT-2026-001
System Boundary and Trust Model Specification
Normative
QODIQA-IDC-2026-001
Interoperability and Deployment Constraints
Normative
QODIQA-TERM-2026-001
Terminology and Normative Definitions
Normative

3.4 Tier IV: Governance and Legal Instruments

Tier IV documents establish the institutional governance of the corpus, define certification boundaries, specify the legal terms under which the corpus is distributed, and provide the residual risk disclosure required of all conformant implementations. These documents are primarily addressed to legal, compliance, and institutional governance functions, but all implementors are required to acknowledge the Residual Risk Annex as a condition of claiming conformance.

Tier IV Governance and Legal: institutional instruments
QODIQA-GC-2026-001
Governance Charter for the QODIQA Standard Corpus
Normative
QODIQA-CF-2026-001
Certification Framework for Deterministic Runtime Consent Enforcement
Normative
QODIQA-RISK-2026-001
Residual Risk and Assumption Disclosure Annex
Normative
QODIQA-PSL-2026-001
Public Specification License
Normative
QODIQA-POS-2026-001
Positioning and Scope Limitation Statement
Normative

3.5 Tier V: Informative Documents

Tier V documents provide contextual, analytical, and process support for the corpus. They do not introduce normative requirements and carry no binding force. They are intended to support evaluation, adoption, and stakeholder communication. Readers may engage with these documents selectively based on their role and purpose.

Tier V Informative: no normative force
QODIQA-EB-2026-001
Executive Brief for Deterministic Runtime Consent Enforcement
Informative
QODIQA-EIA-2026-001
Economic Impact Analysis of Deterministic Runtime Consent Enforcement
Informative
QODIQA-RAM-2026-001
Regulatory Alignment Matrix for Deterministic Runtime Consent Enforcement
Informative
QODIQA-AEM-2026-001
Audit and Evidence Generation Model
Informative
QODIQA-ARP-2026-001
Audit Readiness and Evidence Pack
Informative
QODIQA-UCD-2026-001
Use Case Dossiers for Runtime Consent Enforcement Deployments
Informative
QODIQA-CCL-2026-001
Corpus Change Log and Version History
Informative

#Reading Paths by Audience

The following four reading paths are designed for distinct professional roles. Each path identifies the minimum set of documents required to achieve functional understanding for that role, presented in the recommended reading order. Documents are listed by identifier; full titles are provided in Section 3.

These paths are not exhaustive. A reader who has completed a path for their primary role may benefit from reading additional documents outside that path, particularly from adjacent tiers. The paths are entry points, not boundaries.

Path A
Implementation Engineer

For engineers building a QODIQA-conformant enforcement layer. Prioritizes architectural specification, control requirements, cryptographic profile, failure behavior, and the reference implementation.

  1. 01QODIQA-WP-2026-001: conceptual foundations and the Authorization/Consent distinction
  2. 02QODIQA-CORE-2026-001: twelve control points, decision semantics, conformance profiles
  3. 03QODIQA-68P-2026-001: full control framework, governance domains, cryptographic layer
  4. 04QODIQA-ARCH-2026-001: reference architecture, component model, trust boundaries
  5. 05QODIQA-SEC-2026-001: cryptographic requirements, key management, signature verification
  6. 06QODIQA-GEI-2026-001: enforcement invariants that must hold across all deployments
  7. 07QODIQA-SBT-2026-001: system boundary definition and trust model
  8. 08QODIQA-IDC-2026-001: integration surfaces, anti-bypass controls, deployment constraints
  9. 09QODIQA-RIS-2026-001: minimal reference implementation specification
  10. 10QODIQA-IMPL-2026-001: 30/60-day integration playbook
  11. 11QODIQA-FHS-2026-001: failure handling, recovery, and fail-closed guarantees
  12. 12QODIQA-NCC-2026-001: non-compliance conditions and prohibited system behaviors
  13. 13QODIQA-TM-2026-001: threat model and bypass scenario analysis
  14. 14QODIQA-RISK-2026-001: residual risk disclosure, required acknowledgement
Path B
Compliance and Audit

For compliance officers, internal auditors, and assurance teams evaluating whether a QODIQA implementation meets conformance requirements and produces adequate evidence artifacts.

  1. 01QODIQA-WP-2026-001: conceptual model, consent gap analysis
  2. 02QODIQA-CORE-2026-001: conformance profiles (CORE-MIN / CORE-VER / CORE-ENT)
  3. 03QODIQA-CF-2026-001: certification framework, what certification validates and does not validate
  4. 04QODIQA-CTS-2026-001: conformance test suite, test matrix, evidence packaging requirements
  5. 05QODIQA-CVS-2026-001: conformance verification procedures
  6. 06QODIQA-NCC-2026-001: hard and soft non-compliance conditions, severity levels
  7. 07QODIQA-AEM-2026-001: audit and evidence generation model
  8. 08QODIQA-ARP-2026-001: audit readiness and evidence pack structure
  9. 09QODIQA-RISK-2026-001: residual risk register, assumption disclosures
  10. 10QODIQA-GC-2026-001: governance charter, amendment process, authority structure
Path C
Regulatory and Legal

For regulatory reviewers, legal counsel, and policy advisors evaluating the QODIQA framework against applicable legal and regulatory requirements, or assessing institutional liability exposure.

  1. 01QODIQA-POS-2026-001: scope limitation, explicit non-claims, what QODIQA does not provide
  2. 02QODIQA-WP-2026-001: conceptual foundations, consent gap analysis
  3. 03QODIQA-CORE-2026-001: normative requirements, conformance definition
  4. 04QODIQA-RAM-2026-001: GDPR, EU AI Act, NIST RMF, ISO 27001, ISO 42001 alignment matrix
  5. 05QODIQA-RISK-2026-001: residual risk disclosure, no-guarantee clause, non-coverage declarations
  6. 06QODIQA-PSL-2026-001: public specification license terms
  7. 07QODIQA-CF-2026-001: certification boundary, what certification does and does not establish
  8. 08QODIQA-GC-2026-001: governance authority, amendment procedure, corpus integrity
Path D
Executive and Strategic

For executives, board-level stakeholders, and strategic decision-makers evaluating QODIQA as an institutional infrastructure investment. Prioritizes problem framing, economic rationale, and strategic positioning.

  1. 01QODIQA-EB-2026-001: executive brief, strategic case, adoption rationale
  2. 02QODIQA-WP-2026-001: Section 1 (Executive Summary) and Section 3 (The Consent Gap)
  3. 03QODIQA-EIA-2026-001: economic impact analysis, risk surface quantification, scenario modeling
  4. 04QODIQA-POS-2026-001: scope limitations, non-claims, what QODIQA does not guarantee
  5. 05QODIQA-RAM-2026-001: regulatory alignment summary, compliance coverage density
  6. 06QODIQA-UCD-2026-001: use case dossiers for sector-specific deployment scenarios
  7. 07QODIQA-RISK-2026-001: Section 0 (Executive Disclosure), residual risk register summary

#Cross-Reference Map

The following table identifies the primary dependency relationships between documents in the corpus. Column "Requires" lists documents that must be read before the listed document can be fully understood. Column "Referenced by" identifies documents that cite the listed document as a normative or informative source. This map is not exhaustive of all cross-references in the corpus; it identifies structural dependencies only.

Table 2. Primary document dependencies
Document Requires (read before) Referenced by
QODIQA-WP-2026-001 (Technical Whitepaper) None (entry point) All corpus documents
QODIQA-CORE-2026-001 (Core Standard) QODIQA-WP-2026-001 All Tier II, III, IV documents
QODIQA-68P-2026-001 (68-Point Framework) QODIQA-WP-2026-001, QODIQA-CORE-2026-001 ARCH, SEC, CTS, CVS, GEI, IMPL, RIS, CF
QODIQA-ARCH-2026-001 (Reference Architecture) QODIQA-CORE-2026-001, QODIQA-68P-2026-001 RIS, IMPL, IDC, SBT, FHS
QODIQA-SEC-2026-001 (Security and Crypto Profile) QODIQA-CORE-2026-001, QODIQA-68P-2026-001 RIS, IMPL, TM, ETM, IDC
QODIQA-TM-2026-001 (Threat Model) QODIQA-CORE-2026-001, QODIQA-ARCH-2026-001, QODIQA-SEC-2026-001 ETM, NCC, FHS, RISK
QODIQA-CTS-2026-001 (Conformance Test Suite) QODIQA-CORE-2026-001, QODIQA-68P-2026-001, QODIQA-ARCH-2026-001 CVS, CF, AEM, ARP
QODIQA-RISK-2026-001 (Residual Risk Annex) QODIQA-CORE-2026-001, QODIQA-TM-2026-001 CF (required acknowledgement clause)
QODIQA-CF-2026-001 (Certification Framework) QODIQA-CORE-2026-001, QODIQA-CTS-2026-001, QODIQA-RISK-2026-001 GC, ARP
QODIQA-RAM-2026-001 (Regulatory Alignment Matrix) QODIQA-CORE-2026-001, QODIQA-68P-2026-001 EB (informative), EIA (informative)

#Consolidated Glossary

The following glossary consolidates all defined terms used across the QODIQA corpus. Each definition is drawn from its authoritative source document, identified in the reference field. Where a term is defined in multiple documents, the definition from the highest-tier document is used. Terms are listed alphabetically.

This glossary is informative. In the event of apparent conflict between a definition here and the definition in the source document, the source document governs.

Audit Log
A tamper-evident, hash-chained sequence of Audit Records produced by the Audit Layer for every enforcement decision. The Audit Log must be written before execution proceeds on any ALLOW path and must be written on all DENY paths. Write failure triggers DENY.
Source: QODIQA-CORE-2026-001, Section 4.2
Audit Record
A single immutable entry in the Audit Log corresponding to one enforcement decision. An Audit Record contains the frozen evaluation context, the decision outcome, the policy version applied, and a cryptographic reference to the Decision Artifact.
Source: QODIQA-CORE-2026-001, Section 4.2
Authorization
Standing technical permission granted to an actor or system to access a resource or perform a class of operations. Expressed through roles, access control lists, API keys, or service identities. Generally static, coarse-grained, and context-independent. Authorization answers: Is this actor permitted to perform this class of operation? Authorization does not satisfy the Consent requirement and must not be used as a proxy for Consent evaluation.
Source: QODIQA-WP-2026-001, Section 3.3; QODIQA-CORE-2026-001, Section 3.1
Calling System
An application, service, or agent that requests an AI action by submitting a DecisionRequest to the Enforcement Gateway. The Calling System is responsible for providing a complete, explicit intent declaration. It must not submit partial, inferred, or defaulted intent fields.
Source: QODIQA-CORE-2026-001, Section 2.3
Conformance
The state of a system that satisfies all MUST-level requirements of the declared Conformance Profile. A system claiming Conformance must declare exactly one profile (CORE-MIN, CORE-VER, or CORE-ENT) and must satisfy all requirements of that profile. Declaration of a higher profile without satisfaction of its requirements constitutes non-Conformance.
Source: QODIQA-CORE-2026-001, Section 2.4
Consent
Contextual, conditional legitimacy for a specific AI action under explicitly declared purpose, scope, time constraints, jurisdictional binding, and current Revocation state. Consent answers: Is this specific action legitimate under present conditions? Consent is granular, time-bounded, and revocable. It is distinct from Authorization and must be evaluated independently of it.
Source: QODIQA-WP-2026-001, Section 3.3; QODIQA-CORE-2026-001, Section 3.1
Consent Registry
The authoritative system component that stores and resolves current Consent state, including grants, expiry timestamps, and Revocation status. The Consent Registry is the single source of truth for Consent state at enforcement time. Registry unavailability must trigger DENY; no system may default to ALLOW when the Registry is unreachable.
Source: QODIQA-CORE-2026-001, Section 4.2
Consent Token
A cryptographically signed, machine-readable data structure that encodes a Consent grant for a specific purpose, scope, data category set, jurisdictional binding, and time window. A Consent Token must be verified for cryptographic integrity and checked against the Consent Registry for current validity before any enforcement decision proceeds.
Source: QODIQA-CORE-2026-001, QCC-02; QODIQA-68P-2026-001
Decision Artifact
An immutable, cryptographically signed record of an enforcement decision, containing the frozen evaluation context, the policy version applied, the Consent state at evaluation time, and the resulting ALLOW or DENY outcome. Decision Artifacts are the primary evidence instrument for independent Replay Verification. Artifact generation failure must trigger DENY.
Source: QODIQA-CORE-2026-001, Section 4.3; QODIQA-WP-2026-001, Section 6.6
DecisionRequest
The explicit, machine-readable input contract submitted by the Calling System to the Enforcement Gateway. A DecisionRequest must contain all required fields: actor identity, requested action, purpose, data categories, and jurisdictional context: with no missing, inferred, or defaulted values. Unknown or missing fields must result in DENY without evaluation.
Source: QODIQA-WP-2026-001, Section 6.2; QODIQA-CORE-2026-001, QCC-01
Enforcement Gateway
The system component that intercepts all AI-bound requests on the critical path and implements the six-stage enforcement lifecycle. The Enforcement Gateway must be positioned on the critical path between the Calling System and the AI System; any architectural configuration that permits bypass of the Enforcement Gateway constitutes non-Conformance.
Source: QODIQA-CORE-2026-001, Section 4.2
Fail-Closed
The required failure mode of a Conformant QODIQA implementation. A system fails closed when it issues DENY on any missing, malformed, unavailable, or unresolvable input, rather than defaulting to ALLOW or attempting partial evaluation. No partial execution occurs on any DENY path. Fail-closed behavior is mandatory and cannot be disabled or bypassed.
Source: QODIQA-WP-2026-001, Section 4.6; QODIQA-CORE-2026-001, Section 4.3
Frozen Evaluation Context
The immutable snapshot of all inputs and state present at enforcement decision time, including the DecisionRequest, the resolved Consent state, the policy version, and the evaluation timestamp. The Frozen Evaluation Context is the basis for Decision Artifact generation and Replay Verification. No element of the Frozen Evaluation Context may be modified after the enforcement decision is made.
Source: QODIQA-CORE-2026-001, Section 6.1; QODIQA-WP-2026-001, Section 6.5
Intent Declaration
The explicit, machine-readable specification of who is acting, for what purpose, on what data, and under which constraints, provided as a mandatory component of every DecisionRequest. Intent must be declared, not inferred. The enforcement system must refuse to evaluate any request for which intent has not been explicitly declared.
Source: QODIQA-WP-2026-001, Section 5.2; QODIQA-CORE-2026-001, QCC-01
Policy Engine
The system component that executes deterministic policy evaluation as a pure function over a Frozen Evaluation Context. The Policy Engine must be free of side effects and must not make external calls during evaluation. Given identical inputs and the same policy version, the Policy Engine must always produce identical outputs.
Source: QODIQA-CORE-2026-001, Section 4.2
Purpose Binding
The enforcement requirement that a Consent grant be evaluated for its validity with respect to the specific declared purpose of an AI action. An action performed for a purpose not explicitly covered by the applicable Consent Token must be denied. Inference, approximation, or generalization of purpose is prohibited.
Source: QODIQA-CORE-2026-001, QCC-03
Replay Verification
The capability to reproduce a prior enforcement decision from its Frozen Evaluation Context and confirm that the same decision would be reached under the same inputs and policy version. Replay Verification is the primary mechanism for independent audit of QODIQA enforcement behavior. All Conformant implementations must produce Decision Artifacts sufficient to support Replay Verification.
Source: QODIQA-CORE-2026-001, Section 6.3; QODIQA-WP-2026-001, Section 7.3
Revocation
The withdrawal of a previously granted Consent, effective immediately upon issuance of the Revocation event. Revocation must propagate to all enforcement nodes within the required propagation window. Any Revocation event cancels all prior grants and supersedes any cached state or prior ALLOW decision. Revocation cannot be deferred, buffered, or ignored by any component of a Conformant implementation.
Source: QODIQA-CORE-2026-001, QCC-06, R-01
Runtime
The moment of AI system invocation, the execution boundary at which a model or inference system is called to perform an action. Runtime is the only boundary where purpose, actor identity, jurisdiction, and Revocation state are simultaneously present, evaluable, and current. QODIQA enforcement operates exclusively at this boundary.
Source: QODIQA-CORE-2026-001, Section 1.3; QODIQA-WP-2026-001, Section 1
Scope Binding
The enforcement requirement that a Consent grant be evaluated for its validity with respect to the specific data categories and action scope of a request. Where multiple applicable Consent grants exist, the most restrictive scope governs (Conflict Resolution Rule R-02). Inference or assumption of broader scope is prohibited.
Source: QODIQA-CORE-2026-001, QCC-04, R-02

This glossary contains the twenty most frequently referenced terms across the corpus. Terms used exclusively within a single document are defined in that document and are not reproduced here. For a complete term inventory of any individual document, refer to the Terminology and Normative Definitions section within that document, or to QODIQA-TERM-2026-001.

#Corpus Amendment History

This section records the amendment history of the Master Index itself. For the amendment history of the full corpus, refer to QODIQA-CCL-2026-001 (Corpus Change Log and Version History).

Table 3. Master Index revision history
Version Date Change Description Author
1.0 April 2026 Initial issue. Full document index across five tiers, four reading paths, cross-reference map, and consolidated glossary for corpus Version 1.0. QODIQA

#Document Status

This document is issued as a companion navigational instrument to the QODIQA standard corpus at Version 1.0. It is classified as informative. It introduces no normative requirements and does not modify any existing document in the corpus. In the event of conflict between any statement in this document and any normative statement in a Tier I through Tier IV document, the normative statement governs without exception.

This document is intended for the following audiences:

  • Engineers and architects beginning implementation of a QODIQA-conformant system
  • Compliance and audit functions evaluating an existing or proposed implementation
  • Regulatory, legal, and policy review bodies assessing the QODIQA corpus
  • Executives and strategic decision-makers evaluating QODIQA as an institutional investment
  • Any reader approaching the QODIQA corpus for the first time

This document should be updated whenever a new document is added to the corpus, an existing document is substantially revised, or a new defined term is introduced. Updates are subject to the amendment process defined in QODIQA-GC-2026-001.

Institutional Closing Statement The QODIQA corpus addresses a structural gap in artificial intelligence governance: the absence of deterministic enforcement of consent at the moment of model invocation. This Master Index is issued in the recognition that a corpus, however rigorous, is only as accessible as its navigational instruments allow. A standard that cannot be found cannot be adopted. A term that cannot be located cannot be consistently applied. A reading path that must be inferred imposes a cost that reduces the probability of correct implementation. This document exists to eliminate that cost. QODIQA. Deterministic Runtime Consent Enforcement · April 2026

For strategic inquiries, architectural discussions, or partnership exploration:

Bogdan Duțescu

bddutescu@gmail.com

0040.724.218.572

Document Identifier QODIQA-IDX-2026-001
Title Master Index: Reader's Guide
Subtitle Navigation Reference and Consolidated Glossary for the QODIQA Standard Corpus
Publication Date April 2026
Version 1.0
Document Type Informative: Navigation Instrument
Document Status Informative, Companion Document to QODIQA Corpus v1.0
Governing Authority QODIQA Governance Charter (QODIQA-GC-2026-001)
Normative Force None. This document introduces no requirements and does not modify any normative instrument in the corpus.