Browse the reference ⌄
Artefact published

Primary Sources and Open Checks

The official texts this reference relies on (EU legal instruments with ELI links, DORA Level 2 acts, Commission and ESA publications, national law, standards, vendor documentation and the specifications hosted on this site), each with its identifier, the version or date it was read, its verification status and the pages that use it, followed by a consolidated register of the open fact-checks that still stand between a source claim and an official text.

Version
0.1.0
Owner
DEIXEI
Last reviewed
Reading time
28 min

For Cto · Ai Architect · Platform Engineer · Risk And Assurance · Compliance · Legal And Compliance · Internal Audit

Sources and details
Section
Reference
Source works
Book 1 · Book 3 · Research Series · Supporting Tools
Source chapters
6, 7
Source appendices
01:C, 04:A, 04:I
Tool specifications
audit_evidence_schema@0.1.0, cab_decision_record@0.1.0, deployer_manifest@0.1.0
Refresh trigger
quarterly

Full source list ↓ Source index →

This page is the bibliography of official texts behind the AI Delivery Factory reference, and the register of what has not yet been checked against them. It answers three questions a reviewer, an auditor or a supervisor-facing team asks before relying on a page:

  1. Which official text does this statement rest on, and which version was read?
  2. Has anyone on this reference actually read that text, or is the statement only as a book cites it?
  3. What is still open, who closes it, and where?

The books, the research papers and the Supporting Tools are the reference’s secondary sources. They supply the method, the models and most of the numbers, and each page names them in its own source notes. This page lists only the texts those sources point at: legislation, delegated and implementing acts, supervisory publications, standards, vendor documentation, and the specifications this site publishes.

It was compiled on 14 November 2026 from two things: every sourceUrls entry across the reference, and every [FACT-CHECK: …] marker in page text (347 markers on 37 pages at that date). A recount during verification on 15 November 2026 found 355 markers on 43 pages, because pages written in the current wave had been added; those pages are now placed in the groups below. A statement that carries a marker is an open check, not a source, and it appears in the open-checks register below, not in the source tables.

How to use this page

You need to…Do this
Cite an obligation externallyUse only a row marked Verified below, then read the text yourself at the official location. A book citation is not an official source.
Plan against a dateGo to the regulatory calendar. This page deliberately does not restate application, publication or deadline dates.
Map an article to a controlGo to the regulatory map. This page names instruments; the map reads them.
Configure a vendor productRead the vendor row here for what was verified and when, then check the open-checks group for that vendor before rollout.
Close a checkFollow the closing procedure.

Status labels

LabelMeaningMay a page state it as fact?
VerifiedRead against the official location on the date given, by the page that cites itYes, with the date
Verified (secondary host)Read from an official consolidation or official publisher other than EUR-Lex (the Commission’s AI Act Service Desk; the Official Journal text hosted outside EUR-Lex) because EUR-Lex refused automated retrieval during the November 2026 checkYes, with the host and date; confirm on EUR-Lex before external citation
Checked (unofficial copy)Read against an unofficial reproduction of the official textNo. Treat as cited until read on EUR-Lex
CitedNamed by a book or paper; the official text was not read for this referenceNo. Attribute it (“per Book 1 Ch 6”) and keep the marker
Vendor-datedA vendor’s own documentation, read on a date; vendor documentation is not the contractYes, as “the vendor’s documentation states, as of …”; the executed agreement governs

Level 1: regulations the reference is built on

InstrumentIdentifier and version readOfficial locationStatusUsed on
Artificial Intelligence ActRegulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744 (the AI Omnibus). Articles 14, 26, 27, 49, 50, 73 and 113 read in the Service Desk consolidated text as at 27 July 2026, accessed 15 Nov 2026ELI: eur-lex.europa.eu/eli/reg/2024/1689/oj/eng; consolidated articles at the AI Act Service DeskArticles listed: Verified (secondary host). All other articles: CitedRegulatory map, regulatory calendar, control map, risk tiers, model governance, audit evidence, incident response, data classes and lanes, authority process
AI Omnibus (amending act)Regulation (EU) 2026/1744. The OJ reference was confirmed through the Commission’s AI Act policy page (last updated 19 Oct 2026); the regulation number is as Book 2 Ch 26, Book 09 Ch 1 and Research Paper 1 cite itCommission AI Act policy page; ELI not yet recordedOJ reference: Verified (secondary host). Act date, OJ date and the other reported amendments: CitedRegulatory calendar, regulatory map
DORA (Digital Operational Resilience Act)Regulation (EU) 2022/2554. Application date confirmed on the EIOPA DORA page, 15 Nov 2026ELI: eur-lex.europa.eu/eli/reg/2022/2554/oj/eng; EIOPA DORA pageApplication date: Verified. Article-level statements: Cited unless the regulatory map marks them verifiedRegulatory map, regulatory calendar, control map, vendor concentration and exit, deployment routes, incident response, change governance, release engineering, evaluation and resilience and most build pages through the CIF tag
GDPRRegulation (EU) 2016/679. Articles 22, 28 and the processor and sub-processor concepts are used; no article was re-read for this referenceELI not yet recordedCitedRegulatory map, data classes and lanes, deployment routes, risk tiers, incident response, identity and secrets, coding-agent workstation

The control map cites the AI Act by a shorter ELI (/eli/reg/2024/1689) accessed 14 Nov 2026. It resolves to the same act; use the /oj/eng form above in new citations so every page points at one address.

Level 2: DORA delegated and implementing acts

Regulatory technical standards (RTS) are adopted as Commission delegated regulations and implementing technical standards (ITS) as Commission implementing regulations. The reference cites them by their short number, as the books do.

InstrumentWhat the reference uses it forOfficial locationStatusUsed on
RTS 2025/301: content and time limits for major-incident notifications and reportsThe 4 h / 24 h / 72 h / one-month clocks and when they start (Art 5)ELI: eur-lex.europa.eu/eli/reg_del/2025/301/oj/eng; OJ text read 15 Nov 2026Art 5: VerifiedRegulatory map (clocks), regulatory calendar, incident response
RTS 2024/1774: ICT risk-management frameworkArt 17 change management as the evidence frame for change records; the logging articleELI not yet recordedArt 17(1): Checked (unofficial copy). Logging article number and OJ date: CitedRegulatory map, regulatory calendar, audit evidence, change governance
RTS 2024/1772: classification of ICT-related incidentsArt 8 major-incident testELI not yet recordedArt 8: Checked (unofficial copy). OJ reference: CitedRegulatory map, regulatory calendar, incident response
RTS 2024/1773: policy on ICT services supporting critical or important functions provided by third partiesSupplier-policy rows; the policy count Book 1 givesELI not yet recordedCitedRegulatory map, regulatory calendar, vendor concentration and exit
ITS 2024/2956: Register of Information templatesWhich template carries the arrangement and service rowsELI not yet recordedCited (Book 1 names template B_05.02)Regulatory map (Register of Information), regulatory calendar, vendor concentration and exit
ITS 2025/302: incident-reporting templatesField list for the initial notificationELI not yet recordedCitedRegulatory calendar, incident response
RTS 2025/532: subcontracting of ICT services supporting critical or important functionsSupplier and sub-processor rowsELI not yet recordedCitedRegulatory map, regulatory calendar
RTS 2025/1190: threat-led penetration testingTLPT cadence, tester rotation and entity scope; agents in TLPT scopeELI not yet recordedCitedRegulatory map (TLPT), regulatory calendar, evaluation and resilience

Recommendation. The DORA Level 2 acts are the largest block of unverified law in the reference, and three of them drive evidence the factory produces every day (change records, incident classification, the Register of Information). Close OC-01 before any of those pages moves out of draft.

Sectoral law cited by the reference

These instruments bind regardless of AI. The reference cites them through Book 3 Appendix I §8 (NIS2 through §9) and Book 1 Ch 6–7. None was re-read for this reference; all are Cited. Identifiers are deliberately not given until they are read on EUR-Lex (OC-09).

InstrumentProvisions the reference usesUsed on
MiFID II and RTS 6Arts 16, 17 (algorithmic trading, with the RTS 6 self-assessment), 24 and 25Regulatory map
CRR3 and CRD VIInternal-model requirements, read with the ECB Guide to Internal ModelsRegulatory map, model governance
Solvency IIArt 41 (governance); Arts 112–127 (internal models)Regulatory map, authority process, implementation roadmap
Insurance Distribution Directive (IDD)Art 25 product oversight and governanceRegulatory map
PRIIPs RegulationManufacturer accuracy duty for key information documentsRegulatory map
NIS2Incident-reporting overlap with DORARegulatory map, incident response

National law and case law

InstrumentVersion readOfficial locationStatusUsed on
Italy, Legge 23 settembre 2025, n. 132 (AI law)Gazzetta Ufficiale, Serie Generale n. 223, accessed 15 Nov 2026ELI: gazzettaufficiale.it/eli/id/2025/09/25/25G00143/sgAdoption, publication and entry-into-force dates: Verified. Content as described by Book 1 Ch 6–7; delegated decrees: CitedRegulatory calendar (with the correction of Book 1 App C), regulatory map
Germany (KI-MIG), Netherlands (Uitvoeringswet AI-verordening), Spain (anteproyecto), France, BelgiumDraft or proposal status as of 30 May 2026 per Book 1 Ch 7Bundesgesetzblatt, Staatscourant, BOE, Légifrance, Moniteur belgeCited; none is yet a sourceRegulatory calendar
Switzerland: revFADP (Arts 9(1), 21, 22, 24); FINMA Guidance 08/2024; FINMA Circulars 2023/1 and 2018/3; Swiss Bankers Association Cloud Guidelines, 3rd editionCircular 2018/3 margin numbers read by Research Paper 9 against the circular as amended 4 November 2020; the rest as Book 3 App I cites themFINMA; fedlex; SBACited (Paper 9’s reading of 2018/3 is a secondary check, not a check by this reference)Regulatory map (Switzerland), data classes and lanes, deployment routes, control map
United Kingdom: Data (Use and Access) Act 2025 (substitution of UK GDPR Art 22)As of 10 Nov 2026 per Research Paper 2legislation.gov.ukCitedRegulatory calendar, regulatory map
CJEU, SCHUFA judgment (C-634/21)Case reference and date as Book 3 cites themcuria.europa.euCitedRegulatory map (GDPR Art 22), risk tiers

Commission and supervisory publications

None of these is binding law. The regulatory map labels them Guidance. Publication dates are on the regulatory calendar.

PublicationReference or versionOfficial locationStatusUsed on
Commission AI Act Service Desk: implementation timeline; consolidated articlesConsolidated as at 27 July 2026; accessed 15 Nov 2026Timeline; articles 14, 26, 27, 49, 50, 73, 113VerifiedRegulatory map, regulatory calendar
Commission AI Act policy pageLast updated 19 Oct 2026; accessed 15 Nov 2026digital-strategy.ec.europa.euVerifiedRegulatory calendar (Omnibus facts)
ESAs, first list of designated critical ICT third-party providersESMA press release; accessed 15 Nov 2026ESMA press releasePublication: Verified. List content (which providers are on it, and that no model provider is): Cited from Book 3Regulatory calendar, regulatory map, deployment routes, vendor concentration and exit, incident response
EIOPA, Opinion on AI governance and risk managementEIOPA-BoS-25-360; date and reference confirmed 15 Nov 2026EIOPA OpinionDate and reference: Verified. The seven principles and four assessment dimensions: CitedRegulatory map (sectoral layer), regulatory calendar, implementation roadmap
EBA factsheet on AI Act implications for the banking sectorDate confirmed via the EBA listing on 15 Nov 2026; canonical title differs between the PDF and Book 1EBA publicationsDate: Verified. Title and content: CitedRegulatory map, regulatory calendar, model governance
ECB Guide to Internal Models (revised)As Book 3 App I cites itECB Banking SupervisionCitedRegulatory map, regulatory calendar, model governance
ESMA statement on AI in retail investment services; ESMA supervisory briefing on algorithmic tradingAs Book 3 App I cites themESMACitedRegulatory map, regulatory calendar
BaFin guidance on ICT risks in the use of AI at financial entitiesAs Book 3 App I cites itBaFinCitedRegulatory calendar, regulatory map
Commission guidelines on high-risk classification (AI Act Art 6(5)); guidance on Art 73 serious-incident reporting; codes of practice under Art 50(7)Delayed, unverified or pending, per the calendarCommission; Service DeskNot yet sourcesRegulatory calendar, risk tiers, incident response

Standards, protocols and threat catalogues

Voluntary unless the firm adopts them or another instrument makes them binding. The control map records, for each, the edition, the adoption basis and the practices the firm chose to implement. No standard below was read against its official text for this reference. Where the books disagree on a version, the page that uses it says which it follows.

Standard or catalogueEdition the sources citePublisherUsed on
ISO/IEC 42001 (AI management system)2023, with Annex A control anchorsISOControl map, regulatory map, regulatory calendar, deployment routes, evaluation and resilience
ISO/IEC 23894 (AI risk management); ISO/IEC 27001 and 27701Not stated in the sourcesISOControl map, regulatory map, MCP and connector broker
NIST AI RMF; NIST AI 600-1 (Generative AI Profile); NIST AI 100-2 (adversarial ML); NIST SP 800-218AAI RMF 1.0NISTControl map, regulatory map, evaluation and resilience
OWASP Top 10 for Agentic Applications (ASI01–ASI10); OWASP Top 10 for LLM ApplicationsAgentic list v1.0 per Book 1 App C; the books differ slightly on version labels and titlesOWASP GenAI Security Project (genai.owasp.org)Evaluation and resilience, control map, incident response, risk tiers, MCP and connector broker, and others
MITRE ATLASv5.1.0 per Book 3 App IMITRE (atlas.mitre.org)Evaluation and resilience, control map, risk tiers, MCP and connector broker
CIS Controls; CIS benchmarksControls v8.1 (18 controls, 153 safeguards); benchmark v5.0.0 as the source cites itCenter for Internet SecurityControl map
ITIL; COBITITIL 5 as Book 1 Ch 5 cites it; ISACA’s 2025 paper on COBIT for AI governancePeopleCert / AXELOS; ISACAControl map, readiness diagnostic, implementation roadmap
CEN-CENELEC harmonised standards under standardisation request M/593 (including prEN 18286, QMS)Enquiry stage per Book 1 App CCEN-CENELEC; citation in the OJRegulatory calendar
Model Context ProtocolRevision 2026-07-28 (previous 2025-11-25); Book 3 App C was written against 2025-11-25MCP specification siteMCP and connector broker, change governance
Agent2Agent (A2A) protocolLatest released specification; version not pinned in the sourcesA2A projectMCP and connector broker, BOM and recipes, evaluation and resilience
in-toto Statementv1 (_type: https://in-toto.io/Statement/v1), used as the AES envelope; the spec does not redefine itin-toto projectAudit evidence, schemas and tools
JSON SchemaDraft 2020-12 (the AES schema’s dialect)json-schema.orgSchemas and tools, audit evidence, release engineering

Vendor documentation

The site is not vendor-neutral. Vendor facts sit on the topic pages, dated, and the executed agreement always overrides public documentation. Only the rows below were read directly by a page of this reference; everything else vendor-specific is carried as an open check (OC-18 to OC-27).

Read directly

Vendor pageRead onStatusUsed on
Anthropic, API and data retention15 Nov 2026Vendor-datedDeployment routes (ZDR by route, features that leave ZDR, HIPAA)
Anthropic, Data residency15 Nov 2026Vendor-datedDeployment routes (residency checks)
Anthropic, Claude in Microsoft Foundry15 Nov 2026Vendor-datedDeployment routes (Anthropic as processor on Foundry; hosting options)
Anthropic, Claude Platform on AWS15 Nov 2026Vendor-datedDeployment routes (inference location; MCP tunnels; separate organisation)
Anthropic, Claude models on Google Cloud, Anthropic managed15 Nov 2026Vendor-datedDeployment routes (an offering absent from Book 3)
Anthropic, Claude Agent SDK: hosting, session storage, permissions15 Nov 2026Vendor-datedDeployment routes (SDK as a process; session-store mirroring; permission pipeline)
Microsoft Learn, Azure Blueprints retirementPage dated 30 Oct 2026; checked 14 Nov 2026Vendor-datedLanding zone (retirement timeline and successors)
Microsoft Learn, Power Platform environments overview and Secure the default environmentCited by Book 2 Ch 21 and Book 09 Ch 10 (November 2026); the URLs are held on the pageCited (the page reports the books’ reading; the landing-zone page keeps a check open)Application foundation, landing zone

What the direct reading changed. Reading the vendor text on 15 November 2026 overturned several Book 3 statements, and the deployment-routes page follows the vendor text on each. Among them: who processes on Foundry (where Book 3 itself is split between appendices); inference location on Claude Platform on AWS; HIPAA eligibility per route; whether the local session file stays authoritative once a session store is in use; computer-use eligibility; and whether Foundry publishes feature-limitation and networking guidance. The difference table is on deployment routes. The glossary’s hosting-route crosswalk now follows the same reading.

Secondary vendor snapshots

Two research papers carry dated vendor-documentation snapshots that pages use with attribution. They are secondary sources, not verified primary ones:

Specifications published on this site

These are DEIXEI’s own normative files, versioned on the Supporting Tools cadence. They are primary for the fields they define. Schemas and tools explains what each requires and where the source specification contradicts itself.

SpecificationVersionLocationUsed on
Audit Evidence Schema (AES predicate)v0.1.0/aes/v0.1.0/audit_evidence_schema.jsonAudit evidence, accountability, schemas and tools, enterprise control plane, agent lifecycle, control map, agent-driven departments
CAB change (input)v0.1.0/aes/v0.1.0/cab_change.jsonChange governance, accountability, schemas and tools
CAB decision (output)v0.1.0/aes/v0.1.0/cab_decision.jsonChange governance, schemas and tools
Deployer Manifestv0.1.0/aes/v0.1.0/deployer_manifest.jsonRelease engineering, accountability, schemas and tools

Open-checks register

Each group below consolidates the [FACT-CHECK: …] markers on the named pages. A group is closed only when every marker in it has been resolved on its page. Priority is this page’s recommendation. P1 blocks an external citation, a supervisory answer or a regulated go-live. P2 blocks a configuration rollout or a contract row. P3 is context that should be confirmed before publication. Owner names the role that should close the group, also a recommendation.

Law and supervisory publications

Owner for every row: the regulatory-calendar owner in Legal and Compliance. The calendar is the canonical place to record any date the check produces.

IDOpen checkWhere to checkPages carrying itPriority
OC-01ELI links, OJ references and article pinpoints for the DORA Level 2 acts: RTS 2024/1774 (which article is the logging article; Art 17 read only on an unofficial copy), RTS 2024/1772 (Art 8), RTS 2024/1773 (the policy count Book 1 gives), ITS 2025/302 (template fields), ITS 2024/2956 (which template carries arrangement and service rows), RTS 2025/532, RTS 2025/1190 (cadence, tester rotation, entity scope)EUR-LexRegulatory map, regulatory calendar, incident response, audit evidenceP1
OC-02The “five-year floor” Book 1 App B attributes to DORA Art 9. That article is not obviously a retention-period provisionDORA and RTS 2024/1774 on EUR-LexAudit evidenceP1
OC-03DORA Art 30(2) versus 30(3) (which contract provisions apply to all ICT arrangements and which only to those supporting critical or important functions); the basis of the first-TLPT deadline; the Register of Information submission window this yearEUR-Lex; the firm’s competent authorityRegulatory map, regulatory calendar, vendor concentration and exitP1
OC-04AI Omnibus (Regulation (EU) 2026/1744): date of the act, OJ publication date, ELI, and each of the other reported changes (Art 4 AI literacy, bias-detection necessity test, small mid-cap relief, financial-sector competence)EUR-LexRegulatory calendar, regulatory mapP1
OC-05AI Act provisions not yet re-read: Art 111(3) (legacy GPAI models); Art 86 scope after the amended Art 113; Art 49(2) as consolidated; Annex III exclusions for AML and trading models; point lettering in the reproduced Art 14(4) elementsEUR-Lex; Service DeskRegulatory map, regulatory calendar, risk tiers, model governanceP1
OC-06Pending Commission deliverables: Art 6(5) high-risk classification guidelines; Art 73(7) serious-incident guidance; Art 50(7) codes of practiceCommission; Service DeskRegulatory calendar, risk tiers, incident responseP1
OC-07Content of the first CTPP designation list (Book 3: nineteen providers, including AWS, Microsoft and Google Cloud; neither Anthropic nor OpenAI) and any later roundESAs list PDF; ESAs Joint CommitteeRegulatory calendar, regulatory map, deployment routes, vendor concentration and exit, incident responseP1
OC-08DORA incident report field list against the RTS and ITS templates (Book 3’s extract is illustrative); the incident-criteria count where Book 1, Book 3 App I and App F differEUR-LexIncident response, regulatory mapP1
OC-09Identifiers and consolidated versions of the sectoral instruments (MiFID II and RTS 6, CRR3/CRD VI, Solvency II, IDD, PRIIPs, NIS2) and of GDPREUR-LexRegulatory map, model governance, authority processP2
OC-10Supervisory publications: EBA factsheet canonical title; EIOPA Opinion’s seven principles and four dimensions; ECB Guide to Internal Models revision; ESMA retail statement and algorithmic-trading briefing; BaFin AI guidance; the “EBA factsheet of 21 November 2025” wording cited by Book 1 Ch 14; the BaFin, CSSF and ESRB statements Book 3 cites on model change; EBA and EIOPA follow-up workIssuing authorities’ sitesRegulatory map, regulatory calendar, model governance, evaluation and resilienceP2
OC-11Switzerland: FINMA Guidance 08/2024 content; SBA Cloud Guidelines, 3rd edition; revFADP articlesFINMA; fedlex; SBARegulatory map, regulatory calendarP2
OC-12National layer: which Italian legislative decrees under Art 24 of Law 132/2025 were adopted and whether the delegation period held; draft status in Germany, the Netherlands, Spain, France and Belgium; UK Data (Use and Access) Act commencementGazzetta Ufficiale and Normattiva; national journals; legislation.gov.ukRegulatory calendarP2
OC-13CJEU SCHUFA judgment reference and datecuria.europa.euRegulatory map, risk tiersP1
OC-14Harmonised standards status (CEN-CENELEC, M/593, prEN 18286) and any OJ citationCEN-CENELEC; OJRegulatory calendarP2

Standards and protocols

IDOpen checkWhere to checkPages carrying itOwnerPriority
OC-15ISO/IEC 42001:2023 Annex A anchors. This reference reads A.10 as third-party relationships and puts event logging under A.6.2. Book 1 uses A.6.2.6 for audit logging in one chapter and for human oversight in anotherThe purchased standardControl mapHead of model riskP1
OC-16OWASP Top 10 for Agentic Applications version, entry titles and v2.0 status; the OWASP incident tracker’s location, incident count and category distribution; the named public incidentsgenai.owasp.orgEvaluation and resilience, incident response, regulatory calendar, recipe catalogue (ASI numbering)CISOP2
OC-17MITRE ATLAS version; CIS benchmark version; ITIL 5 launch and module structure; any ISACA COBIT focus area for AI; the 80–90% framework-overlap figure, which is the author’s estimate with no primary sourceatlas.mitre.org; cisecurity.org; PeopleCert; ISACAControl map, regulatory calendarCISO; head of operationsP3
OC-18MCP revision 2026-07-28 key changes and deprecated features; elicitation; MCP Apps isolation and per-server disable; server-delivered skills extension; current A2A specificationMCP and A2A specification sitesMCP and connector broker, change governanceAI platform ownerP2

Vendor: Anthropic and Claude

Owner for every row: the AI platform owner, with the DPO for data-handling rows. As of November 2026 the books’ Claude statements date from May to August 2026; Claude Code settings in particular move with each release.

IDOpen checkWhere to checkPages carrying itPriority
OC-19Claude Code managed settings and versions: enforceAvailableModels, the allowManaged*Only lock flags, forceRemoteSettingsRefresh, disableAutoMode, processWrapper, claudeMdExcludes, allowedProviders, cleanupPeriodDays, the env block; the default model and permission mode by version; hook event names and blocking semantics; whether --bare skips managed hooks; whether a permissions.deny match emits a hook event; IDE policy names; authentication precedence; network host listcode.claude.com settings, managed-settings, hooks, network-config, authentication and model-configuration pagesCoding-agent workstation, model governance, release engineering, identity and secrets, landing zone, incident response, change governance, evaluation and resilience, bounded agent, schemas and tools, audit evidence, risk tiersP2
OC-20Data handling per feature: ZDR eligibility of the Files API, the Messages API mcp_servers connector and batch processing; prompt-caching TTL and ZDR; Compliance API coverage per surface (including whether the Cowork gap has closed); Managed Agents trace export and retention; local transcript persistence; extended-thinking trace returnsplatform.claude.com data-retention pages; Claude Code ZDR page; admin documentationData classes and lanes, deployment routes, model gateway, audit evidence, bounded agent, vendor concentration and exit, research assistantP1
OC-21Route facts not re-read on 15 Nov 2026: Amazon Bedrock, Google-managed Google Cloud, Microsoft 365 Copilot (hosting, sub-processor listing and EU Data Boundary position), Managed Agents; per-model EU region availability (europe-west1, eu, Bedrock EU cross-region profile); Foundry EU data zone; any EU-resident Anthropic offering; SSO mediator and plan; contracting layers for the Anthropic-managed Google offering; MCP support per routeVendor documentation per route; executed agreementsDeployment routes, cloud and hosting, data classes and lanes, vendor concentration and exit, landing zone, build-configure-consume, regulatory map, incident response, glossary (Bedrock and Google-managed processor), inspection case (Foundry region), research assistant (Claude Code routing to Foundry)P1
OC-22Contract terms that only the executed agreement settles: SLA, DPA notice periods, termination and data-return terms, MACC eligibility, current pricingExecuted MSA, DPA and SOWDeployment routes, model gateway, vendor concentration and exit, build-configure-consumeP1
OC-23Model line-up and lifecycle: current model IDs and aliases per route, alias resolution, whether a consolidated deprecation schedule is now published, retirement dates per route, the restriction Book 3 records on one model’s ZDR availability, the “best” alias behaviourAnthropic models and deprecations pages; each cloud provider’s model lifecycle pageModel governance, release engineering, bounded agent, vendor concentration and exit, model gateway, schemas and tools, research assistant, inspection caseP2
OC-24Cost and administration: prompt-caching multipliers, Batch API discount, apps-gateway capabilities, spend-limit semantics and default pricing tier, Enterprise admin cost controls, Analytics API scope, OTel metric names, contribution metrics (beta status, export, per-user attribution switch), the Value tabAnthropic admin and API documentationModel gateway, factory measurement, bounded agent, research assistant (prompt-caching terms)P2
OC-25Anthropic publications the books cite: the Usage Policy (prohibited and high-risk categories, revision date; anthropic.com/legal/aup); the constitution’s wording and value ordering (anthropic.com/constitution); “Zero risk isn’t the job: a CISO’s guide to agentic AI” (the four questions, the seven requirements, the least-agency wording); “Bringing code review to Claude Code” statistics; “Running an AI-native engineering org”; “Claude models explained”; an admin post on model defaults; the champion and communications kits; the Opus 4 to 4.5 upgrade account; the customer story and incident-reporting route; the trust-centre certification list; certification eligibility and pricing; Claude Security beta terms; Outcomes; Managed Agents scheduling and vault rotation; the finance pluginsanthropic.com, claude.com/blog, code.claude.com, trust.anthropic.comRisk tiers, bounded agent, regulatory map, deployment routes, factory charter, enterprise control plane, model governance, incident response, accountability, agent-speed SDLC, agent lifecycle, implementation roadmap, evaluation and resilience, change governance, MCP and connector broker, research assistant (Usage Policy)P2 (P1 for the Usage Policy rows, which are a contract boundary)

Vendor: Microsoft, AWS and Google Cloud

Owner: the head of cloud for each provider, with the AI platform owner. Many of these were preview or announcement-stage when the books were written.

IDOpen checkWhere to checkPages carrying itPriority
OC-26Microsoft: Foundry versionUpgradeOption values and default; Foundry deployment types, data zones and the policy aliases that deny them; APIM MCP features and API Center MCP support; Entra Agent ID claims, Conditional Access status, sponsor and lifecycle workflows; Agent 365; Purview DLP on agent egress and Sentinel correlation; Purview Agent Framework SDK; Foundry PII detection; the Agent Governance Toolkit; Power Platform default-environment behaviour and Power Apps code apps; the FSI Landing Zone repository; immutable Blob retention semantics; product status per Book 1 Ch 5Microsoft LearnModel gateway, release engineering, model governance, cloud and hosting, identity and secrets, MCP and connector broker, incident response, data classes and lanes, enterprise control plane, landing zone, application foundation, agent lifecycle, risk tiers, control map, BOM and recipes, implementation roadmap, schemas and tools, build-configure-consume, glossary and accountability (Entra sponsor workflows)P2
OC-27AWS: Bedrock model lifecycle states and end-of-life behaviour; IAM action names and the eu. inference profile; AgentCore Identity, Registry, Policy, Gateway and Runtime (Book 1 Ch 14 reports Registry and Policy GA in March 2026); Bedrock Guardrails; session-tag mapping to agent identity; CodeDeploy and AppConfig progressive delivery; CloudWatch signals; App Studio regions; AWS Proton support status; DynamoDB Global Tables consistencyAWS documentationRelease engineering, coding-agent workstation, model governance, enterprise control plane, implementation roadmap, running the factory, data classes and lanes, factory measurement, application foundation, build-configure-consumeP2
OC-28Google Cloud: the agent-platform branding (Book 2 Ch 13 and others report Gemini Enterprise Agent Platform absorbing Vertex AI agent tooling in April 2026); model versions and retirement policy; Agent Identity and Agent Registry; Cloud DLP; Cloud Deploy; Firestore multi-region consistency; Application Design Center; Workload Identity Federation token lifetimeGoogle Cloud documentationModel governance, release engineering, agent-driven departments, running the factory, data classes and lanes, enterprise control plane, application foundation, identity and secretsP2
OC-29Cross-provider: guardrail capability parity; agent-identity claim formats; evidence-store immutability guarantees; MCP connector token lifetime and revocation propagation; which instruction files (such as AGENTS.md) agents read by default, and AGENTS.md stewardshipEach provider’s documentationModel gateway, audit evidence, agent lifecycle, incident response, BOM and recipes, application foundation, agent-speed SDLC; and the pages whose markers ask for every named cloud service to be re-checked: SDLC catalogue (including the starter kits), data, API and integration, agent readiness, choosing a product shape, policy, audit and actuals, workflow, recipe catalogue, agent-driven departmentsP2

Closed by a direct reading, still marked elsewhere. The Azure Blueprints retirement timeline was verified on the landing-zone page on 14 November 2026. The markers on cloud and hosting, BOM and recipes and schemas and tools can be closed by pointing to that reading, after a re-read if the page has moved. The Foundry processor statement was verified on deployment routes on 15 November 2026. The build-configure-consume marker can be closed the same way.

Other third-party claims

IDOpen checkWhere to checkPages carrying itOwnerPriority
OC-30The Ponemon 2026 Cost of Insider Risks figure and its populationThe report itselfIncident responseCISOP3
OC-31Market-data vendor licence terms on LLM or agent session useLicence agreementsRisk tiersProcurementP2
OC-32Works-council consultation as a go-live condition for per-user metrics in DE, AT and NLLegal reviewFactory measurementLegal and ComplianceP1
OC-33Supervisory expectation on production versus non-production exit rehearsalLead supervisorVendor concentration and exitSecond lineP2

Site specifications

IDOpen checkWhere to checkPages carrying itOwnerPriority
OC-34Licence for each hosted file under /aes/; publish a LICENSE notice before inviting external reuseSite owner decisionSchemas and toolsSite ownerP1
OC-35Field names and SLO targets in the running-the-factory tables against the current published Supporting Tools releaseSupporting Tools releaseRunning the factoryAI platform ownerP2
OC-36Book-internal question: whether Book 1 App F lists fewer standard-foundation components than the “eighteen” its prose and App D giveThe author; Book 1 App FSDLC catalogueSite ownerP3

Close an open check

  1. Read the official text at the location in the register. A secondary host (a consolidation service, a vendor summary, a book) does not close a legal check. It can move the row to Verified (secondary host).
  2. Record what you read: the URL, the version or consolidation date, and the date read. For vendor pages, also record the product version the page describes.
  3. Fix the page that carries the marker. Replace the marker with the dated statement. Add the URL to that page’s sourceUrls. If the official text contradicts a book, keep the book’s version visible in the page’s source-differences table, say which the page now follows, and log the book correction for the author. The books are never edited from this reference.
  4. For a legal or supervisory item, run the calendar’s change-trigger procedure and record any date there, not here.
  5. Update this page. Move the item from the register into the right source table with its status and date. Delete the register row once no page still carries the marker.
  6. Re-date the page’s updated field and, for vendor rows, set the next review against the page’s vendor-release or quarterly trigger.

Failure modes to avoid.

  • Closing on the book. A check closed by re-reading the book that raised it is still open.
  • Silent drift. A vendor row verified once and never re-read becomes wrong without anyone noticing. Vendor rows older than one quarter go back into the register.
  • Date sprawl. A dated regulatory fact copied onto a build or operate page will drift from the calendar. Link instead.
  • Treating documentation as contract. Processor, retention and notice statements go into a Register of Information entry or a contracting-matrix row only from the executed agreement. Book 3 App A §6 itself asks for the Foundry processor statement to be re-derived from current vendor text at every quarterly review; this page applies the same rule to every route (recommendation).

Acceptance checks for this page

  • Every URL in any page’s sourceUrls appears in a source table here, with its status. As of 14 November 2026 the set is the 31 URLs in this page’s frontmatter, plus the control map’s short-form AI Act ELI, which is noted under the AI Act row.
  • Every page that carries a [FACT-CHECK: …] marker appears in at least one register group.
  • No row here states an application, publication or deadline date for a legal instrument; those are on the calendar.
  • Every row marked Verified names the date read and the host.
  • Each register group names an owner and a priority, and P1 groups are reviewed before any page they touch moves from draft to review.

Source and status

This page’s synthesis: the status labels, the grouping of markers into the register, the priorities and the owners. Source claims are those recorded by the pages listed, with their dates. Verification dates come from the regulatory map and calendar (15 November 2026), deployment routes (15 November 2026), the landing-zone page (14 November 2026) and the control map (14 November 2026). This page did not read any official text itself. It compiles what the reference has read and what it has not.

Review trigger: quarterly, and whenever a page adds a sourceUrls entry or closes or adds a marker.

Source material

  • Book 1 (Building Organizations for the Age of AI), Appendix C, The Stop-the-Press Calendar (as of 10 May 2026; the three-question discipline for a moving item)
  • Book 1 (Building Organizations for the Age of AI), Chapter 6, DORA, the EU AI Act, and the Sectoral Layer (instrument list as cited, as of 15 May 2026)
  • Book 1 (Building Organizations for the Age of AI), Chapter 7, The EU AI Act, Sectoral Guidance, and the National Layer (Draft 4, as of 30 May 2026)
  • Book 3 (Deploying Claude Safely), Appendix A, Anthropic Deployment Options Matrix (revised 3 August 2026; §6 quarterly review checklist)
  • Book 3 (Deploying Claude Safely), Appendix I, Regulatory Mapping (as of 14 May 2026; §11 maintenance triggers)
  • Research Paper 3, Securing Claude Code in the Enterprise (vendor documentation as verified 10 November 2026)
  • Research Paper 9, Data Classes, Processing Lanes and Controller/Processor Roles for AI (§8.2 vendor documentation snapshot, accessed 10 November 2026)
  • Supporting Tools, spec/ (Audit Evidence Schema, CAB Decision Record and Deployer Manifest v0.1.0)
  • European Commission, AI Act Service Desk, timeline and consolidated articles 14, 26, 27, 49, 50, 73 and 113 (consolidated as at 27 July 2026), accessed 15 November 2026, as recorded on the regulatory map and calendar
  • Commission Delegated Regulation (EU) 2025/301, Official Journal text, read 15 November 2026, as recorded on the regulatory calendar
  • Anthropic platform and Claude Code documentation pages listed on the deployment-routes page, read 15 November 2026
  • Microsoft Learn, Azure Blueprints retirement (page dated 30 October 2026), checked 14 November 2026, as recorded on the landing-zone page

← All AI Delivery Factory guidance

On this page

  1. How to use this page
    1. Status labels
  2. EU legal instruments
    1. Level 1: regulations the reference is built on
    2. Level 2: DORA delegated and implementing acts
    3. Sectoral law cited by the reference
    4. National law and case law
  3. Commission and supervisory publications
  4. Standards, protocols and threat catalogues
  5. Vendor documentation
    1. Read directly
    2. Secondary vendor snapshots
  6. Specifications published on this site
  7. Open-checks register
    1. Law and supervisory publications
    2. Standards and protocols
    3. Vendor: Anthropic and Claude
    4. Vendor: Microsoft, AWS and Google Cloud
    5. Other third-party claims
    6. Site specifications
  8. Close an open check
  9. Acceptance checks for this page
  10. Source and status

All pages in Reference →