Decisions and Records
Nordvik Region is documented through its records. Each volume of the series gives the Region a stock of identifiers, and most of them name a decision, an approval, a test or a mandate that someone signed. This chapter sorts them. It shows which families of record the series attributes to the Region, what each family decides, who holds the decision, how the families refer to one another, and which decisions shaped the organisation. It draws on Books 2 to 14 and on Landscape. The full list of identifiers, with the volume and chapter that state each one, is Appendix A and is generated from the ledger; this chapter does not repeat it. The identifiers and dates are those of the volumes. The records of 2027 to 2031 are illustrative, as Chapter 21 explains, and the same holds for the decisions they carry (2, Nordqvist, 2026) (10, Nordqvist, 2026).
The AI Decision Record and its ranges
The AI Decision Record (AIDR) is the series' basic unit of decision. It states what was decided, by whom, between which options, with what review date. Each volume from AI Red Team onwards allots a number range to each organisation, and the ranges make the chronology of Chapter 21 visible in the identifiers.
| Volume | Range for Nordvik | Opening record | Subject of the range |
|---|---|---|---|
| AI Governance, AI Platform and Security | none stated | AIDR-0002, -0007, -0011, -0014, -0018, -0042, -0188, -0203, -0211 |
Reference architecture, the triage system, assistants, thresholds |
| AI Red Team | 0300 to 0399, not split between the two organisations | AIDR-0301, -0302 |
Security triage assistant; AI red-teaming |
| AI Threat | 0400 to 0499, not split between the two organisations | AIDR-0401 and later (-0409, -0416, -0420, -0425, -0431, -0471) |
The threat assessment and its commitments |
| The Transformed Security Architect | 0500 to 0549 | AIDR-0500 |
The security architect's role and craft |
| AI Boss | 0600 to 0649 (Hansa Mutual 0650 to 0699) | AIDR-0600 (and -0601) |
Algorithmic management |
| AI Blue | 0700 to 0749 | AIDR-0700 |
The security unit |
| AI Purple | 0800 to 0849 | AIDR-0800 |
The purple loop |
| AI Operations | 0900 to 0949 | AIDR-0900 |
IT operations |
| AI Leader | 1000 to 1049 | AIDR-1000 |
Leadership |
| AI Developer | 1100 to 1149 | AIDR-1100 |
Development |
| Vibe to Dev | 1200 to 1249 | AIDR-1200 |
The builder's tool |
| AI Environment | 1300 to 1349 (Hansa Mutual 1350 to 1399) | AIDR-1300 |
The environmental register and what the estate costs the environment |
Three features of the numbering matter to a reader who uses it to date things. First, numbers are not always in date order: AIDR-0802 is dated 2028-02-22 while AIDR-0803 and -0804 are dated 2028-02-08 (9, Nordqvist, 2026). Second, numbers go unused. AIDR-1133 and AIDR-1202 are unused, and AI Purple leaves spare numbers between 0807 and 0811, 0816, 0819, 0825, 0828, 0836, 0840 and 0844 to 0845 (12, Nordqvist, 2026) (13, Nordqvist, 2026). Third, numbers are sometimes reassigned: AI Boss renumbered AIDR-0603, -0604 to -0608 and -0610 from earlier values, and files AIDR-0601, dated 2026-09-18, under AIDR-0600, dated 2026-11-16, so that a record can precede the one that holds it (7, Nordqvist, 2026).
The commissioning chain
Every volume from AI Threat to AI Developer opens the Region's year with a dated record that asks a named person what a function becomes. The chain is the clearest pattern in the Region's decision-making, and the dossier sets it out as one table.
| Record | Date | Who asks | Who answers | Due | Answer |
|---|---|---|---|---|---|
ATA-NR-2026-01 (terms of reference AIDR-0401) |
2026-10-05 | The audit committee, through the regional director | CISO and AI governance lead, with the data protection officer and the Head of Benefits Unit | 2027-03-31 | No general pause; commitments at every scale; adopted by the council |
AIDR-0500 |
2026-10-12 | Regional director | CISO | 2026-11-27 | Role charter ROLE-NR-SA-01 and competence record CMP-NR-01 |
AIDR-0600 |
2026-11-16 | Regional director | HR director | 2027-06-30 | Report accepted 2027-06-30; two-year plan requested |
AIDR-0700 |
2026-11-23 | Regional director | CISO | 2027-06-30 | Report delivered two days early; answer AIDR-0732 on 2027-06-28 |
AIDR-0800 |
2028-01-11 | Audit committee | Not named in the extract (reviewers: internal audit, data protection officer, AI architect) | Not stated | AIDR-0841, 2028-04-29 |
AIDR-0900 |
2028-09-12 | Regional executive committee | Head of IT and Digitalisation | 2029-03-31 | First report and AIDR-0949 |
AIDR-1000 |
2029-09-10 | Regional director | HR director and Head of IT and Digitalisation | 2030-06-30 | Report under the record; twelve-month plan AIDR-1047 on 2030-09-02 |
AIDR-1100 |
2030-09-16 | The extract does not name the asker | Head of IT and Digitalisation | 2031-06-30 | Submitted 2031-06-27 |
AIDR-1200 |
2031-10-06 | Not a question: opens the builder workspace | Platform team | none | AIDR-1201, AIDR-1203 |
AIDR-1300 |
2032-09-20 | Not a question: adopts the environmental register and the Count rule | Head of IT and Digitalisation as register owner | none | register/environment-nr.yaml; AIDR-1309, AIDR-1322, AIDR-1329 |

Figure 22.1: The chain of commissioning records. Each record opens the year of one volume; the first is the threat assessment, the last opens a tool, not a question.
The chain has a rule that the volumes repeat. The answer to a commission is a record in the same family as the question: a charter, a plan with a review date, a list of decisions put to the committee. AI Purple shows what happens when the answer is not of that kind. The first draft of the answer to AIDR-0800 read "nine of nine mapped"; it was rewritten as five results, two claims by the provider and two untested (9, Nordqvist, 2026).
The record families
The series names many families of record. Table 22.1 groups those the extracts attribute to Nordvik Region, with the pattern of each identifier, the volume where it starts and what it decides. The table gives the families, not every instance.
| Family | Pattern and example | Starts in | What it records | Decided by |
|---|---|---|---|---|
| AI Decision Record | AIDR-0007 |
B2 | A decision on an AI system, with options and review date | The owner named in the record; tier by matrix |
| Fundamental rights impact assessment | FRIA-2026-002, -007 |
B2 | Assessment of a high-risk deployment under Article 27 | The Region as deployer |
| Data protection impact assessment | DPIA-2026-007, -031 |
B2, B7 | Data protection risk | The Region, with the data protection officer |
| Use case, descriptor, legal mandate | UC-2026-017, UCD-2026-022, LM-2026-009 |
B2 | Intake and basis of an AI use | Business owner; Head of Digital Services signs the descriptor |
| Public algorithm register entry | NR-ALG-2026-003, -007, -009 |
B2 | Public entry for an algorithmic system | Owner named per entry |
| Mandate manifest | MND-NR-01, MND-NR-SOC-01, MND-NR-OPS-003, MND-NR-LDR-01, MND-NR-DEV-01, MND-NR-BLD-2031-01 |
B6 | What an agent or assistant may read, write and run | CISO (security), platform lead or Head of IT, by volume |
| Delegation profile | DLG-NR-SEC-01, -ROS-01, -EXE-01, -OPS-001, -DEV-01, -LOOP-01 |
B7 | Level per class of action | Named owner with the parties; negotiated where the staff are affected |
| Decision-rights file or register | DRF-NR-01, -SOC-01, -LOOP-01, DRF-NR-001, DRR-NR-001 |
B7 | Who may decide, stop or approve | The record's owner |
| Role charter | ROLE-NR-SA-01, -SEC-DET, -MGR-01, -DIR-01, -DEV-01 |
B6 | Rights, vetoes and limits of a post | The owner (the CISO for ROLE-NR-SA-01), endorsed by the regional director |
| Competence record | CMP-NR-01, -02 to -07, -21, CMP-NR-2029-21 |
B6 | Assessed competence with a validity date | The assessor named in the record |
| Exception | EXC-NR-0007 |
B6 | A time-limited departure from a control | CISO (tier 2) |
| Exit plan and test | EXIT-NR-01 to -03, RST-NR-2029-001, RST-NR-2031-0001 |
B5, B6 | Ability to leave a supplier, with a test | Owner named in the record |
| Threat register entry | THR-NR-01 to THR-NR-09 |
B5 | A risk with evidence rung and review | CISO; reviewed twice a year |
| Rules of engagement | RoE-NR-2027-001, -002, -003, RoE-NR-2028-001 |
B4 | Scope and limits of a test | CISO and the head of the affected unit |
| Finding and regression case | FND-NR-2027-007, REG-NR-0004 |
B4, B9 | A defect, and the test that keeps it closed | Owner of the control |
| Detection, hunt, case, playbook | DET-NR-0001, HNT-NR-0001, CASE-NR-0231, PBK-NR-ISOLATE-01 |
B8 | Security operations artefacts | Detection owner |
| Service, objective, runbook, observer | SVC-NR-001 to -008, SLO-NR-001, RBK-NR-0002, OBS-NR-0001 |
B10 | Operations artefacts | Platform lead |
| Incident, post-incident review, problem | INC-NR-2026-0071, PIR-NR-2026-0071, PRB-NR-0007 |
B10 | An incident and its lessons | Incident commander (duty manager) |
| Change, restore test | CHG-NR-2028-0007, RST-NR-2027-001 |
B10 | A change; a timed restore | Platform lead; Head of IT |
| Management decision, contestation | MDR-NR-0001, CNT-NR-0001 |
B7 | A schedule decision; a challenge to it | Unit manager; reviewer from HR |
| Footprint, benefit, budget | FPR-NR-0001 to -0008, BEN-NR-0001, -0003, -0006, EBG-NR-0001 to -0004 |
B14 | The energy and carbon of one use, the benefit it claims and the monthly budget with a drilled stop | Use owner; register owner; the regional AI board for budgets of 1,000 to 4,000 kWh |
| Claim, supplier disclosure, hardware, placement, watchlist | CLM-NR-0001, SDR-NR-0001 to -0003, HWL-NR-0001, PLC-NR-0001, WCH-NR-0001, MPL-NR-0001, MCR-NR-0001 |
B14 | A public statement with its boundary and withdrawal rule; what suppliers disclose; reserved capacity; where and when work runs; five markers read every 90 days; measurement plan; model choice | Regional director for a published claim; owners named in the records |
| Legal register, stop path, mandate and delegation for environmental agents | LGL-NR-0001 to -0003, STOP-NR-ENV-01, RBK-NR-ENV-001, MND-NR-ENV-0001, DLG-NR-ENV-0001, ROLE-NR-ENV-01, CMP-NR-ENV-02, TA-NR-ENV-01 |
B14 | Rules as of a date; the route that stops an assistant; limits per session and month; the post of environmental owner; a procurement annex | CIO and platform on-call hold the stop; the procurement manager holds the annex |
| Leadership decision, span, accountability | LDR-NR-2029-0003, SPN-NR-2029-01, ACC-NR-2030-01 |
B11 | Leadership decisions and structure | The named leader |
| Specification, ownership, review, run, provenance | SPC-NR-2030-0001, OWN-NR-2030-04, RVW-NR-2031-0001, RUN-NR-2030-0019, PRV-NR-2031-0001 |
B12, B13 | Development artefacts | Owner named in the record |
| Build, handover, takeover test | BLD-NR-2031-0001, HND-NR-2031-0001, TKT-NR-2031-0001 |
B13 | The builder's artefacts | The builder; the manager (Gunilla Roos) approves |
| Plan and horizon register | PLAN-NR-SA-2027, PLAN-NR-OPS-2029-01, HZN-NR-SA-01 |
B6 to B13 | The plan for two years and what would change it | Owner named in the plan |
Table 22.1: Record families attributed to Nordvik Region. The families DEC and KBV, which the blueprint of this book lists among the series' families, are Hansa Mutual's. No DEC-NR or KBV-NR appears in the extracts for Nordvik Region (11, Nordqvist, 2026) (12, Nordqvist, 2026).
Two naming facts need care. There are two reversibility tests with similar identifiers: RVT-NR-2027-01 in AI Threat (a month without the claims ranker) and RVT-NR-ROS-2027-01 in AI Boss (the rostering system, 5 to 16 April 2027). They are different tests of different systems (5, Nordqvist, 2026) (7, Nordqvist, 2026). And the identifier RST-NR-2031-0001 is used twice: for the exit test of the code model on 2031-02-03 in AI Developer and for the builder's restore test on 2031-12-05 in Vibe to Dev. That clash is an open thread (12, Nordqvist, 2026) (13, Nordqvist, 2026).
How the families relate
A record refers upwards to the decision that authorises it and sideways to the record it constrains. The relations that the volumes establish are few, and each is a reference by identifier.
- A decision to a mandate. An AIDR decides that an agent may exist and a manifest says what it may touch:
AIDR-0511andMND-NR-01;AIDR-0714andMND-NR-SOC-01;AIDR-0916andMND-NR-OPS-003;AIDR-1108andMND-NR-DEV-01;AIDR-1201andMND-NR-BLD-2031-01. - A mandate to a ceiling. A role charter or a delegation profile sets a ceiling that the manifest must not exceed. The charter of 2027-01-01 sets Level 1 Assisted for the security architect's tools, while
MND-NR-01versions 1.0.0 and 2.0.0 allowed edits at Level 2 Supervised until version 3.0.0 aligned them in May 2027. "A later instrument governs," the volume concludes, and the volumes differ on whether the four-month gap was ever exercised (Chapter 27) (6, Nordqvist, 2026). - A decision to a test. A decision that sets a limit names the test that shows it holds:
AIDR-0910forbids scripted runbooks at Level 3 until the observerOBS-NR-0001is in force;AIDR-1111requires a gate the change cannot edit, a named owner and a rehearsed revert within 90 days. - A test to a claim. A test result carries an expiry, and a claim without a current result is written as untested (Chapter 23). The coverage records
COV-NR-0001to-0009and the restore tests are the two cases. - A plan to its triggers. A plan lists the events that would reopen its decisions: the horizon registers
HZN-NR-SA-01,-BT-01,-PL-01,-OPS-01and the plan recordsPLAN-NR-SA-2027,-BT-2027,-LOOP-2028,-MGT-2027,-OPS-2029-01.
Who decides
The extracts give four layers of decision authority, and the volumes do not number them in the same way. The Transformed Security Architect defines three tiers in AIDR-0512: tier 1 is the platform's own gates; tier 2 is the CISO with the enterprise architect; tier 3 is the AI governance board and the regional director; the political level is the regional executive committee. Landscape has five seats, T0 for none, T1 for a user or operator, T2 for a system owner or architect, T3 for an executive or director and T4 for a board or elected body. The two scales do not map onto each other without a rule, and the dossier does not give one (6, Nordqvist, 2026) (15, Nordqvist, 2026).
The persons who hold decisions are in Chapter 24. The rights to stop a system are the subject of most of the decision records of 2027 to 2031 and are set out here.
| System | Who may stop it | Within | Record |
|---|---|---|---|
| Benefits-triage ranking | Head of Benefits Unit; team leaders may suspend ranking; senior caseworker, head of social services and the on-call platform engineer hold stop decisions in the harm-path review | 60 seconds to date order (B2); five minutes (B3) | AIDR-0011, HPR-NR-2026-01 |
| Rostering system | Unit manager pauses open shifts; HR director stops it across the Region; platform on-call stops it technically | 15 minutes; one hour | DRF-NR-01 |
| Security AI | CISO, duty security officer, MSSP shift lead (out of hours) | 15 minutes (the supplier's AI, MS-2); 10 minutes (own budget) |
NR-SEC-PROG-2027, AIDR-0731 |
| Security architect's AI tools | The security architect | 15 minutes | ROLE-NR-SA-01 |
| Operations assistant and runbooks | Duty manager, platform lead, on-call platform engineer without approval; regional director as backstop | Not stated | DRF-NR-001 |
| Leadership assistants | CISO and the system owner, among others | Not stated | DRR-NR-001 |
| Builder's tool | Platform team | Not stated | AIDR-1200 |
| Citizen-service assistant, environmental budget | Platform on-call with the CIO, through the gateway route STOP-NR-ENV-01; the regional director can order it |
Inside a minute at 1.10 of the quota (drilled 14 minutes against 10, then 6 minutes 20 seconds) | EBG-NR-0001, AIDR-1328 |
The line between a stop and a decision about a person is the same in every volume. A system may rank, draft or propose; it does not decide on a named person's employment, pay, discipline or access to work. DLG-NR-EXE-01 leaves the people class undelegated, DLG-NR-DEV-01 does the same, and DRF-NR-01 caps the consequence function at Level 1 Assisted, stricter than the series' default (7, Nordqvist, 2026) (11, Nordqvist, 2026) (12, Nordqvist, 2026).
Decisions that shaped the Region
The dossier selects ten decisions that, in the volumes' own accounts, changed what the Region is. None of them is a technical choice alone.
- Keep the leverage in the contract (
AIDR-0007,AIDR-0011,AIDR-0211, 2026). The Region is a deployer that buys, and the two volumes of 2026 conclude that the contract, not the platform, is where it holds power. The benefits-triage system displays a band and three reasons and not the score (AIDR-0011), and the staff assistant runs on an open-weight model with the Region's keys (AIDR-0211, option A of three, weighted score 4.30) (3, Nordqvist, 2026). - Pause, and do not defend (
AIDR-0601, 2026-09-18). A public employer that must give reasons cannot run a ranking it cannot explain. The pause of the screening pilot gave every later procurement a requirement (7, Nordqvist, 2026). - Do not pause AI as a whole (
ATA-NR-2026-01). No register entry shrinks more from a pause than from commitments, and the one threat that grows with a pause isTHR-NR-02(5, Nordqvist, 2026). - Mandate before tools (
NR-SEC-PROG-2027, 2027-01-18). The charter caps the security AI at Mode 4 and offensive work at Level 2 (4, Nordqvist, 2026). - Defer the agent team (
AIDR-0503, 2026-11-04). Capacity, not technology, decides; the reopening triggers are a second security-architect post, agent operators and a Mode 5 agent in the environment (6, Nordqvist, 2026). - Negotiate the profile and how it changes (
AIDR-0602,AIDR-0627, January 2027). Class 1 changes are negotiated before the decision, class 2 are notified with a difference ten working days ahead, class 3 are notified (7, Nordqvist, 2026). - Take over detection one rule at a time (
AIDR-0701,AIDR-0719,AIDR-0726). The Region creates a detection owner and a trainee post, and keeps the supplier's AI visible through annexMS-2(8, Nordqvist, 2026). - Report coverage as tested, asserted or untested (
AIDR-0814,AIDR-0815, 2028). A claim without a result younger than 180 days counts as untested (9, Nordqvist, 2026). - Set the ceiling at Level 1 and keep it (
AIDR-1002, 2029;AIDR-1135, 2031). The leader's profile and the developer's profile the leader's profile stays at Level 1 in every class and the developer's generation classes stay at Level 1, with no Level 4 anywhere (11, Nordqvist, 2026) (12, Nordqvist, 2026).
Across the degrees of delegation
The delegation profiles are the records that set a degree of delegation per class of action. The table shows the ceiling each sets. It is a list of the Region's own profiles and not a model.
| Profile | Class or system | Level | Note |
|---|---|---|---|
NR-SEC-001 |
Security triage | Level 1 Assisted | Read-only identity svc-nr-sec-001 |
NR-SEC-003 |
Exposure prioritisation | Level 0 Advisory | |
NR-SEC-PROG-2027 |
Offensive work | maximum Level 2 | Irreversible actions Level 1 |
DLG-NR-ROS-01 |
Rosters and routes | Level 2 | Open shifts Level 3 in v1.0.0 (clash with L); rest flags Level 1 |
DRF-NR-01 |
Consequence (M3) | maximum Level 1 | Hire: no system; pay review: class named |
DLG-NR-OPS-001 |
Production-changing classes | maximum Level 2 | One class at Level 3 only after the observer test |
MS-2 classes MS2-C1, -C2, -ISO |
The supplier's closures and isolation | Level 3 Bounded | All other classes Level 1 |
DLG-NR-EXE-01 |
Leadership classes | Level 1 | People class undelegated |
DLG-NR-DEV-01 |
Specify, design, review, deploy, operate, migrate | Level 0 | Generate, refactor, test Level 1; document Level 2 |
permit-by-tier.yaml |
Builder assistant | maximum Level 3 Bounded | Never Level 4 |
The ceiling and the practice are not the same in every case. AI Leader records that practice before DLG-NR-EXE-01 was Level 0 in most classes, and AI Developer records that the platform team's drafting is at Level 2 from AIDR-1116 while the generate ceiling is Level 1 (11, Nordqvist, 2026) (12, Nordqvist, 2026).
- Count before claiming (
AIDR-1300,AIDR-1309,AIDR-1322, 2032). The Region adopts a register of its uses, continues a use without an environmental claim when it is unmeasured, and withdraws its own published figure of 1.90 g per resolved enquiry, 2,235 days old, until an independent check exists (14, Nordqvist, 2026).
Inconsistencies in the records
The records disagree in ways that the dossier does not resolve. Chapter 27 collects them.
| Record | Disagreement | Volumes |
|---|---|---|
| FRIA for triage | FRIA-2026-002 (complete 2026-06-20, notified 2026-07-02) against a FRIA summary for NR-ALG-2026-003 (complete 2026-02-11, notified 2026-02-18) |
B2 Ch. 10 and 17 |
| EU database identifier | EUDB-DEP-2026-004213 (Ch. 9) against EUDB-2026-NR-00412 (Ch. 17) |
B2 |
| Register entries | NR-ALG-2026-007 used for the staff assistant (B2 Ch. 15); NR-ALG-2026-003 for living-support triage |
B2 |
| AI Act role of the staff assistant | provider in NR-UC-020; deployer in UCD-2026-022; "compound system provider, general-purpose model deployer" in B3 |
B2, B3 |
| Risk record names | NR-RISK-2027-014 (B4 Ch. 5), NR-RISK-AI-014 and -016 (Ch. 13); finding names NR-FND-2027-014 against FND-NR-2027-007 |
B4 |
| Plan measures | PLAN-NR-SA-2027 has four measures in the chapter and six in the profile; PLAN-NR-MGT-2027 has N1 to N5 in one chapter and N1 to N7 elsewhere |
B6, B7 |
AIDR-0501 |
proposed in Ch. 5, treated as decided in Ch. 25 |
B6 |
AIDR-1102 |
Cited as two decisions (ambient completion, pilot to 2030-12-31) | B12 |
AIDR-0211 date |
2026-06-18 against use from April and general availability on 2026-06-01 | B2, B3 |
MND-NR-01 and the charter |
Level 2 in the manifest against Level 1 in the charter for four months | B6 |
| Dashboard classification | Open in the profile; decided as high-risk in AIDR-0609 |
B7 |
AIDR-1300 to -1349 |
Numbered 1300 plus chapter, with second decisions from AIDR-1326; AIDR-1310, -1316 and -1323 are not listed in the allocation table; AIDR-1318 is dated 2032-11-02 but cited for the district-heating study, and HWL-NR-0001, TA-NR-ENV-01, SDR-NR-0001 and -0003 carry no AIDR |
B14 |
FPR-NR-0007 |
The next-use number in the profile and the model footprint sheet in its Chapter 5; the platform team's Mode 3 tool became FPR-NR-0008 (renumbered); EBG-NR-0002 became -0003 for placement |
B14 |
Open threads
The disagreements on the FRIA, the EU database identifier and the register entries, and the collision of RST-NR-2031-0001, are the clearest candidates for a decision by the owners of the series. They are listed in Chapter 27 with the rest.
Summary
The Region's decisions leave records of a few families, and the volumes use the same few relations between them. A commission opens each year, an answer in the same family closes it, a mandate follows a decision, a ceiling bounds the mandate and a test bounds the ceiling. The dossier's own conclusions are three. First, the Region decides slowly and in writing: nine decisions shape it, and none removes the contract as its main lever. Second, the stop right is the most carefully assigned right in the records, and its holder is almost always a named role that can act without asking: a duty manager, a team leader, the on-call engineer. Third, the records are not yet consistent: they differ on tiers, on identifiers, on dates and on which version of a plan applies. A reader who uses the identifiers needs Appendix A and the findings of Chapter 27 as well as this chapter.
Sources
- Nordqvist, G. AI Governance: Governing Artificial Intelligence in European Enterprises and Public Authorities. (2, Nordqvist, 2026)
- Nordqvist, G. AI Platform and Security: Building and Securing AI Platforms in European Enterprises and Public Authorities. (3, Nordqvist, 2026)
- Nordqvist, G. AI Red Team: AI as an Active Part of Cyber Defence in European Enterprises and Public Authorities. (4, Nordqvist, 2026)
- Nordqvist, G. AI Threat: Are the Dystopias Coming True? Evidence, Risk and Response for European Enterprises and Public Authorities. (5, Nordqvist, 2026)
- Nordqvist, G. The Transformed Security Architect: Role, Craft and Career in the Age of AI in European Enterprises and Public Authorities. (6, Nordqvist, 2026)
- Nordqvist, G. AI Boss: When Artificial Intelligence Manages People in European Enterprises and Public Authorities. (7, Nordqvist, 2026)
- Nordqvist, G. AI Blue: How Artificial Intelligence Transforms the Blue Team in European Enterprises and Public Authorities. (8, Nordqvist, 2026)
- Nordqvist, G. AI Purple: How Red and Blue Learn Together When AI Joins the Loop in European Enterprises and Public Authorities. (9, Nordqvist, 2026)
- Nordqvist, G. AI Operations: How Artificial Intelligence Transforms IT Operations in European Enterprises and Public Authorities. (10, Nordqvist, 2026)
- Nordqvist, G. AI Leader: How Leadership Roles Change When AI Is Used Broadly in European Enterprises and Public Authorities. (11, Nordqvist, 2026)
- Nordqvist, G. AI Developer: How the Developer Role Changes When AI Is Used Broadly in European Enterprises and Public Authorities. (12, Nordqvist, 2026)
- Nordqvist, G. Vibe to Dev: From Vibe Coding to Professional Software, Step by Step, for Builders Who Are Not Developers, in European Enterprises and Public Authorities. (13, Nordqvist, 2026)
- Nordqvist, G. AI Environment: Designing AI for the Greatest Benefit and the Least Environmental Harm in European Enterprises and Public Authorities. (14, Nordqvist, 2026)
- Nordqvist, G. Landscape: A Fact-Based Picture of Architecture and AI at Work, for Leaders, Architects and Citizens. (15, Nordqvist, 2026)