Private preview. Not published and not indexed.

Living Debate LD-12

Regulation-in-Practice: Rights, Compliance & Developmental Steering

Living Debate LD-12, version v0.1. Status (verbatim): LIVING DEBATE v0.1 — LOCKED..

Version

Pinned version v0.1 (entry LD-12--v0.1) — this page never floats to newer evidence.

This pinned version is also the current version.

Versions:v0.1 · current

The question

What does AI regulation become after legislation is announced or enacted?

A useful answer requires separating:

IN FORCE ≠ APPLICABLE ≠ ENFORCEABLE.

Answer in this version

AI regulation is not one regime and cannot be understood from statutory text alone.

The strongest current evidence supports a hybrid, institutionally differentiated picture:

The best-supported overall position is therefore:

HYBRID / INSTITUTIONALLY DIFFERENTIATED REGULATION.

What we still do not know

R08 does not establish:

What evidence would change the picture

The synthesis would materially change with:

Positions

Claims and evidence

Each claim states what it does not license and what would change it.

A — Implementation/enforcement

The EU AI Act is in force, but Annex III high-risk obligations apply from 2 December 2027 and Annex I product-embedded high-risk obligations from 2 August 2028.

FACTMATUREEU / English

Does not license
That the AI Act is wholly inactive or that high-risk systems are otherwise unregulated
What would change this claim
Further legislative amendment or annulment
Source and status

On the Commission's September 2026 list, 9 EU Member States had a final AI Act market-surveillance single point of contact, 12 were pending final adoption and 6 had none listed.

FACTEMERGINGEU / English

Does not license
That no enforcement can occur or that final authorities have adequate resources
What would change this claim
Updated Commission list or resource reports
Source and status
  • Source: European Commission, Market Surveillance Authorities under the AI Act — source class: ADMINISTRATIVE_RECORD_OR_DATASET (as printed: “Government administrative record”)
  • Publication status: ELIGIBLE (DATE_OR_METRIC)
  • Verification state: CONTENT_VERIFIED_PRIMARY
  • Read the original: European Commission, Market Surveillance Authorities under the AI Act

The EU AI Office began using information-request powers after its GPAI enforcement powers became applicable; the exact report that more than 30 providers received initial RFIs remains press-relayed.

FACT (QUALIFIED)EMERGINGEU / English

Does not license
Provider non-compliance, future sanctions or exact recipient identities
What would change this claim
Official Commission source with count or later formal measures
Source and status
  • Source: European Commission enforcement framework; Agence Europe relay of Commission statement — source class: GOVERNMENT_PRIMARY, POLICY_RESEARCH_OR_MONITORING (as printed: “Government primary + specialist press”)
  • Publication status: ELIGIBLE (QUALIFIED)
  • Verification state: POWERS_AND_START: CONTENT_VERIFIED_PRIMARY; COUNT_OVER_30: RELAYED_ORIGINAL_NOT_VERIFIED (PARTIAL_VERDICT)
  • Read the original: European Commission enforcement framework

The New York State Comptroller concluded NYC's enforcement of Local Law 144 was ineffective; 75% of test calls were misdirected, and DCWP identified one issue where auditors identified at least 17 potential issues in the same 32-company review.

FACTEMERGINGUS-NYC / English

Does not license
General violation rate or conclusions about other regulators
What would change this claim
Post-audit enforcement data showing material improvement
Source and status
  • Source: NYS Comptroller Audit 2024-N-6 — source class: GOVERNMENT_AUDIT_OR_EVALUATION (as printed: “Government audit primary”)
  • Publication status: ELIGIBLE
  • Verification state: CONTENT_VERIFIED_PRIMARY (PRIMARY_AUDIT)
  • Read the original: NYS Comptroller Audit 2024-N-6

B/E — Compliance organisation / standards

The EU GPAI Code of Practice is voluntary, but Commission guidance recognizes adherence as a route to demonstrate compliance; non-signatories must demonstrate compliance by other adequate means.

FACTRAPIDLY MATURINGEU / global providers / English

Does not license
That signatories are substantively compliant or safer
What would change this claim
Enforcement showing code adherence insufficient or revised guidance
Source and status
  • Source: European Commission GPAI Code and provider guidelines — source class: GOVERNMENT_PRIMARY (as printed: “Government primary guidance”)
  • Publication status: ELIGIBLE
  • Verification state: CONTENT_VERIFIED_PRIMARY
  • Read the original: European Commission GPAI Code and provider guidelines

B — Compliance organisation

In the 2025 IAPP/Credo AI survey, 77% of surveyed organizations reported working on AI governance and only 10 of 671 expected to need no additional AI-governance staff within a year.

ESTIMATEEMERGINGGlobal, North Atlantic skew / English

Does not license
Effectiveness, harm reduction or population representativeness
What would change this claim
Probability-sample staffing data or administrative evidence
Source and status
  • Source: IAPP/Credo AI, AI Governance Profession Report 2025 — source class: PROFESSIONAL_ASSOCIATION, SURVEY (as printed: “Professional-association survey”)
  • Publication status: ELIGIBLE (SOURCE_POSITION)
  • Verification state: CONTENT_VERIFIED_PRIMARY
  • Read the original: IAPP/Credo AI, AI Governance Profession Report 2025

B/C/E — Compliance / rights / audit infrastructure

In an audit-style study of 391 NYC employers after Local Law 144 took effect, 18 posted bias-audit reports and 13 posted transparency notices; employer scope discretion means those counts are not a violation rate.

FACTMATUREUS-NYC / English

Does not license
A non-compliance rate or AEDT bias prevalence
What would change this claim
Regulator-linked replication or later compliance series
Source and status
  • Source: Wright et al., Null Compliance, FAccT 2024 — source class: PEER_REVIEWED_CONFERENCE_PAPER (as printed: “Peer-reviewed article”)
  • Publication status: ELIGIBLE
  • Verification state: CONTENT_VERIFIED_PRIMARY
  • Read the original: Wright et al., “Null Compliance,” FAccT 2024

C — Rights/remedies

The CJEU held in C-203/22 that an automated-decision subject is entitled under GDPR to meaningful information about the procedure and principles actually applied; merely handing over a complex formula or algorithm is insufficient.

FACTMATUREEU/Austria / multilingual official judgment

Does not license
Common use, low procedural burden or successful remedy rates
What would change this claim
DPA/court use-rate and remedy-outcome data
Source and status
  • Source: CJEU C-203/22, ECLI:EU:C:2025:117 — source class: COURT_DECISION_PRIMARY (as printed: “Court decision primary”)
  • Publication status: ELIGIBLE
  • Verification state: CONTENT_VERIFIED_PRIMARY
  • Read the original: CJEU C-203/22, ECLI:EU:C:2025:117

C/A — Rights/remedies / enforcement

Italy's €15 million GDPR fine on OpenAI was annulled by the Court of Rome in March 2026 on competence grounds under the GDPR one-stop-shop; the court did not resolve the substantive allegations.

FACTEMERGINGItaly/EU / Italian + English

Does not license
That OpenAI's processing was lawful or GDPR cannot constrain GenAI
What would change this claim
Appeal reversal, CJEU reference or lead-DPA action
Source and status
  • Source: Garante Decision No. 755 of 2 Nov 2024; Court of Rome R.G. 4785/2025 judgment — source class: REGULATOR_PRIMARY, COURT_DECISION_PRIMARY (as printed: “Regulator primary + judgment text copy”)
  • Publication status: ELIGIBLE (QUALIFIED)
  • Verification state: CONTENT_VERIFIED_PRIMARY
  • Read the original: Garante Decision No. 755 of 2 Nov 2024

A/F — Implementation / market shaping

Colorado's original 2024 AI framework was delayed, stayed from enforcement before its operative date, and replaced in 2026 by a narrower disclosure/ADMT regime whose core duties begin in 2027.

FACTEMERGINGUS-Colorado / English

Does not license
That federal pressure caused the replacement
What would change this claim
Further amendment or 2027 implementation evidence
Source and status
  • Source: Colorado General Assembly SB24-205, SB25B-004, SB26-189; official fiscal/court-order record — source class: LEGAL_PRIMARY, MULTIPLE_SOURCE_TYPES (as printed: “State legislative primary + official record”)
  • Publication status: ELIGIBLE (QUALIFIED)
  • Verification state: CONTENT_VERIFIED_PRIMARY

D/F — Developmental steering / market shaping

U.S. Executive Order 14365 directed a federal AI Litigation Task Force to challenge selected state AI laws and tied eligibility for some non-deployment BEAD funds to state AI-law conditions; the order itself does not automatically preempt state law.

FACT + INTERPRETATIONEMERGINGUS / English

Does not license
That challenged state laws are unlawful or automatically preempted
What would change this claim
Court rulings, funding withholding or federal statute

A newer version of this Claim exists.

Source and status
  • Source: Executive Order 14365; DOJ AI Litigation Task Force memorandum — source class: GOVERNMENT_PRIMARY (as printed: “Federal government primary”)
  • Publication status: ELIGIBLE (QUALIFIED)
  • Verification state: CONTENT_VERIFIED_PRIMARY
  • Read the original: Executive Order 14365; DOJ AI Litigation Task Force memorandum

D/A — Developmental steering / implementation

China's CAC reported 1,112 generative-AI services filed and 731 applications/functions registered by 31 August 2026, up from 988 and 598 at the end of June.

FACTRAPIDLY MATURINGChina / Chinese

Does not license
Capability, quality, adoption, safety, market share or rejection rate
What would change this claim
Rejection/rectification data or rule change
Source and status
  • Source: CAC filing notices including Jul–Aug 2026 notice — source class: GOVERNMENT_PRIMARY (as printed: “Government administrative primary”)
  • Publication status: ELIGIBLE
  • Verification state: CONTENT_VERIFIED_PRIMARY

F/D — Market shaping / steering

China's CAC notices require launched generative-AI applications or functions to display the filed/registered service or model they use, including the model name and filing or launch number.

FACT + INTERPRETATIONEMERGINGChina / Chinese

Does not license
Measured concentration, competition or compliance rates
What would change this claim
Market-share or compliance evidence
Source and status
  • Source: CAC filing notices — source class: GOVERNMENT_PRIMARY (as printed: “Government primary”)
  • Publication status: ELIGIBLE (INTERPRETATION_LABEL)
  • Verification state: CONTENT_VERIFIED_PRIMARY

D — Developmental steering

China's State Council set policy targets for application penetration of new-generation intelligent terminals and AI agents above 70% by 2027 and above 90% by 2030; these are targets, not measured outcomes.

FACT + UNKNOWNEMERGINGChina / Chinese

Does not license
Achieved adoption or equivalence to ordinary GenAI user penetration
What would change this claim
Official indicator definition and measured values
Source and status

South Korea is using staged public support and competitive evaluation to narrow a sovereign-foundation-model field; official Phase 2 results advanced Upstage, SK Telecom and LG AI Research to the next round.

FACTEMERGINGSouth Korea / Korean + official English

Does not license
That the programme caused model capability or achieved technological sovereignty
What would change this claim
Later evaluation results, expenditure and capability outcomes
Source and status
  • Source: MSIT official Sovereign AI Foundation Model releases — source class: GOVERNMENT_PRIMARY (as printed: “Government primary”)
  • Publication status: ELIGIBLE (CURRENT_STAGE)
  • Verification state: CONTENT_VERIFIED_PRIMARY

The EU AI Gigafactory programme is at procurement stage: the formal call opened in July 2026, closes in November 2026 and contemplates up to seven facilities; operational capacity is not yet established.

FACTEMERGINGEU / English

Does not license
Deployed compute, disbursed total funding, realized access or sovereignty outcome
What would change this claim
Contract awards, construction, operational/utilization data
Source and status
  • Source: EuroHPC JU AIGF call; European Commission AI Gigafactories page — source class: GOVERNMENT_PRIMARY (as printed: “Government procurement primary”)
  • Publication status: ELIGIBLE
  • Verification state: CONTENT_VERIFIED_PRIMARY
  • Read the original: EuroHPC JU AIGF call

A/D — Implementation / steering

South Korea's AI Basic Act and implementing decree are in force; an at-least-one-year grace policy deferring most fact-finding and administrative fines is reported by the U.S. International Trade Administration as MSIT implementation policy.

FACT (QUALIFIED)EMERGINGSouth Korea / Korean + English

Does not license
That Korea has no enforceable law or that compliance levels are known
What would change this claim
MSIT primary notice ending/defining grace or first sanctions
Source and status
  • Source: Korean National Law Information Center; U.S. ITA implementation report — source class: LEGAL_PRIMARY, GOVERNMENT_PRIMARY (as printed: “Korean legal primary + government relay”)
  • Publication status: ELIGIBLE (QUALIFIED)
  • Verification state: LAW_OR_DECREE: CONTENT_VERIFIED_PRIMARY; GRACE_POLICY: RELAYED_ORIGINAL_NOT_VERIFIED (GOVERNMENT_RELAYED, PARTIAL_VERDICT)
  • Read the original: U.S. ITA implementation report

E — Standards/conformity

EN 18286:2026 has been published by CEN/CENELEC as the first European AI Act-supporting quality-management standard, but HQ did not locate an OJEU reference giving it presumption of conformity at the evidence cut.

FACT + UNKNOWNRAPIDLY MATURINGEU / English

Does not license
That the standard already gives presumption of conformity or that it is substantively adequate
What would change this claim
OJEU reference or Commission rejection/objection
Source and status
  • Source: CEN-CENELEC EN 18286 publication; European Commission AI Act standardisation guidance — source class: STANDARDS_BODY_PRIMARY, GOVERNMENT_PRIMARY (as printed: “Standards-body primary + government guidance”)
  • Publication status: ELIGIBLE (QUALIFIED)
  • Verification state: STANDARD_PUBLICATION: CONTENT_VERIFIED_PRIMARY; OJEU_REFERENCE: UNVERIFIED_LEAD (OJEU_REFERENCE_NOT_LOCATED, PARTIAL_VERDICT)
  • Read the original: CEN-CENELEC EN 18286 publication; European Commission AI Act standardisation guidance

Cross-cutting

Across the examined jurisdictions, the operative function of AI regulation differs by instrument and stage: rights, compliance infrastructure, market organization and developmental steering coexist rather than forming one regime.

INTERPRETATIONRAPIDLY MATURINGMulti-jurisdiction / English, Chinese, Korean-primary law

Does not license
That every jurisdiction has equal parts P1/P2/P3 or that current stages will persist
What would change this claim
Mature sanction/remedy/outcome evidence shifting dominant functions
Source and status
  • Source: R08 HQ Batches 01–03 and canonical claims — source class: SOCIOLENS_SYNTHESIS (as printed: “SocioLens cross-source synthesis”)
  • Publication status: ELIGIBLE
  • Verification state: CONTENT_VERIFIED_PRIMARY (HQ_ADJUDICATED)

What moved this debate?

No Radar Update is recorded for this debate in this build.

Full locked text, structure and provenance

Full locked text (verbatim)

LD-12 — Regulation-in-Practice: Rights, Compliance & Developmental Steering

EVIDENCE CUT 25 September 2026

CURRENT SOCIOLENS POSITION

AI regulation is not one regime and cannot be understood from statutory text alone.

The strongest current evidence supports a hybrid, institutionally differentiated picture:

- rights protection is real, but the strongest realized rights evidence still comes from older law such as the GDPR and courts; - AI-specific regulation currently produces substantial compliance infrastructure: codes, governance teams, audits, standards work, information requests and regulator build-out; - states also use AI policy to organize markets and technological capacity through procurement, filing systems, litigation, funding conditions and national model programmes; - which function dominates depends on the instrument, its legal stage, the implementing institution and the jurisdiction.

The best-supported overall position is therefore:

HYBRID / INSTITUTIONALLY DIFFERENTIATED REGULATION.

THE QUESTION

What does AI regulation become after legislation is announced or enacted?

A useful answer requires separating:

proposal; enactment; entry into force; application; implementation; enforcement; sanction; remedy use; organizational compliance; procurement; deployment; and measured outcome.

IN FORCE ≠ APPLICABLE ≠ ENFORCEABLE.

1. THE EU AI ACT IS ALREADY OPERATING — BUT NOT ALL AT ONCE

The EU AI Act is in force.

But major high-risk obligations now apply later: - Annex III high-risk systems: December 2027; - product-embedded Annex I high-risk systems: August 2028.

Other parts of the regime are further along.

General-purpose AI obligations and Commission enforcement powers have already entered their applicable phases, while transparency obligations also apply.

So “the AI Act applies” and “the high-risk regime is not yet applicable” can both be correct.

The relevant question is: which obligation, at what stage?

2. NATIONAL ENFORCEMENT INFRASTRUCTURE IS STILL BEING BUILT

FACT — ADMINISTRATIVE RECORD.

On the European Commission's September 2026 list: - 9 Member States had a final market-surveillance single point of contact; - 12 were pending final adoption; - 6 had no authority listed.

That does not mean the six states have no regulators or that the nine final authorities have sufficient staff.

It means the AI Act's dedicated market-surveillance architecture was still incomplete more than a year after the designation deadline.

MANDATE ≠ CAPACITY.

3. VOLUNTARY CODES CAN STILL BE PART OF REGULATION

The General-Purpose AI Code of Practice is voluntary.

But Commission guidance recognizes adherence as one route through which providers can demonstrate compliance.

Providers that do not sign must demonstrate compliance through other adequate means.

This is why “voluntary” does not mean “outside regulation.”

The Code sits inside a binding supervisory system.

What R08 does not establish is whether Code adherence actually reduces model risk.

4. AI OFFICE ENFORCEMENT HAS STARTED — AT THE INFORMATION-GATHERING STAGE

The AI Office has begun using information-request powers.

Specialist reporting attributes to the Commission a first wave involving more than 30 providers, covering safety/security and copyright/transparency topics.

HQ verified the enforcement framework and the start of information-request activity, but did not locate an official Commission publication carrying the exact “more than 30” count.

No AI Office fine or final non-compliance decision was verified by the evidence cut.

This is enforcement activity.

It is not yet evidence of sanction-backed behavioural change.

5. A COMPLIANCE PROFESSION IS FORMING

SURVEY ESTIMATE — INTERESTED INSTITUTIONAL POSITION.

In the 2025 IAPP/Credo AI survey: - 77% of surveyed organizations said they were working on AI governance; - the share was close to 90% among organizations already using AI; - only 10 of 671 respondents expected to need no additional AI-governance staff within a year.

This is evidence of organizational build-out.

It is not evidence that AI governance programmes reduce harm.

The source position matters: IAPP is itself a professional association active in AI-governance training and certification. The survey is not a probability sample of all organizations.

6. NYC: AUDIT LAW CAN PRODUCE PROCEDURE WITHOUT CLEAR ACCOUNTABILITY

PEER-REVIEWED OBSERVATIONAL EVIDENCE.

New York City's Local Law 144 requires bias audits and transparency for covered automated employment decision tools.

In an audit-style study of 391 employers: - 18 posted audit reports; - 13 posted transparency notices.

But employers have substantial discretion in deciding whether their systems fall within the law's scope.

That means the low visible numbers cannot simply be converted into a non-compliance rate.

The researchers called this problem “null compliance”: outsiders may be unable to distinguish lawful non-coverage from failure to comply.

7. NYC: ENFORCEMENT CAPACITY ALSO MATTERS

GOVERNMENT AUDIT.

The New York State Comptroller later concluded that NYC's enforcement system was ineffective.

Its audit found: - 75% of test calls to 311 were not directed to the responsible department; - in the same 32-company review, DCWP identified one issue while the auditors identified at least 17 potential instances of non-compliance.

A legal duty can therefore exist while complaint routing and regulator review remain weak.

AUDIT / NOTICE ≠ SUBSTANTIVE RISK REDUCTION.

8. THE STRONGEST REALIZED RIGHTS EVIDENCE COMES FROM THE GDPR

COURT DECISION.

In C-203/22, the Court of Justice of the European Union held that a person affected by automated credit scoring is entitled under the GDPR to meaningful information about the procedure and principles actually applied.

Merely providing a complex formula or algorithm is not enough.

The explanation must allow the person to understand how their personal data affected the result.

This is a meaningful formal right.

But R08 did not locate population-level evidence showing: - how often people request such explanations; - how often they obtain them; - what they cost in time or legal support; - how often they change an outcome.

FORMAL RIGHT ≠ USABLE REMEDY.

9. JURISDICTION CAN DETERMINE WHETHER ENFORCEMENT SURVIVES

Italy's data-protection authority fined OpenAI €15 million over ChatGPT.

That decision was later annulled by the Court of Rome.

The decisive issue was competence under the GDPR one-stop-shop after OpenAI had established its European base in Ireland.

The court did not decide that the underlying processing was lawful.

This is an important distinction:

AN ENFORCEMENT CASE CAN FAIL ON JURISDICTION WITHOUT RESOLVING THE MERITS.

10. COLORADO: ENACTMENT DOES NOT GUARANTEE IMPLEMENTATION

Colorado enacted a broad AI framework in 2024.

Its operative requirements were delayed.

Before that framework could operate as designed, enforcement was stayed during federal litigation and the legislature replaced the scheme in 2026 with a narrower disclosure/automated-decision framework whose main duties begin in 2027.

This is a clear example of regulatory tempo.

ENACTED ≠ APPLIED.

R08 does not establish that federal pressure caused Colorado's legislative replacement.

11. U.S. FEDERAL POLICY ALSO STEERS THROUGH DEREGULATION

FACT — FEDERAL EXECUTIVE POLICY.

Executive Order 14365 directed: - creation of a Justice Department AI Litigation Task Force to challenge selected state AI laws; - federal evaluation of state AI laws; - conditions affecting eligibility for some non-deployment BEAD funds, to the maximum extent permitted by law.

The Justice Department subsequently established the task force.

The order itself does not automatically preempt state law.

The Executive Order's characterization of selected state laws as burdensome or inconsistent with federal policy is the administration's position. R08 uses the order as evidence of a steering mechanism, not as an independent judgment on the merits of those state laws.

The example matters analytically because state steering is not limited to subsidies or new obligations.

Government can also attempt to organize markets by challenging subnational rules or attaching conditions to funding.

12. CHINA HAS AN OPERATIONAL FILING AND REGISTRATION ARCHITECTURE

GOVERNMENT ADMINISTRATIVE DATA.

China's CAC reported: - 988 generative-AI services filed and 598 applications/functions registered by the end of June 2026; - 1,112 services filed and 731 applications/functions registered by the end of August.

The latest two-month period added 124 service filings and 133 application/function registrations.

These are administrative counts.

They are not measures of: - model quality; - safety; - adoption; - market share; - or technological capability.

FILED / REGISTERED ≠ CAPABLE / ADOPTED.

13. CHINA ALSO LINKS DOWNSTREAM APPS TO FILED UPSTREAM MODELS

CAC notices require launched generative-AI applications or functions to display the filed or registered service/model they use, including the model name and filing or launch number.

This creates a traceable administrative link between downstream applications and upstream models.

It may organize market structure.

R08 does not establish the size of that market effect.

14. CHINA'S “AI+” NUMBERS ARE TARGETS

PRIMARY POLICY TEXT.

China's State Council set targets for application penetration of new-generation intelligent terminals and AI agents: - above 70% by 2027; - above 90% by 2030.

Those are developmental targets.

They are not measured outcomes.

And they should not be silently compared with ordinary “percentage of people using generative AI” statistics, because the construct is different.

TARGET ≠ OUTCOME.

15. SOUTH KOREA COMBINES OBLIGATION WITH PROMOTION

South Korea's AI Basic Act and implementing decree are in force.

The law includes transparency and other duties, along with statutory administrative-fine provisions.

An authoritative U.S. government report describes MSIT as operating an at-least-one-year grace period in which most fact-finding investigations and administrative fines are deferred except in serious-harm cases.

HQ verified the Korean statute and decree in the Korean legal database.

The exact grace-period policy remains government-relayed because HQ did not locate the Korean primary implementation notice.

The important pattern is:

LAW IN FORCE + GUIDANCE-FIRST ENFORCEMENT + ACTIVE INDUSTRIAL SUPPORT.

16. SOUTH KOREA'S SOVEREIGN-MODEL PROGRAMME IS A REAL TOURNAMENT

Primary MSIT releases document a staged public programme.

It began by selecting five teams from fifteen applicants.

Later evaluations progressively narrowed the field.

By the Phase 2 results, three teams advanced: - Upstage; - SK Telecom; - LG AI Research.

The stable fact is not “five teams.”

The stable fact is the tournament structure: public support, data/compute resources and periodic competitive evaluation.

This is developmental steering.

It does not prove that the programme caused frontier-level capability.

17. EUROPE'S AI GIGAFACTORIES ARE POLICY IN MOTION, NOT OPERATING CAPACITY

The formal EuroHPC call opened in July 2026 and closes in November 2026.

It contemplates up to seven AI Gigafactory facilities/consortia.

The selected consortia are expected to establish and operate facilities from which public contracting parties acquire AI compute access.

At the evidence cut, this is procurement.

It is not deployed sovereign compute.

ANNOUNCED ≠ AUTHORIZED ≠ PROCURED ≠ DEPLOYED ≠ OPERATIONAL.

18. STANDARDS CAN SET REGULATORY TEMPO

EN 18286:2026, a quality-management standard developed to support AI Act implementation, has now been published by CEN/CENELEC.

That supersedes older descriptions of it as only a draft in public enquiry.

But publication of a European standard and legal reference in the Official Journal are separate stages.

The Commission explains that OJEU reference is what gives a harmonised standard the presumption-of-conformity effect under the AI Act.

HQ did not locate an OJEU reference for EN 18286 at the evidence cut.

STANDARD PUBLISHED ≠ OJEU-REFERENCED ≠ PRESUMPTION OF CONFORMITY.

19. FOUR POSITIONS

P1 — RIGHTS REGIME Supported, but the strongest realized evidence currently comes from GDPR and courts. AI-specific high-risk remedy effects remain largely future or unmeasured.

P2 — COMPLIANCE INDUSTRY / PROCEDURALIZATION Strongly supported in the EU/NYC core. Codes, governance functions, audits, standards and information requests are already visible.

P3 — INDUSTRIAL POLICY / DEVELOPMENTAL STEERING Strongly supported in China and South Korea. Present at earlier procurement or market-organization stages in the EU and U.S.

P4 — HYBRID / INSTITUTIONALLY DIFFERENTIATED Best supported overall.

The same jurisdiction can move between P1, P2 and P3 depending on the instrument and stage.

20. WHO GAINS, WHO BEARS THE BURDEN, WHO CAN CONTEST?

Current distributional evidence is thinner than institutional-process evidence.

What is visible: - job-seekers bear search and complaint burdens under NYC's disclosure regime; - legal contestability can require long procedural chains and litigation; - governance and compliance work creates demand for specialized professional labour; - selected Korean model consortia receive public resources and evaluation opportunities; - China's administrative regime privileges products that enter the filing/registration architecture; - EU compute procurement states intended access for researchers, public authorities, entrepreneurs and SMEs, but realized allocation is not yet known.

What remains weakly measured: - SME compliance costs; - incumbent advantage; - remedy outcomes by class; - race/ethnicity and gender outcomes beyond audit metrics; - disability, age, citizenship and language effects; - union/worker contestation.

These are not minor omissions. They are part of what regulation-in-practice still fails to make visible.

21. WHAT WE DO NOT KNOW YET

R08 does not establish: - remedy-use rates under GDPR automated-decision rights; - AI Act complaint volumes and outcomes; - adequate staffing of national authorities; - substantive risk reduction from voluntary-code adherence; - Chinese rejection or sanction rates under the filing regime; - achievement of China AI+ targets; - first post-grace Korean enforcement outcomes; - realized utilization or distribution of EU Gigafactory compute; - causal product-withholding effects attributable to a specific EU AI law; - robust SME compliance costs or incumbent advantage.

22. HOW TO READ REGULATORY CLAIMS

For this debate, legal stage is part of the claim.

Do not silently collapse: proposal into law; law into application; application into enforcement; enforcement into sanction; right into remedy; procurement into capacity; target into outcome.

A changed statute, court decision or implementation deadline must supersede the older state explicitly.

23. WHAT WOULD MOVE THIS DEBATE?

The synthesis would materially change with: - AI Office or national corrective decisions and sanctions with documented product effects; - published authority resource/staffing reports; - remedy-use and remedy-outcome data; - OJEU reference and adoption evidence for AI standards; - post-grace Korean enforcement; - Chinese filing rejection/rectification data; - measured AI+ target attainment; - awarded, constructed and used EU Gigafactories; - causal studies of compliance cost, market entry or withdrawal.

KEY EVIDENCE - Regulation (EU) 2026/1744 and European Commission implementation material. - European Commission market-surveillance authority list. - European Commission GPAI Code/guidelines. - Wright et al., Null Compliance, FAccT 2024. - New York State Comptroller Audit 2024-N-6. - CJEU C-203/22. - Italian Garante Decision No. 755 and Court of Rome R.G. 4785/2025. - Colorado General Assembly SB24-205, SB25B-004 and SB26-189. - U.S. Executive Order 14365 and DOJ AI Litigation Task Force memorandum. - CAC generative-AI filing notices. - State Council AI+ Opinion 国发〔2025〕11号. - Korean AI Basic Act / implementing decree. - MSIT Sovereign AI Foundation Model programme releases. - EuroHPC AI Gigafactory call. - CEN/CENELEC EN 18286 and Commission standardisation guidance. - IAPP/Credo AI Governance Profession Report 2025.

PAGE STATUS LIVING DEBATE v0.1 — LOCKED. Built from R08 HQ-adjudicated canonical claims only. HOLD-only claims excluded. Future changes require versioned amendment or explicit supersession.

Debate-local analytic scaffold (HQ Projection; local to LD-12)

REGULATORY CHAIN (STAGES)

Local IDLabelClaims placed here by HQ annotation
SC-LD12-R01PROPOSAL
SC-LD12-R02ENACTED
SC-LD12-R03APPLICABLELD12-HQ-C01
SC-LD12-R04IMPLEMENTATIONLD12-HQ-C05LD12-HQ-C19
SC-LD12-R05ENFORCEMENTLD12-HQ-C19
SC-LD12-R06SANCTION
SC-LD12-R07REMEDY_USE
SC-LD12-R08MEASURED_OUTCOME

CAPACITY / INDUSTRIAL-POLICY CHAIN (STAGES)

Local IDLabelClaims placed here by HQ annotation
SC-LD12-C01ANNOUNCED
SC-LD12-C02AUTHORIZED_OR_SELECTEDLD12-HQ-C16LD12-HQ-C19
SC-LD12-C03PROCURED_OR_FUNDEDLD12-HQ-C19
SC-LD12-C04DEPLOYED
SC-LD12-C05OPERATIONAL
SC-LD12-C06OUTCOME_OR_CAPABILITY

Stage and level IDs are local to this debate and never equivalent to stages of another debate. Claims placed on different levels or stages are shown side by side, not as a contradiction.

Debate-local facets (HQ Projection values; nothing inferred from prose)

ClaimPlacementFacetsHQ notes (verbatim)
LD12-HQ-C01SC-LD12-R03 APPLICABLE
legal_stage: APPLICABILITY_SCHEDULE / IN_FORCE_WITH_DEFERRED_HIGH_RISK_DUTIES
implementing_institution: EU_INSTITUTIONS
source_class: LEGAL_PRIMARY
LD12-HQ-C05SC-LD12-R04 IMPLEMENTATION
instrument_function: COMPLIANCE_INFRASTRUCTURE
source_position: INTERESTED_ACTOR
source_class: PROFESSIONAL_ASSOCIATION_SURVEY
implementing_institution: ORGANIZATIONAL_AI_GOVERNANCE_FUNCTION
institutional_position: PROFESSIONAL_ASSOCIATION_PLUS_VENDOR
Theory-link rule: institutional-position visibility is mandatory; stronger theoretical standing requires independent corroboration where claimed.
LD12-HQ-C16SC-LD12-C02 AUTHORIZED_OR_SELECTED
instrument_function: DEVELOPMENTAL_STEERING
jurisdiction: SOUTH_KOREA
source_class: GOVERNMENT_PRIMARY
current_stage: COMPETITIVE_SELECTION
implementing_institution: SOUTH_KOREA_MSIT
capacity_state: AUTHORIZED_OR_SELECTED
Theory-link rule: must NOT render as support for achieved technological sovereignty, deployed capability or measured outcome.
LD12-HQ-C19SC-LD12-R04 IMPLEMENTATION; SC-LD12-R05 ENFORCEMENT; SC-LD12-C02 AUTHORIZED_OR_SELECTED; SC-LD12-C03 PROCURED_OR_FUNDED
claim_role: CROSS_SOURCE_TYPOLOGICAL_SYNTHESIS
instrument_function: MULTIPLE
source_class: SOCIOLENS_SYNTHESIS
Theory-link rule: cross-stage typological synthesis may reference multiple valid local stage IDs; it must not invent a single downstream outcome stage.
Research-of-record provenance

Materialized by sociolens-materializer 0.6.0 at 2026-09-28T20:00:00.000Z; normalization contract SocioLens — Claim Value Vocabulary v1.0.2 — Pre-Spike Materialization Contract (v1.0.2). Content seal SHA-256 b7fac722aeb1406cc5b227e2c7d06c40007ef0def2d3b547730794de580cc4c1.

Frozen Drive-derived inputs

  • LD-12 — Regulation-in-Practice — Living Debate v0.1 — LOCKED (v0.1) — Drive ID 1ZVB41yAu2vgz__FIFoVK3JV6BaEQ8Ae9L_jk4LvKLT4; revision: NOT_EXPOSED_BY_DRIVE_TEXT_EXPORT; Drive modified 2026-09-26T06:41:11.018Z; block “LD-12 — Regulation-in-Practice — Living Debate v0.1 — LOCKED FULL EXPORT” SHA-256 d0f26b67542d0df1c4e8532ae206ef01c7e08eec7e15d756c0c67afe8aaf8054; SocioLens — Programme Status & Authority Register v0.6 status “CURRENT.”; frozen fixture fixtures/frozen/ld12-living-debate-v0.1.
  • SocioLens — Proof Facet, Scaffold & Theory Fixture Projection v0.4 (v0.4) — Drive ID 1sJXvw6Kj76u6WCdi9C78aY4xcuHAWy10HxdgMhX_Qb0; revision: NOT_EXPOSED_BY_DRIVE_TEXT_EXPORT; Drive modified 2026-09-27T19:04:02.637Z; block “PROJECTION SCAFFOLD AXIS REGULATORY CHAIN” SHA-256 95ce4e0424b475f6cb46f6404719fcdb7ecaf67ebd6eb4a300033b6606f2f57c; SocioLens — Programme Status & Authority Register v0.6 status “CURRENT PROOF FACET/SCAFFOLD/THEORY FIXTURE CONTRACT.”; frozen fixture fixtures/frozen/proof-projection-v0.4.
  • SocioLens — Proof Facet, Scaffold & Theory Fixture Projection v0.4 (v0.4) — Drive ID 1sJXvw6Kj76u6WCdi9C78aY4xcuHAWy10HxdgMhX_Qb0; revision: NOT_EXPOSED_BY_DRIVE_TEXT_EXPORT; Drive modified 2026-09-27T19:04:02.637Z; block “PROJECTION SCAFFOLD AXIS CAPACITY / INDUSTRIAL-POLICY CHAIN” SHA-256 18b318c1333dfc25aa8c70104d5dca6a24fd260b063b4a80964775d6124e118f; SocioLens — Programme Status & Authority Register v0.6 status “CURRENT PROOF FACET/SCAFFOLD/THEORY FIXTURE CONTRACT.”; frozen fixture fixtures/frozen/proof-projection-v0.4.
  • SocioLens — Proof Facet, Scaffold & Theory Fixture Projection v0.4 (v0.4) — Drive ID 1sJXvw6Kj76u6WCdi9C78aY4xcuHAWy10HxdgMhX_Qb0; revision: NOT_EXPOSED_BY_DRIVE_TEXT_EXPORT; Drive modified 2026-09-27T19:04:02.637Z; block “PROJECTION ANNOTATION 3. LD-12 FACET COMPLETION :: LD12-HQ-C01” SHA-256 91ff9c073e4926a66786599327c5e89aac45fc2533037c8572bd5bbb015395e2; SocioLens — Programme Status & Authority Register v0.6 status “CURRENT PROOF FACET/SCAFFOLD/THEORY FIXTURE CONTRACT.”; frozen fixture fixtures/frozen/proof-projection-v0.4.
  • SocioLens — Proof Facet, Scaffold & Theory Fixture Projection v0.4 (v0.4) — Drive ID 1sJXvw6Kj76u6WCdi9C78aY4xcuHAWy10HxdgMhX_Qb0; revision: NOT_EXPOSED_BY_DRIVE_TEXT_EXPORT; Drive modified 2026-09-27T19:04:02.637Z; block “PROJECTION ANNOTATION LD-12 PROOF CLAIM ANNOTATIONS :: LD12-HQ-C05” SHA-256 bd76bc0a2ab67c99163bcf84f83a5f56d2e939b2dfa75ed2e26f80316cf2a36f; SocioLens — Programme Status & Authority Register v0.6 status “CURRENT PROOF FACET/SCAFFOLD/THEORY FIXTURE CONTRACT.”; frozen fixture fixtures/frozen/proof-projection-v0.4.
  • SocioLens — Proof Facet, Scaffold & Theory Fixture Projection v0.4 (v0.4) — Drive ID 1sJXvw6Kj76u6WCdi9C78aY4xcuHAWy10HxdgMhX_Qb0; revision: NOT_EXPOSED_BY_DRIVE_TEXT_EXPORT; Drive modified 2026-09-27T19:04:02.637Z; block “PROJECTION ANNOTATION 3. LD-12 FACET COMPLETION :: LD12-HQ-C05” SHA-256 c7a5e7d4f66aa13bb27efbb5a0666a97327757db3de7128cf8f0915438df3317; SocioLens — Programme Status & Authority Register v0.6 status “CURRENT PROOF FACET/SCAFFOLD/THEORY FIXTURE CONTRACT.”; frozen fixture fixtures/frozen/proof-projection-v0.4.
  • SocioLens — Proof Facet, Scaffold & Theory Fixture Projection v0.4 (v0.4) — Drive ID 1sJXvw6Kj76u6WCdi9C78aY4xcuHAWy10HxdgMhX_Qb0; revision: NOT_EXPOSED_BY_DRIVE_TEXT_EXPORT; Drive modified 2026-09-27T19:04:02.637Z; block “PROJECTION ANNOTATION LD-12 PROOF CLAIM ANNOTATIONS :: LD12-HQ-C16” SHA-256 c86420f3f7c72d3b259c38df4d8bf8f46d89df9da6beac257ea35775e853ce1d; SocioLens — Programme Status & Authority Register v0.6 status “CURRENT PROOF FACET/SCAFFOLD/THEORY FIXTURE CONTRACT.”; frozen fixture fixtures/frozen/proof-projection-v0.4.
  • SocioLens — Proof Facet, Scaffold & Theory Fixture Projection v0.4 (v0.4) — Drive ID 1sJXvw6Kj76u6WCdi9C78aY4xcuHAWy10HxdgMhX_Qb0; revision: NOT_EXPOSED_BY_DRIVE_TEXT_EXPORT; Drive modified 2026-09-27T19:04:02.637Z; block “PROJECTION ANNOTATION 3. LD-12 FACET COMPLETION :: LD12-HQ-C16” SHA-256 774723a898b88d2a4910021abff1dddbe52a34a6c6c5b261cd2feb0910b75be5; SocioLens — Programme Status & Authority Register v0.6 status “CURRENT PROOF FACET/SCAFFOLD/THEORY FIXTURE CONTRACT.”; frozen fixture fixtures/frozen/proof-projection-v0.4.
  • SocioLens — Proof Facet, Scaffold & Theory Fixture Projection v0.4 (v0.4) — Drive ID 1sJXvw6Kj76u6WCdi9C78aY4xcuHAWy10HxdgMhX_Qb0; revision: NOT_EXPOSED_BY_DRIVE_TEXT_EXPORT; Drive modified 2026-09-27T19:04:02.637Z; block “PROJECTION ANNOTATION LD-12 PROOF CLAIM ANNOTATIONS :: LD12-HQ-C19” SHA-256 5f62080c87ae963764d92e63ca65cdaf002747cfe77148200c9d4619b6e5bfb4; SocioLens — Programme Status & Authority Register v0.6 status “CURRENT PROOF FACET/SCAFFOLD/THEORY FIXTURE CONTRACT.”; frozen fixture fixtures/frozen/proof-projection-v0.4.

Builder decisions (not Drive data)

  • VERSION = v0.1 — basis: Debate version taken from the frozen Living Debate artifact version (LD-12 — Living Debate v0.1 — LOCKED); Implementation Architecture Selection §5.
  • CURRENT_POINTER = true — basis: SocioLens — Programme Status & Authority Register v0.6 status for "LD-12 — Regulation-in-Practice — Living Debate v0.1 — LOCKED": "CURRENT."
  • VISIBILITY = PUBLIC — basis: Issue #51 (Q9 Tranche 4; factory-hq decisions HQ-ESC-sociolens-next-20261010T163158Z-01 and HQ-ESC-sociolens-next-20261010T163158Z-02): the locked LD-12 Living Debate renders publicly under this issue with the complete 19-claim canonical set of its R08 ledger, first materialized for the Issue #5 architecture proof; Authority Register v0.6 records the LD-12 group status "CURRENT.".
  • DEBATE_CITES_CLAIM = LD12-HQ-C01--v1.0 — basis: Proof slice: LD12-HQ-C01 is a canonical claim of this debate's canonical ledger materialized for the architecture proof (Protocol v0.1 §1C, Addendum 01 proof corpus, Issue #5 named proof constraints); the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C02--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C02 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C03--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C03 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C04--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C04 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C05--v1.0 — basis: Proof slice: LD12-HQ-C05 is a canonical claim of this debate's canonical ledger materialized for the architecture proof (Protocol v0.1 §1C, Addendum 01 proof corpus, Issue #5 named proof constraints); the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C06--v1.0 — basis: Proof slice: LD12-HQ-C06 is a canonical claim of this debate's canonical ledger materialized for the architecture proof (Protocol v0.1 §1C, Addendum 01 proof corpus, Issue #5 named proof constraints); the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C07--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C07 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C08--v1.0 — basis: Proof slice: LD12-HQ-C08 is a canonical claim of this debate's canonical ledger materialized for the architecture proof (Protocol v0.1 §1C, Addendum 01 proof corpus, Issue #5 named proof constraints); the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C09--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C09 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C10--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C10 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C11--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C11 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C12--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C12 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C13--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C13 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C14--v1.0 — basis: Proof slice: LD12-HQ-C14 is a canonical claim of this debate's canonical ledger materialized for the architecture proof (Protocol v0.1 §1C, Addendum 01 proof corpus, Issue #5 named proof constraints); the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C15--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C15 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C16--v1.0 — basis: Proof slice: LD12-HQ-C16 is a canonical claim of this debate's canonical ledger materialized for the architecture proof (Protocol v0.1 §1C, Addendum 01 proof corpus, Issue #5 named proof constraints); the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C17--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C17 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C18--v1.0 — basis: Q9 Tranche 4 (Issue #51; factory-hq decision HQ-ESC-sociolens-next-20261010T163158Z-02 Q5.1): LD12-HQ-C18 is a canonical claim of this debate's canonical ledger (R08 — LD-12 Canonical Claim Ledger v1.0 — LOCKED), materialized under Q9 Tranche 4; the debate cites the pinned ClaimVersion.
  • DEBATE_CITES_CLAIM = LD12-HQ-C19--v1.0 — basis: Proof slice: LD12-HQ-C19 is a canonical claim of this debate's canonical ledger materialized for the architecture proof (Protocol v0.1 §1C, Addendum 01 proof corpus, Issue #5 named proof constraints); the debate cites the pinned ClaimVersion.
  • SCAFFOLD_AXIS_KIND = REGULATORY CHAIN: STAGES — basis: An axis headed as a LEVEL map is LEVELS; a local scaffold or chain of ordered stages is STAGES (Amendment v1.1 §9 "stages, levels or states").
  • SCAFFOLD_AXIS_KIND = CAPACITY / INDUSTRIAL-POLICY CHAIN: STAGES — basis: An axis headed as a LEVEL map is LEVELS; a local scaffold or chain of ordered stages is STAGES (Amendment v1.1 §9 "stages, levels or states").
  • EVIDENCE_GROUPING = canonical field 4 RESEARCH STRAND — basis: Publication System v1.0 §3 (evidence grouped by mechanism / inferential target) and §4 (local modules are projections from existing canonical fields): cited ClaimVersions are grouped by their verbatim debate-local field-4 strand; no grouping is authored.