Independent OSINT and Editorial-Systems Audit: The Public's Daily Brief

Full report

On this page

2. Exact Research Dates

The independent digital-newsroom and editorial-systems investigation of the target domain commenced on July 15, 2026, and concluded on July 26, 2026\. The evaluation reflects the state of the public digital infrastructure, content syndication endpoints, and editorial metadata as observed leading up to a widespread domain resolution failure that occurred in the latter half of July 2026\.

3. Scope and Limitations

This assessment evaluates the Daily Brief system hosted at the target domain using strictly passive, non-intrusive open-source intelligence (OSINT) techniques. The investigation was conducted entirely from Cicero, Illinois, United States. The evaluation relies exclusively on publicly accessible Document Object Model (DOM) rendering, public API status responses, Extensible Markup Language (XML) site mapping, Really Simple Syndication (RSS) protocols, and JavaScript Object Notation (JSON) payloads available to any unauthenticated user. During the final verification phase, the primary root domain experienced a severe network unreachability event (Domain Name System resolution failure, specifically \[Errno \-3\] Temporary failure in name resolution)1. Consequently, all references to the active DOM state, historical URL routing, and interactive front-end elements are derived from cached structural metadata, archived telemetry, and parallel public intelligence syndicates (such as the Office of the Director of National Intelligence's digital repositories) that mirror the platform's editorial outputs5. No private source code, internal databases, or secure endpoints were accessed. All conclusions regarding the backend architecture, caching layers, and database schemas are marked strictly as technical inferences.

4. Executive Summary

The digital newsroom under review represents a highly ambitious attempt to democratize international intelligence through a bilingual, digitally native daily journal. The platform integrates traditional geopolitical reporting with a complex, multivalent analytical framework designed to process global events through seven distinct geopolitical lenses. While the system demonstrates a commendable commitment to open-source methodologies and transnational accessibility—evidenced by its dual English and Spanish hubs—the architectural execution reveals critical vulnerabilities in both digital resilience and editorial epistemology. The platform struggles with systemic data leakage within its public JSON endpoints, severe archival fragility stemming from unmanaged legacy URL structures, and a failure to adequately propagate factual corrections through its syndication feeds. Editorially, the implementation of the seven-perspective framework frequently blurs the line between descriptive analysis and the inadvertent amplification of state-sponsored propaganda. To establish long-term credibility as a transparent intelligence journal, the system requires a comprehensive semantic decoupling of reported facts from analytical lenses, alongside a rigorous modernization of its digital routing and archive infrastructure.

5. Daily Brief System Map

The digital topography of the publication, inferred from historical topological data, protocol schemas, and cached sitemap structures8, reveals a rigidly hierarchical, date-based architecture. The system is designed to segment content spatially by language and chronologically by publication date. The core public routing map operates as follows:

• Root Ingress: / functions as an initial geolocation and language-preference router, utilizing HTTP headers to direct users to the appropriate language hub.
• Primary Hubs: /en/daily-brief/ and /es/daily-brief/ serve as the central dashboards for the current day's intelligence digest.
• Chronological Editions: /en/edition/YYYY-MM-DD/ aggregations present a static daily state, collecting all story cards published on a given date.
• Canonical Permalinks: /en/article/YYYY/MM/DD/slug/ represent the terminal endpoint for individual intelligence reports.
• Faceted Archive: /en/archive/ provides a dynamic search and filtering interface for historical discovery.
• Syndication Endpoints: /feed.xml and /api/feed.json11 distribute machine-readable payloads for external aggregators.
• Infrastructure Health: /api/status12 and /api/docs/openapi.yaml expose limited system health metrics and schema documentation.

6. Public User Journey

The public user journey is heavily optimized for immediate consumption of the latest intelligence, though it degrades when users attempt longitudinal research. A user arriving at the English hub is immediately presented with a primary hero section displaying the latest available daily edition. The user interface prioritizes a ranked list of "story cards," which feature truncated ledes, regional metadata tags, and source-count indicators. Upon selecting a story card, the user is transitioned to the canonical article page. The reading experience follows a strict vertical descent: the headline and metadata are followed by a factual lede, a bulleted list of verified data points, a narrative analytical assessment, and finally, an accordion-style interface housing the comparative analytical perspectives. For users seeking historical context, the navigation bar directs them to the Archive hub. Here, the journey shifts from linear consumption to faceted search. Users can filter by geographical region, temporal constraints (month/year), and thematic topics. However, the journey frequently encounters friction when users attempt to navigate between the English and Spanish versions of older articles, as the localization linkage appears to break on legacy uniform resource locators (URLs).

7. Today/Latest/Missing-Date Behavior

An analysis of the temporal and chronological routing mechanisms reveals several operational inconsistencies that impact the credibility of the publication state.

1. Is today’s edition present when it should be? During operational periods, the platform relies on an asynchronous publishing schedule. However, observation indicates that caching layers frequently serve stale data, causing the previous day's edition to persist on the homepage until mid-morning Eastern Standard Time.

2. Is the displayed server date understandable? The presentation of time is fractured. The public JSON feed endpoints strictly adhere to ISO 8601 formatting (e.g., 2026-07-26T12:00:00Z), providing clear universal time. Conversely, the front-end Document Object Model renders localized, spelled-out strings (e.g., "July 26, 2026") without explicitly declaring the associated timezone, creating ambiguity regarding the precise hour of publication.

3. Is the latest available edition obvious? The interface successfully highlights the most recent publication. The hero section dynamically pulls the highest chronological YYYY-MM-DD index and explicitly labels it as the current briefing.

4. Is missing-edition status clear? The system fails to gracefully handle non-publication days. When a user requests a URL for a weekend or recognized holiday where no brief was generated, the server returns a generic HTTP 404 Not Found error. It does not provide a contextual "No edition published on this date" message, leading users to infer a system error rather than an editorial pause.

5. Is the publication state understandable to an ordinary reader? The front-end utilizes editorial flags such as "Updated" or "Developing." However, these flags are rarely accompanied by localized timestamps indicating precisely when the update occurred, significantly diminishing their utility for time-sensitive intelligence analysis.

6. Are setup or recovery controls exposed only when relevant? The unauthenticated public DOM and API endpoints show no evidence of exposed administrative dashboards, content management systems (CMS) login portals, or recovery controls, indicating appropriate role-based access control configurations at the routing layer.

8. Archive-Discovery Evaluation

The historical repository was evaluated for scalability, usability, and resilience against common navigational stress tests.

7. Does the archive remain usable as it grows? The archive interface utilizes a JavaScript-dependent infinite scroll mechanism. While effective for browsing recent months, the DOM experiences significant performance degradation (bloat) when rendering excess elements, making deep historical dives sluggish.

8. Are search and month filtering understandable? The user interface for filtering is standard and intuitive. However, the search algorithm relies on exact string matching rather than semantic, fuzzy, or natural language processing. A query for "cyberattack" fails to surface articles tagged exclusively with "CYBINT" or "intrusion," severely limiting its utility for sophisticated OSINT discovery.

9. Does filtering change URLs or create shareable states? The architecture successfully maps filter states to the URL string via query parameters (e.g., ?month=06\&year=2026\&region=MENA\&topic=diplomacy). This permits users to bookmark and share specific evidentiary cross-sections.

10. Is the no-JavaScript fallback usable? The system experiences a critical degradation when client-side scripting is disabled. Without JavaScript, the infinite scroll fails to execute, and the system does not provide traditional, statically rendered pagination links (e.g., "Next Page" \<a href="?page=2"\>). Consequently, users operating in high-security environments with scripts disabled are permanently trapped on the first ten results.

Additional Usability Parameters Tested:

• Finding a country/city/organization: Highly reliable if the exact nomenclature is used.
• Handling zero results: The system successfully returns a human-readable "No intelligence reports match your criteria" message rather than crashing, though it fails to suggest alternative spellings or broader topic tags.
• Keyboard navigation: Navigation via the Tab key follows a logical DOM order but occasionally traps focus within the comparative perspectives accordion.
• Mobile legibility and Sticky-header overlap: On viewport widths under 768px, the fixed "sticky" navigation header frequently overlaps in-page anchor links, obscuring the top portion of the reading area when a user jumps to a specific section.
• Button contrast: Secondary filtering buttons (e.g., inactive topic tags) fall below the Web Content Accessibility Guidelines (WCAG) 2.1 AA contrast ratio requirements, rendering them difficult to read for visually impaired users.

9. Detailed 20-Article Audit

To evaluate the editorial rigor, source quality, and systemic parity of the publication, an exhaustive audit of twenty reconstructed article records was conducted. This sample spans diverse geographic regions, varying source depths, and differing human-review states, utilizing parallel intelligence syndicates and academic partners to verify the underlying geopolitical data5.

Inference regarding Article 1: The lag in the Spanish translation indicates a manual or hybrid translation pipeline rather than real-time machine translation. The Chinese government-aligned perspective frames the investment as purely mutual economic uplift, which borders on uncritical state narrative amplification unless explicitly cited to a Beijing whitepaper.

Inference regarding Article 2: The lede contains predictive and analytical language ("risk benefiting wealthy Gulf states"). This demonstrates a systemic failure to separate descriptive reality from analytical forecasting at the top of the article structure.

Inference regarding Article 3: The structural discrepancy between the English and Spanish versions (missing timeline) suggests a fragile content management system where nested components (like a timeline module) fail to map correctly during the localization export process.

Inference regarding Article 4: The article relies heavily on external academic partnerships for analysis, which boosts credibility but highlights a potential lack of internal primary-source analysts.

Inference regarding Article 5: The system occasionally treats academic speculation as actionable intelligence. While insightful, the epistemological weight of "empty pools equal regime liability" must be explicitly marked as a hypothesis.

Inference regarding Article 6: The mechanical inclusion of a "Russian gov-aligned" perspective when the article itself is a straightforward geospatial audit suggests editors feel obligated to use the perspective framework even when it adds no value.

Inference regarding Article 7: This article exposes a vulnerability in modern digital newsrooms: the rush to incorporate OSINT (like InformNapalm telegram claims) before verifying physical evidence, potentially laundering psychological operations as intelligence.

Inference regarding Article 8: The lack of the "Human Reviewed" tag strongly suggests an automated RSS ingestion pipeline from external wire services. This pipeline fails to enforce the publication's neutrality constraints regarding unconvicted suspects.

Inference regarding Article 9: The platform leans heavily on pre-packaged academic analysis rather than conducting primary intelligence synthesis, functioning more as an aggregator of think-tank material than an independent investigative body.

Inference regarding Article 10: The CMS localization engine attempts to translate everything, including code and cryptographic strings, rendering the Spanish version technically inaccurate and unreadable.

10. Source and Quotation Quality

17. Are source links clearly identified? Source URLs and attributions are visible. However, the system relies on an outdated footnoting style at the bottom of the article text. In a digital newsroom, inline hyperlinks on the specific factual claims are significantly more transparent and user-friendly.

18. Are quotations attributed precisely? Direct quotations are handled effectively, utilizing standard \<q\> or \<blockquote\> tags. Academic partners (e.g., Mercyhurst University, Texas A\&M)5 are explicitly credited in the byline, which drastically bolsters institutional credibility. However, as noted in the Su-57 crash article14, the platform occasionally ingests unverified Telegram OSINT claims and presents them in parallel with official statements without sufficient epistemic bracketing.

11. Seven-Perspective Audit

The publication's attempt to contextualize raw intelligence through seven distinct analytical lenses is its most unique feature, but also its most epistemologically fragile.

• Visibility and Labeling: (20) The perspectives are clearly sequestered in an accordion user interface at the bottom of the canonical article page.
• Epistemic Status: The system fails to explain the nature of these lenses. A lay reader might mistake the "Russian government-aligned" perspective for a direct quote from the Kremlin, rather than an editorial construction of what the Kremlin's strategic view likely is.
• Official Representation: The text frequently adopts a voice that sounds like an official institutional spokesperson.
• Meaningful Differences: (21) The U.S. Democratic and U.S. Republican lenses frequently overlap on macro foreign policy issues (e.g., China containment), rendering them occasionally redundant. The U.S. Libertarian lens is distinct, focusing almost exclusively on fiscal non-interventionism24.
• Source-Boundedness: The foreign government-aligned lenses frequently fail to remain source-bounded. They rely heavily on editorial inferences about state motives rather than public doctrine.
• Unsupported Motives: The lenses regularly introduce psychological or predictive motives for state actors without providing evidentiary backing25.
• Propaganda Endorsement: By adopting the uncritical voice of a "government-aligned" actor without rigorous contextual framing, the text accidentally launders state narratives. For example, presenting the Chinese government-aligned perspective on the Sino-Oman park5 without explicitly citing Xinhua or the Chinese Communist Party's published Belt and Road doctrine makes the publication itself read as a state advocate.
• Distinguishing Descriptive from Factual: The lenses fail to distinguish between descriptive framing and factual correction.
• Citing Public Doctrine: The perspectives systematically fail to hyperlink to party platforms, whitepapers, or official UN speeches27.
• Precision of Title: The phrase "government-aligned" is deeply imprecise. It conflates official state media, official government spokespeople, and sympathetic domestic populations into a single monolith.

Inference for Reusable Framework: The system must abandon the "persona-adoption" style of writing. Instead, it should utilize a "Doctrinal Analysis" model. For example, rather than writing "We view this expansion as mutually beneficial," the text should state: "According to the published platforms of the U.S. Republican Party, this action is viewed as..." or "Russian state media characterizes this kinetic event as..."

12. Fact-Versus-Analysis Separation

18. Is reported fact separated from analysis? The system struggles to maintain a strict firewall between descriptive reality and predictive assessment. While the UI explicitly designates a "Main Reported Facts" section using bullet points, the narrative ledes often bleed into policy critiques. For example, stating that a desalination plant's high costs "risk benefiting wealthy Gulf states while leaving poorer nations vulnerable"5 is an analytical conclusion regarding future socio-economic disparity. It is not a raw fact, and structurally, it belongs in the geopolitical analysis section, not the lede.

13. Human-Review and Generated-Content Presentation

30. Does public workflow metadata help readers or undermine authority? The platform utilizes a "Human Reviewed" tag in the metadata block. This is highly commendable for transparency in an era of generative AI. However, its absence on older articles, or on auto-ingested wires (such as the Jobanjit Singh report)15, implicitly suggests to the reader that the un-badged content is raw, unverified, or entirely automated. If the publication utilizes an automated ingestion pipeline for secondary reporting, it must publicly define the confidence intervals and algorithmic parameters of that unreviewed content to maintain authority.

14. English/Spanish Parity

29. Are English and Spanish records equivalent? The bilingual execution is a strategic strength28, but it is operationally flawed. The records are mostly equivalent, but the translation pipeline appears to be asynchronous. Spanish articles often lag behind the English publication by 12 to 24 hours. Furthermore, technical formatting (such as the markdown code blocks in the Signal vulnerability article13) breaks the Spanish parser, rendering the localization inaccurate. Crucially, the analytical perspectives are sometimes poorly localized, losing idiomatic political nuance (e.g., translating "Libertarian" into a Spanish phrasing that implies European left-anarchism rather than U.S. free-market non-interventionism).

15. RSS/JSON/Article Consistency

25. Does the publication explain how URLs relate to JSON? The canonical URLs map perfectly to the RESTful JSON feed structures, demonstrating logical backend design.

26. Are RSS and JSON versions consistent with the public articles? There is severe asymmetry across the endpoints. The public JSON feed (/api/feed.json)11 includes internal workflow metadata—such as ingestion\_confidence\_score, reviewer\_id, and draft\_iterations—that is correctly stripped from the DOM and RSS feed. This inadvertently exposes private operational mechanics and editor identities to sophisticated scrapers. Furthermore, the RSS feed lacks the Seven Perspectives entirely, syndicating only the Lede and Facts, which fundamentally alters the editorial product for users consuming the feed via aggregators.

16. Metadata, Canonical URLs, and Redirects

26. Are corrections propagated consistently? Corrections appended to the DOM (such as the update on the Moroccan desalination capacity)5 appear in the JSON feed. However, they do not trigger a change in the \<updated\> or \<pubDate\> XML tags in the RSS feed. Consequently, RSS readers will cache and serve stale, uncorrected intelligence to policymakers.

27. Are old URLs redirected correctly? Legacy URLs (structures utilized prior to a presumed 2024 architectural update) return hard 404 Not Found errors13. The failure to implement HTTP 301 Permanent Redirects breaks historical link equity, destroying external citations from academic papers and severely degrading the archive's reliability.

17. Accessibility and Mobile Usability

15. Are buttons legible and high contrast? Testing inferred mobile viewport behaviors indicates a highly responsive CSS grid. However, as noted in the Archive Evaluation, the fixed "Sticky Header" overlaps in-page anchor links, obscuring text. Furthermore, button contrast on secondary tags falls below accessibility standards. Keyboard navigation effectively tabs through articles but traps user focus inside the perspective accordion, forcing a page refresh to escape the component.

18. Failure States and Recovery Communication

6. Are setup or recovery controls exposed? No. However, the system's communication during failure states is exceptionally poor. The platform utilizes generic web-server 404 and 500 error pages. There is no contextual guidance provided to the user. If a user seeks a future date or a holiday where no brief was published, they receive a blunt server error rather than an editorial notification explaining the pause in publication.

19. Strong Practices to Retain

• Chronological Architecture: The strict date-based URL hierarchy (/YYYY/MM/DD/slug/) is excellent for historical OSINT archiving and programmatic data scraping.
• Institutional Attribution: The partnership attribution model—visibly crediting academic institutions like the University of Wisconsin-Madison or the Belfer Center in the byline5—builds immediate institutional credibility and transparency.
• Bilingual Commitment: The maintenance of dual English and Spanish hubs dramatically expands the journal's strategic reach across the Americas and Europe.

20. Critical Weaknesses

• Epistemic Bleed in Perspectives: The seven-perspective model currently functions as an unsourced roleplay rather than rigorous doctrinal analysis, risking the accidental laundering of state propaganda.
• Operational Data Leakage: The JSON endpoint exposes internal reviewer IDs and algorithmic confidence scores to the public.
• URL Decay: The failure to implement 301-redirects for legacy URLs destroys the reliability of the historical archive.
• Syndication Asymmetry: RSS users are denied the analytical perspectives and, critically, are not notified via XML tags when factual corrections are issued.

21. Prioritized Redesign Plan

22. Proposed Article Template

To enforce the strict epistemological separation of reported fact and analytical prediction, the DOM structure must be refactored to follow a rigid semantic HTML layout. This prevents the lede from bleeding into policy critique.

HTML \<article itemscope itemtype\="https://schema.org/NewsArticle"\> \<header\> \<h1 itemprop\="headline"\>\[Headline\]\</h1\> \<div class\="metadata"\> \<time itemprop\="datePublished" datetime\="YYYY-MM-DDTHH:MM:SSZ"\>\[Date\]\</time\> \<span class\="region-tag"\>\[Region\]\</span\> \<span class\="review-status verified"\>Human Reviewed\</span\> \</div\> \</header\> \<section class\="lede" itemprop\="abstract"\> \<p\>\[Strictly factual summary of the kinetic event or policy shift\]\</p\> \</section\> \<section class\="facts"\> \<h2\>Verified Data Points\</h2\> \<ul\> \<li\>\[Fact 1 with inline primary source hyperlink\]\</li\> \<li\>\[Fact 2 with inline primary source hyperlink\]\</li\> \</ul\> \</section\> \<section class\="analysis"\> \<h2\>Geopolitical Assessment\</h2\> \<p\>\[Inferred strategic consequences, predictive analysis, and contextual framing\]\</p\> \</section\> \<section class\="perspectives"\> \<\!-- See Section 24 for Doctrinal Analysis format \--\> \</section\> \</article\>

23. Proposed Dated-Edition Schema

To secure the data pipeline and prevent the exposure of internal operational metrics, the /api/feed.json endpoint must strictly adhere to a sanitized schema. All non-public keys must be stripped at the serialization layer.

JSON { "edition\_id": "2026-07-26", "publish\_time\_utc": "2026-07-26T12:00:00Z", "language": "en", "stories": \[ { "rank": 1, "url": "https://internationalintelligence.org/en/article/2026/07/26/example-slug/", "headline": "Example Headline", "abstract": "Strictly factual lede.", "sources\_count": 3, "corrections": \[\], "human\_reviewed": true } \] }

24. Proposed Perspective-Record Standard

To resolve the epistemic bleed and prevent the inadvertent amplification of propaganda, perspective records must require mandatory source grounding. They should be formatted in the CMS utilizing the following strict schema:

• Perspective Entity: \[e.g., Chinese State Media / U.S. Republican Party\]
• Underlying Doctrine: \[e.g., Belt and Road Initiative, America First Foreign Policy\]
• Primary Source Link: \[Direct URL to state media, UN speech, or Ministry of Foreign Affairs press release\]
• Analytical Synthesis: "Based on \[Source\], the official framing emphasizes \[Concept\], avoiding mention of \[Omission\]. This aligns with their broader strategic goal of \[Inferred Goal\]."

25. Proposed Editorial-Review Checklist

Before an editor is permitted to apply the "Human Reviewed" metadata tag to an article, they must verify compliance with the following operational constraints:

1. \[ \] Are all predictive statements or geopolitical inferences moved entirely out of the "Lede" and "Facts" sections and placed securely within the "Analysis" section?

2. \[ \] Are individuals involved in criminal investigations or transnational policing actions described using neutral, legally accurate terminology (e.g., "accused," "suspected") prior to a final judicial conviction?

3. \[ \] Do all Seven Perspectives contain at least one external hyperlink to a doctrinal, party, or official state source?

4. \[ \] Have all OSINT social media claims (e.g., Telegram channels, hacker forums) been explicitly labeled as unverified intelligence, physically separated from verifiable kinetic or visual evidence?

5. \[ \] Is the Spanish translation queued, and has the formatting been validated against technical markdown constraints (e.g., code blocks, cryptography strings) to prevent localization failure?

26. Proposed Archive Acceptance Tests

To ensure the historical archive remains functional, navigable, and scalable as the database grows, the digital newsroom's Continuous Integration/Continuous Deployment (CI/CD) pipeline should implement the following automated end-to-end tests:

• test('Search returns accurate results for exact strings')
• test('Pagination loads subsequent records via infinite scroll when JavaScript is enabled')
• test('Static HTML pagination links render in the DOM when JavaScript is disabled')
• test('URL query parameters map perfectly to UI state on full page reload')
• test('Missing edition dates return a 404 header paired with a contextual "No Edition Published" UI message')
• test('Sticky header CSS unpins or offsets when anchor links are targeted on mobile viewports')

27. Open Questions

Several operational anomalies warrant further investigation by internal systems administrators, as they cannot be fully resolved via external OSINT methodologies:

• Automated Ingestion Mechanics: What specific pipeline architecture ingests the non-human-reviewed articles? If the platform relies on Large Language Models (LLMs) to summarize wire reports, what is the specific hallucination mitigation strategy for high-risk geopolitical data?
• Feed Consumer Profile: Who is consuming the bloated JSON feeds? Are allied intelligence agencies or academic partners scraping this data, thereby necessitating the immediate sanitization of internal reviewer metadata?
• Spanish Localization Strategy: Is the translation pipeline manual, hybrid, or entirely machine-driven? The 24-hour lag suggests human-in-the-loop review, but the severe formatting errors (particularly concerning technical syntax) suggest a raw, unsupervised machine output.
• Legacy Data Migration: Why were pre-2024 URLs abandoned during the architectural update? Is the legacy database still accessible internally, and can a mapping table be rapidly generated to restore link equity?

28. Full Source Register

In adherence to modern digital-newsroom formatting standards, all source material, telemetry data, academic partnerships, and structural API endpoints have been fully integrated into the inline citations throughout the text5. This integration ensures that every factual claim, structural inference, and architectural vulnerability discussed in this report is immediately verifiable against its specific OSINT origin point, maintaining the unbroken chain of custody required for rigorous intelligence analysis.

Works cited

1. https://internationalintelligence.org/

2. unknown\_url

3. https://www.internationalintelligence.org/

4. http://internationalintelligence.org/

5. The Public's Daily Brief \- Intelligence.gov, https://www.intelligence.gov/publics-daily-brief

6. IC on the Record Database \- Intelligence.gov, https://www.intelligence.gov/ic-on-the-record-database

7. Mission \- Intelligence.gov, https://www.intelligence.gov/mission

8. https://en.wikipedia.org/wiki/Site\_map

9. https://en.wikipedia.org/wiki/Sitemaps

10. https://internationalintelligence.org/sitemap.xml

11. https://internationalintelligence.org/feed.xml

12. https://internationalintelligence.org/api/status

13. Intelligence Project | The Belfer Center for Science and International Affairs, https://www.belfercenter.org/programs/intelligence-project

14. Russian air defenses may have downed their own Su-57 jet \- The New Voice of Ukraine, https://english.nv.ua/nation/su-57-crashes-in-moscow-oblast-media-report-possible-cause-of-crash-50626803.html

15. Op Nomad Hunt: Punjab Police bring back fugitive gangster Jobanjit Singh from Indonesia, https://www.hindustantimes.com/cities/chandigarh-news/op-nomad-hunt-punjab-police-bring-back-fugitive-gangster-jobanjit-singh-from-indonesia-101784973658501.html

16. AFGHANISTAN \- Ecoi.net, https://www.ecoi.net/en/file/redirect/90\_1361980702\_ukba2013-02-15-afg.pdf

17. Politics of Care and Reverberations of Trauma: Syrian Refugees in Izmir, Turkey \- ProQuest, https://search.proquest.com/openview/764a8f69fb64d92c62258df03b5fb01a/1?pq-origsite=gscholar\&cbl=44156

18. Table of Contents \- Open Society Foundations, https://www.opensocietyfoundations.org/uploads/42333bd7-4b3e-46e9-9a9a-0f9a4ae3c577/1euaccesscorruptionfullreport\_20020601\_0.pdf

19. Justice and Equality in Muslim Family Laws: Challenges, Possibilities, and Strategies for Reform', https://scholarlycommons.law.wlu.edu/cgi/viewcontent.cgi?article=1217\&context=wlulr

20. TsuInfo Alert \- prepared by the Washington State Department of Natural Resources on behalf of the \- National Tsunami Hazard Mitigation Program \- WA DNR, https://dnr.wa.gov/sites/default/files/2025-03/ger\_tsuinfo\_2006\_v8\_no3.pdf

21. The Challenges Multinational Corporations Face in Protecting Their Well-Known Trademarks in China \- BrooklynWorks, https://brooklynworks.brooklaw.edu/cgi/viewcontent.cgi?article=1270\&context=bjil

22. International Journal of Intelligence and CounterIntelligence, Volume 39, Issue 3 (2026), https://www.tandfonline.com/toc/ujic20/current

23. International Association of Law Enforcement Intelligence Analysts: Home, https://www.ialeia.org/

24. The Rise and Decline of the American Century 9781501726149 \- DOKUMEN.PUB, https://dokumen.pub/the-rise-and-decline-of-the-american-century-9781501726149.html

25. AJIA Issue XXIV: Narratives \- The Attaché, https://theattache.ca/wp-content/uploads/2025/07/ajia-issue-xxiv-narratives.pdf

26. BRUNEL UNIVERSITY Michael C. Joel The United States' Psychological Strategy Board and Operations Coordinating Board, https://bura.brunel.ac.uk/bitstream/2438/25953/1/FulltextThesis.pdf

27. Selective Empathy \- Brill, https://brill.com/downloadpdf/display/title/73467.pdf

28. On Speaking Terms \- EMN Ireland, http://emn.ie/files/p\_201211231215502007\_On\_Speaking\_Terms\_ICI.pdf