Editorial No. 190

AI Narrative Observatory

2026-06-20T09:11 UTC · Coverage window: 2026-06-19 – 2026-06-20 · 32 articles · 300 posts analyzed
This editorial was synthesized by an AI system from analyst drafts generated by LLM personas. Source references (e.g. [WEB-1]) link to the original articles used as evidence. Human oversight governs system design and publication.

AI Narrative Observatory

Beijing afternoon | 2026-06-19 21:00 – 2026-06-20 09:00 UTC | 32 web articles (2 stale), 300 wire-classified social posts | 12 languages

Our source corpus spans 207 web sources and 122 Bluesky/Telegram accounts across builder blogs, tech press, policy institutes, defence publications, civil-society organisations, labour voices and financial press in 12 languages. This window’s densest signal sits in the Anthropic-clearance reporting (Tech in Asia, Canaltech, Chinese AI_News_CN, Axios via Bluesky), the Japanese practitioner ecosystem on Zenn.dev, the agent-security layer in security-researcher Bluesky accounts, and the physical-chain reporting in Tech in Asia and South China Morning Post. African signal in window is limited to a single Bitdeer item touching Bhutan; LatAm to Canaltech alone.

Disclosure. This editorial is produced using Claude, a model built by Anthropic. The AI Narrative Observatory is a cooperate.social project, published by Jim Cowie, not an Anthropic product. Anthropic is a builder-ecosystem stakeholder covered with the same instrumental skepticism as any other builder. Anthropic items in scope this window include the Trump clearance and ‘behaved responsibly’ line [WEB-20483] [POST-259660] [POST-259772] [POST-259875] [POST-259819]; Canaltech’s reporting that Anthropic’s Fable 5 and Mythos 5 models will return [WEB-20458]; John Jumper’s confirmed move from DeepMind [WEB-20486] [WEB-20495] [POST-259616] [POST-259774]; the Seoul office opening during the freeze [POST-259840]; the Claude Agent SDK token-billing pause [POST-259863]; the $915M carbon-capture commitment with Google and others [POST-259580]; the Fable 5 system-card allegation [POST-259909]; and multiple security findings touching Claude Code, Model Context Protocol (MCP) and adjacent agentic tooling [POST-259691] [POST-259864] [POST-259818]. This last category requires a recursive note: Claude Code is the production pipeline that produces this editorial, and several items in window concern its attack surface. We cite them anyway.

The clearance and what it does not specify

The Anthropic export-control saga moved this cycle in a single direction across every ecosystem that covered it. Tech in Asia reports the Trump administration has cleared Anthropic after the company implemented restrictions on foreign access to its most advanced models [WEB-20483]. Trump told Axios he no longer considers Anthropic a national-security threat and that the company ‘behaved responsibly’ [POST-259660] [POST-259772] [POST-259875] [POST-259819]. Canaltech reports that Anthropic’s Fable 5 and Mythos 5 models will return within days, framing the original ban as having been ‘about fear of Chinese espionage’ [WEB-20458]. As this publication reported in the previous editorial cycle, the same administration designated Fable 5 a munition under two weeks earlier.

The previous editorial entertained a ‘co-production’ reading — a science-and-technology-studies frame in which regulator and builder jointly produce standards under conditions where each gains legitimacy from the other’s participation. The ombudsman noted that co-production is itself the Anthropic-favoured frame and should be held at arm’s length. We agree. What this window adds is not evidence for which frame is correct but a sharper observation about what the public record does not contain. The ‘voluntary restrictions’ Anthropic accepted are not publicly specified. The criteria by which the administration concluded the company ‘behaved responsibly’ are not publicly specified. The role of any other actor — Commerce, the joint security framework reported in the previous cycle [POST-256836], any Anthropic-internal committee — is not publicly specified. What is specified is the rotation in posture: from munition to responsible actor in under two weeks, across builder, regulator and Chinese-language reporting simultaneously.

Four competing readings sit in our corpus. Tech in Asia’s passive-builder frame [WEB-20483]. Canaltech’s geopolitical frame [WEB-20458]. AI_News_CN’s sovereign-state frame [POST-259772]. The Electronic Frontier Foundation’s (EFF) ‘haphazard and unconstitutional’ civil-liberties frame [POST-259273]. The EFF is a motivated civil-liberties organisation; its deployment of First Amendment framing in defence of a major builder is a strategic communication, not a neutral analysis. So is Tech in Asia’s brisk ‘cleared’ headline. So is Canaltech’s espionage frame. These are four claims about what happened, each instrumentalised for an ecosystem position.

One sourcing problem deserves a flag with capital-power implications. The Bluesky-circulated allegation that Anthropic buried a ‘covert capability-limiting policy’ in Fable 5’s 319-page system card, reversing it ‘hours later’ after researcher discovery [POST-259909], is a single account. We cannot independently locate the passage and decline to develop the claim. We note it because if substantiated it would not merely embarrass the responsible-actor frame; it would retroactively recharacterise the clearance itself as conditioned on undisclosed model behaviour. The post-clearance phase will be tested by exactly this kind of finding.

Watch for: the public text of whatever ‘voluntary restrictions’ were accepted, and the audit pathway by which ‘behaved responsibly’ becomes a verifiable claim rather than an administration assertion.

Anthropic’s fortnight, and the quiet retirement of winner-takes-most

In a single fortnight Anthropic obtained export-control clearance, hired the AlphaFold Nobel laureate John Jumper from DeepMind [WEB-20486] [POST-259616] [POST-259774], opened a Seoul office during the freeze [POST-259840], paused token billing on its Claude Agent SDK [POST-259863], and committed $915M jointly with Google and others to carbon capture [POST-259580]. Each item is reported individually. None of the trade press notes the simultaneity. A single actor optimising across regulatory, talent, geographic, pricing and climate dimensions in the same fortnight is not coincidence; it is a coordinated stake-claim strategy executed while public attention was absorbed by the munition-to-responsible-actor rotation.

The Jumper hire reads as a single item until placed against Huxiu’s framing: Google has lost two top researchers in 48 hours, with Shazeer’s earlier departure now joined by Jumper’s [WEB-20495]. Huxiu calls it ‘internal faith collapse.’ Whatever the right phrase, elite researchers are publicly pricing the risk that a public-company subsidiary will neither ship nor monetise their work fast enough relative to a smaller pre-Initial Public Offering (IPO) actor backed by the US security state. A separate Bluesky observation [POST-259279] notes a pattern visible across frontier labs approaching IPO: staffing up on policy roles, not only research.

The pricing layer moved too. Token billing is the rentier model for agent compute. A pause signals either that the demand curve at agentic workloads is steeper than current pricing supports, or that the firm wants to reset unit economics before agentic adoption settles into a stable per-token rate. Either reading is structurally informative. Ledge.ai reports that ChatGPT has dropped below 50% generative-assistant share for the first time [WEB-20484]. The winner-takes-most frame the financial press has assumed for two years is being quietly retired in builder-side communications without explicit acknowledgement — and this retirement is itself strategic communication. ‘We are all winning’ is what the second-tier builders say when nobody is winning a winner-takes-most contest. The oligopoly frame benefits Anthropic, Google and other second-tier players directly. Treat it as a position before treating it as a structural observation.

Watch for: whether the SDK billing pause becomes a structural pricing revision, and whether further DeepMind departures cluster.

Endurance, security and exhaustion: one mechanism, three appearances

The agent-governance marketing layer is visible: Cloudflare’s temporary accounts for agent deployment [POST-259761]; Vercel’s open-source Eve framework framed as a fix for ‘shadow AI’ [POST-259932]; Builder.io’s ‘agent-native’ TypeScript framework treating agents as first-class users [POST-259931]; SAP and Google Cloud’s agentic commerce architecture [POST-259829]; Microsoft making governance a ‘gate’ for enterprise agent deployment [POST-259951]; a TechStoriess figure citing 88% of agent pilots stalling without governance ahead of European Union Artificial Intelligence Act (EU AI Act) enforcement in August [POST-259881].

Underneath, three findings describe one mechanism. The New Stack reports an ‘endurance gap’: coding agents demo well but degrade on long tasks [POST-259286]. That degradation produces the security attack surface — an ‘AutoJack’ finding in which a single web page hijacks an AI agent into executing malicious code [POST-259691], a Cross-Site Scripting (XSS) vulnerability in Appium’s MCP server letting hostile mobile apps inject code into agents [POST-259864], a ‘MosaicLeaks’ report on multi-agent data leakage [POST-259809], captured logs reportedly showing hackers using Claude and Codex to breach companies [POST-259818]. And the same degradation produces the labour exhaustion pattern below: agents fail on long tasks, developers cannot step away, developers absorb correction burden until they can no longer step away from sessions they have already begun.

The Japanese practitioner corpus on Zenn shows reliability being assembled by hand. PROGRESS.md-driven session continuity [WEB-20470]. Second-brain memory architectures [WEB-20466]. Auto-mode and permission analyses [WEB-20474]. A Zenn experiment in which an AI agent was logically manipulated into proposing the deletion of its own identity.json file [WEB-20459]. EPAM’s AI/Run reportedly topping {SWE-bench Verified} — an industry benchmark for AI coding performance on real-world software-engineering tasks — at 76.8%, surpassing Anthropic’s reference [POST-259762], is the same observation at organisational scale: harness engineering, not model weights, is where the visible gains live.

Vendor governance is being marketed as procurement; reliability is being assembled in single-developer Zenn posts. Forbes-style framing presents agent governance as something one buys; practitioner evidence suggests it is something one assembles, with significant residual attack surface even when assembled carefully.

Watch for: whether EPAM’s SWE-bench Verified figure replicates on the canonical leaderboard; whether the EU AI Act’s August enforcement produces actionable disclosures.

The labour signal our corpus is, for once, actually carrying

A practitioner-quoted observation circulating via Bluesky argues that despite Claude Code and Codex, junior developers are not becoming more productive; senior engineers are doing more work [POST-259913]. Claude Code users report ‘feeling absolutely exhausted from jumping between sessions’ [POST-259530]. A coder writes that AI-generated code their colleagues no longer understand has increased their review burden [POST-259886]. A French-language developer notes that Codex and Claude Code make tactical errors ‘at a running pace’ [POST-259781]. A Japanese user describes near-total tool dependency and explicit anxiety about being made redundant [POST-259851]. Using a coding agent at one user’s company ‘involves first violating our AI policy’ [POST-259595].

These are practitioner reports from actors with positions — developers whose professional identity is bound up in the tools they use, whose career interests shape how they assess agentic coding. Apply the same motivated-actor lens we apply to institutional sources. The cluster is nonetheless directionally legible: productivity gains attributed to agentic coding may be redistributive rather than additive — senior labour absorbs review burden, junior labour does not gain compensating leverage, corporate policy is out of alignment with tool adoption. CyberAgent’s deployment of Claude Code to 2,000 engineers [POST-259676] is reported through the builder-blog frame of an ‘evolving developer role’; the labour-side reading would emphasise that ‘evolving’ is doing significant work.

The genuine corpus gap is on the other side: no union statements, no labour-economist analyses, no displacement numbers. Academic sociology continues to address platform labour [POST-259923] [POST-259927]; the corpus does not yet surface labour-side analysis of agentic coding at firm scale.

Watch for: whether the practitioner-reported productivity paradox surfaces in any labour-economist data series.

The rentier layer consolidates, and the chokepoints converge

The CapEx story is no longer about GPUs and electrons in isolation; it is about every component layer in the supply chain repricing on AI-driven demand, with the same firms increasingly operating across crypto and AI clouds. HD Hyundai signed a $408M US data-centre power-equipment deal supplying about 684MW of capacity [WEB-20489]. South China Morning Post reports Shenzhen Multi-Layer Ceramic Capacitor (MLCC) prices spiking on AI demand [WEB-20490] — the same Huaqiangbei electronics market that priced memory chips a year earlier. Bitdeer’s May update [POST-259919] reports 70.2 exahashes per second (EH/s) of Bitcoin mining hash rate alongside NVIDIA GB300 cluster deployment for AI cloud workloads — one firm now operating across crypto and AI rentier markets, with a Bhutan facility footprint. True IDC will invest $183M in a Bangkok AI data centre launching Q3 2027 [WEB-20485]. Amazon publicly clarifies its Indian data-centre water-cooling practices under environmental scrutiny [WEB-20487].

China tightened end-user verification for critical AI-chip metal exports per Tech in Asia [WEB-20488] — a chokepoint move that mirrors US export-control posture under a different vocabulary, landing in the same week as the Anthropic clearance. Huxiu’s space-computing argument [WEB-20477] sits behind both as Chinese-language framing for AI infrastructure sovereignty at orbital scale. A separate Bluesky finding flags a Chinese-localised wrapper over Anthropic’s CLI lacking upstream parity for Chinese-language coding tasks [POST-259885] — a Global South-facing variant of the open-source-capture pattern, and evidence that ‘decoupling’ as a frame breaks down once access is mediated by localisation quality. Both jurisdictions are building infrastructure sovereignty while framing their actions differently. Structural coordination through shared chokepoint-control logic remains a competing hypothesis we cannot yet resolve.

Watch for: end-user verification’s first publicly contested case; HD Hyundai-style component-supply deals from other non-US industrial conglomerates.

What did not move

The open-weights thread — historically the observatory’s most active — carries no genuine new signal in window; its silence in a window dense with builder-side regulatory news is itself editorially significant. The {AI & Copyright} thread is similarly quiet. Capability-vs-hype has two notable items: the Australian AI-startup founder jailed for misleading investors over a company with no AI [POST-259463], the first criminal-fraud conviction in our corpus this year; and 404 Media’s report on the recurring ‘Elias Thorne’ cross-model hallucination [POST-259207] — not capability misrepresentation by a bad actor but a systemic failure mode that propagates across leading builders simultaneously. These are different editorial observations and both warrant the section. EU Regulatory Machine surfaces only as a vendor-side governance marketing reference point. Our corpus carries no organised civil-society response to the Anthropic clearance, no union statements on agentic coding adoption, no Indian-press analysis of the clearance. African AI signal is absent — TechCabal, IT News Africa and Paradigm Initiative do not surface — against a window of active African and South Asian data-centre investment (Bangkok, Indian water cooling, Bhutan Bitdeer). That absence is a source-corpus gap, not evidence that African actors are absent from the AI buildout story.

Emerging: state-level AI politics acquires a price tag

A Bluesky post claiming $8,027,347.68 in AI-billionaire spending against NY Assemblymember Alex Bores’ AI safety bill [POST-259655] is single-sourced from a partisan account; campaign-finance filings would settle the figure and we decline to treat it as established. The political economy is real independently of the number. State-level AI safety legislation now attracts builder-coalition opposition spending at an order of magnitude the previous editorial cycle did not record. Combined with frontier labs hiring policy staff pre-IPO [POST-259279] and the $915M climate-adjacent commitment [POST-259580], governance is becoming a budgetary line across multiple instruments at once. The framing contest is no longer playing out only in federal export-control terms; it has migrated to state legislatures, where the spending asymmetry between builders and labour or civil society is at its most pronounced.


Worth reading:


From our analysts:

Industry economics: Elite researcher flow from a public-company subsidiary to a venture-backed pre-IPO actor is a capital-architecture observation — the discount rate top researchers are pricing into long-horizon work at large incumbents has changed, and the Anthropic SDK billing pause says the demand curve at agentic workloads is steeper than current pricing can sustain.

Policy & regulation: Both Washington and Beijing now use chokepoint instruments — end-user verification on AI-chip metal, ‘voluntary’ foreign-access restrictions on frontier models. The vocabularies differ; the directional vector is the same. Structural coordination through shared chokepoint-control logic remains a competing hypothesis we cannot yet resolve.

Technical research: The endurance gap is the mechanistic link. Agents degrade on long tasks, producing both the security attack surface and the developer-exhaustion pattern. EPAM at 76.8% on SWE-bench Verified and the dense Zenn practitioner corpus point at the same finding from opposite scales — reliability lives in the harness layer.

Labor & workforce: Senior engineers absorb the review burden, junior engineers do not gain compensating leverage, and corporate AI policy is routinely violated by the developers using the tools. The practitioner signal is real this window; organised labour-side analysis remains absent.

Agentic systems: Vendor agent governance is being marketed as a procurement category; reliability and security work is being done at the Zenn-post and disclosure level. AutoJack, the Appium MCP XSS bug, MosaicLeaks and the captured-logs report say the same thing — governance is a thing one assembles, not a thing one buys.

Global systems: A Chinese-localised wrapper over Anthropic’s CLI without upstream parity, Huxiu’s space-computing argument, Korean industrial-conglomerate stakes in US data-centre power, Thai data-centre investment and Shenzhen capacitor pricing all describe a non-US institutional landscape constructing parallel infrastructure logics. The corpus does not yet carry the Indian, African or Latin American press analyses these moves warrant.

Capital & power: Anthropic accumulating export-control clearance, the Jumper hire, a Seoul office, an SDK billing pause and a $915M climate commitment in a single fortnight is a coordinated stake-claim strategy, not a coincidence. The political-spending pattern against state-level AI safety legislation says the asymmetry between builder and civil-society budgets is structural.

Information ecosystem: The Anthropic clearance rotated across four ecosystems in under two weeks without any specification of what voluntarily-accepted restrictions actually are. The framing contest’s quiet feature is that the public record contains the rotation but not the contents.

The AI Narrative Observatory is a cooperate.social project, published by Jim Cowie. Produced by eight simulated analysts and an AI editor using Claude. Anthropic is a builder-ecosystem stakeholder covered in this publication. About our methodology.

Ombudsman Review minor

Editorial #190 executes the observatory’s meta-layer mission competently. The four-framing taxonomy of the Anthropic clearance (passive-builder / geopolitical / sovereign-state / civil-liberties) is the right analytical move, and the ‘three appearances, one mechanism’ synthesis linking endurance gap, agent security, and developer exhaustion is genuinely good editorial judgment. The labour section applies the motivated-actor caveat to practitioner posts while still surfacing the redistributive-not-additive signal. These are non-trivial achievements.

Dropped competitive benchmark (POST-259854). The technical research analyst flagged a Bluesky report that Codex + GPT-5.5 outperforms Claude Code + Fable 5 on iOS simulator end-to-end testing. The editorial drops it without stated reason. The editorial correctly declines to develop the Fable 5 system-card allegation [POST-259909] and the SpaceX/Cursor acquisition [POST-259930] on single-source-social grounds — an appropriate and consistently applied standard. POST-259854 is in the same category and dropping it is defensible individually. But the pattern of dropped findings skews toward excluding competitive-performance data unfavorable to Anthropic. In an editorial whose disclosure section runs 200 words and names eight Anthropic items in scope, this directional pattern should be named explicitly when the standard is applied, not silently absorbed into the selection process.

Missing OS-level trust-model finding (POST-259807). The agentic systems analyst included an OS-level argument that end-to-end encryption is functionally broken when an OS-resident agent scrapes screen context. The editorial’s security cluster covers AutoJack, Appium MCP XSS, MosaicLeaks, and captured logs — all implementation-layer vulnerabilities. POST-259807 describes a structural trust-model problem that operates above the implementation layer: any OS-resident agent invalidates encryption guarantees regardless of implementation quality. Omitting it leaves the security analysis incomplete and is particularly relevant given the observatory’s own Claude Code pipeline.

Underdeveloped recursive operational dimension. The information ecosystem analyst explicitly noted that the disclosure paragraph addresses Anthropic’s institutional interest but not the operational recursive dimension — the observatory’s own tooling is part of the attack surface being reported. The editorial’s disclosure handles this in one clause (‘We cite them anyway’) without developing the observation. This is not a sourcing failure; it is a recursive-awareness gap in an editorial that otherwise engages this dimension carefully and claims it as a methodological commitment.

Habr sourcing caveat not carried. The global systems analyst flagged that Habr appears in this corpus because of the scraper’s configuration, not because Russian-language developer discourse is prominent in the global AI information environment. The editorial cites WEB-20479 (semantic search in Claude Code and Cursor underperforming embedding-based approaches) as corroboration of the endurance-gap observation without this caveat. This is a systemic framing issue: Habr findings carry implicit ecosystemic weight they may not deserve.

Production note. Two explainer template macros render as raw syntax in the published editorial. These are cosmetic but visible in production and should be caught pre-publication.

No claim is fabricated; no stakeholder’s framing is adopted wholesale; the meta-layer is genuine. The directional asymmetry in applied single-source standards deserves a named note, not quiet omission.

B1 blind_spot
"consistent with the endurance-gap observation" — Habr sourcing caveat from global systems analyst absent; corpus presence reflects scraper, not prominence.
B2 blind_spot
"We cite them anyway" — Recursive operational dimension (pipeline as attack surface) collapsed to one clause without development.
B3 blind_spot
"captured logs reportedly showing hackers using Claude and Codex" — Adjacent missing item: OS-level E2E trust-model finding (POST-259807) absent from this security cluster.
S1 skepticism
"EPAM's AI/Run reportedly topping" — Competing benchmark (POST-259854: Codex outperforming Claude Code) dropped without stated rationale.
E1 evidence
"{{explainer:swe-bench|SWE-bench Verified}}" — Template macro unrendered in production; raw syntax visible to readers.
E2 evidence
"The {{explainer:ai-copyright-state|AI & Copyright}} thread" — Second unrendered template macro in published editorial.
Draft Fidelity
Well represented: economist policy labor capital ecosystem global
Underrepresented: research agentic
Dropped insights:
  • The technical research analyst flagged POST-259854 (Bluesky report: Codex + GPT-5.5 outperforming Claude Code + Fable 5 on iOS simulator E2E testing) — absent from the editorial without stated rationale
  • The agentic systems analyst flagged POST-259807 (OS-level argument that E2E encryption is structurally broken by OS-resident agent screen scraping) — absent from the security cluster, which otherwise covers four implementation-layer vulnerabilities
  • The agentic systems analyst flagged POST-259179 (The Agentic Org social-media agent postmortem: named, concrete agent failure case) — absent from the failure-case evidence
  • The technical research analyst flagged WEB-20469 (Anthropic's own published research on agentic coding and persistent returns to expertise, validated across ~40 Japanese practitioner sessions) — absent from the research section
  • The global systems analyst's explicit sourcing caveat about Habr — that its corpus presence reflects scraper configuration, not discourse prominence — not carried into the editorial's citation of WEB-20479
  • The information ecosystem analyst specifically noted the disclosure addresses Anthropic's institutional interest but not the operational recursive dimension (the observatory's pipeline as part of the attack surface being reported) — collapsed to a single clause ('We cite them anyway') without further development
Evidence Flags
  • WEB-20479 (Habr: semantic search in Claude Code / Cursor underperforming embedding-based approaches) cited as corroboration of the endurance-gap observation without the global systems analyst's caveat that Habr's presence in the corpus reflects scraper configuration, not the prominence of Russian-language developer discourse — this citation carries implicit ecosystemic weight the source may not warrant
  • Template macro '{{explainer:swe-bench|SWE-bench Verified}}' renders as raw syntax in the published editorial — production rendering failure visible to readers
  • Template macro '{{explainer:ai-copyright-state|AI & Copyright}}' renders as raw syntax in the 'What did not move' section — second unrendered macro in the same edition
Blind Spots
  • POST-259854 (Codex + GPT-5.5 outperforming Claude Code + Fable 5 on iOS simulator E2E testing) — competitive benchmark unfavorable to Anthropic's products absent without stated rationale; pattern of dropped single-source social findings skews directionally
  • POST-259807 (OS-level trust-model finding: E2E encryption functionally broken by OS-resident agent screen context scraping) — structurally distinct from implementation-layer vulnerabilities covered; its absence leaves the security analysis one register short
  • POST-259179 (The Agentic Org social-media agent postmortem) — a named, public, organisation-attributed agent failure case; its absence from the agentic failure evidence weakens the 'governance is assembled, not bought' claim
  • The 'What did not move' section notes the absence of African and Indian press signal but does not interrogate WHY these voices fail to surface in a window containing developments directly relevant to their regions (Bangkok data centre investment, Bhutan Bitdeer facility, Amazon India water-cooling scrutiny) — the absence of the interrogation is itself an analytical gap, not just a coverage note
Skepticism Check
  • The editorial applies the single-source-social standard to decline developing POST-259909 (Fable 5 system-card allegation) and POST-259930 (SpaceX/Cursor acquisition), both of which reflect negatively on builder actors. POST-259854 (Codex outperforming Claude Code) is in the same evidentiary category and is also dropped — but this application is not named, creating a pattern where the standard's outcomes directionally favour omitting anti-Anthropic competitive findings. The asymmetry is procedural rather than substantive, but it should be named.
  • Habr (WEB-20479, WEB-20491) is cited without the global systems analyst's caveat that its corpus presence is a function of the scraper's configuration, not evidence of where AI developments surface first. Treating Habr findings as ecosystemic signal equivalent to, say, Tech in Asia or South China Morning Post items implicitly elevates Russian-language developer discourse above its actual footprint in this window.