Architecture Report: Provenance-First, Fail-Forward Editorial Pipeline for InternationalIntelligence.org

Full report

On this page

1. Executive editorial-system recommendation

The integration of autonomous systems into the editorial pipeline of the InternationalIntelligence.org Daily Brief presents profound architectural challenges. Current system descriptions reveal a monolithic, highly coupled architecture where research, validation, and composition share overlapping failure domains. In this paradigm, a single defective event or hallucinated citation can collapse an entire publication batch, forcing the system to discard valid evidence and repeatedly pay computational costs to rediscover accepted facts. The structural reliance on continuous, unbroken generation loops fundamentally contradicts the principles of digital evidence preservation and robust systems engineering. To resolve these vulnerabilities, the system must transition to a provenance-first, fail-forward architecture rooted in the distributed Saga transaction pattern1. By treating the editorial process as a finite state machine, local transactions—such as source retrieval, claim decomposition, and translation—operate independently and atomically. When an operation fails or produces a factual hallucination, the system executes a compensating transaction to quarantine the specific defect while preserving the underlying, validated state of the surrounding research3. This decoupling ensures that valid evidence is permanently retained independently of composition failures. Furthermore, the pipeline must enforce strict epistemological boundaries. Claims must be atomically decomposed and traced to their origins using W3C PROV-O ontology standards5, ensuring that the composition contract receives only validated, immutable facts. English and Spanish generation must occur via a hybrid parallel process driven by cross-lingual Natural Language Inference (NLI) models, guaranteeing factual parity without sacrificing idiomatic fluency7. Ultimately, publication must be executed as an atomic promotion anchored by cryptographic timestamps, ensuring the Daily Brief remains a highly trusted, immutable record of international intelligence9.

2. Evidence and provenance principles

An evidence-oriented publication cannot treat digital information as transient text; it must treat it as forensic data. The foundation of this pipeline relies on integrating digital open-source intelligence (OSINT) standards with rigorous journalistic ethics and semantic web tracking. The Berkeley Protocol on Digital Open Source Investigations establishes the international minimum standards for the identification, collection, preservation, and verification of public digital information11. For the InternationalIntelligence.org pipeline, this necessitates operating as a Digital Evidence First Responder (DEFR) compliant with ISO/IEC 27037 guidelines13. The pipeline must cryptographically hash every acquired source at the point of capture, ensuring a pristine chain of custody before any artificial intelligence extraction alters the context14. This ensures that the evidence base remains defensible and untampered. To map the relationships between these cryptographic artifacts and the final journalistic output, the system must employ the W3C PROV Ontology (PROV-O) framework6. The PROV data model structures provenance around three core nodes: Entities, Activities, and Agents6. In this pipeline, Entities represent the raw source documents and the finalized atomic claims. Activities represent the specific pipeline stages, such as extraction or cross-lingual parity checking. Agents represent the specific model version or deterministic algorithm executing the task5. By linking these nodes with standardized relationships, the pipeline establishes a mathematically verifiable graph that traces every generated sentence back to its digital origin. Operating within this forensic framework ensures adherence to the core tenets of journalistic ethics, particularly those outlined in the Reuters Handbook of Journalism. The pipeline is structurally forced to prioritize accuracy over speed, mandating strict attribution boundaries18. Unverified material or single-source allegations are prevented from crossing the internal process boundary into institutional reporting without explicit, mandatory distancing language19.

3. Candidate-event schema

The pipeline requires a canonical schema to serve as the unified data-transfer object across all Saga states. This schema prevents the composition contract from hallucinating variables or discarding vital context by ensuring all data exists within strict, predefined structural bounds.

The inclusion of the Extended Date/Time Format (EDTF) is highly critical for international intelligence gathering. Historical and geopolitical events frequently suffer from temporal ambiguity. Plain ISO 8601 formatting cannot express concepts such as "sometime in late April" or "approximately 2026." The EDTF extension, integrated via ISO 8601-2, allows the pipeline to ingest fuzzy temporal data honestly without forcing the system to hallucinate an artificially precise timestamp20.

4. Claim-to-source model

The traditional mechanism of providing an artificial intelligence model with multiple articles and requesting a synthesized summary reliably produces "hallucinated citations," a phenomenon where the model invents plausible but entirely fabricated sources to support its narrative24. In scholarly and intelligence applications, these hallucinations contaminate the archival record, demanding a structural defense mechanism26. To mitigate this, the pipeline relies on Atomic Claim Decomposition, modeled on the FActScore framework23. Rather than summarizing at the document level, an extraction agent breaks the source narrative into minimal, self-contained factual assertions (atomic claims)27. Each atomic claim is independently verified and mapped directly to a normalized source record. If a claim lacks a verified mapping, it is discarded before composition begins.

Source Record Definition

The pipeline must standardize all ingested material into the following structured format to preserve forensic integrity.

Evidence States

The system must map the corroborated atomic claims into a strict, controlled vocabulary. This vocabulary dictates the downstream lexical generation, determining how the English and Spanish composition agents construct sentences and apply epistemic distancing.

5. Source independence and corroboration

Relying on raw source counts creates a vulnerability to "circular reporting," where a piece of information appears to originate from numerous independent outlets but actually traces back to a single, unverified node29. If an automated pipeline equates ten syndicated wire-service copies with "ten corroborating sources," the foundational evidence standards of the publication are compromised. Authoritative OSINT methodologies, such as those utilized by Bellingcat, mandate rigorous source disambiguation to prevent this illusion of multiple validations31. To distinguish genuinely independent corroboration from artificial amplification, the pipeline must implement an auditable independence-scoring algorithm. This methodology identifies and groups sources based on their origin rather than their URL. Detection Mechanisms for Non-Independent Sources:

• Syndicated copies & Wire-service republication: The system calculates the Jaccard similarity and semantic embedding distances between the core text of different URLs. High overlap (e.g., \>80% similarity) across different publisher domains indicates syndication33.
• Press-release repetition: Identified by extracting named entity quotes and structural mirroring of corporate or state media sites.
• Circular citation: Detected through hyperlinking analysis, revealing when Source B cites Source A, and Source C cites Source B.
• Multiple articles relying on one anonymous source: Natural language processing extracts attribution phrases (e.g., "an official familiar with the matter told Reuters"). If multiple articles share the same attribution structure without adding new primary data, they are grouped.
• AI-generated aggregation pages: Detected via low semantic entropy, high perplexity variance, or hallucination-detection heuristics, identifying pages that merely rewrite existing reports without independent verification34.

Independence-Scoring Method: The system constructs a graph where nodes are Source Records and edges represent structural and semantic similarity. A clustering algorithm groups sources with a cosine similarity exceeding 0.85 into a single independence\_group. The true corroboration\_count for any candidate event is defined strictly as the number of distinct independence\_group clusters, completely ignoring the total volume of URLs. A candidate event requires a minimum corroboration\_count of 2, originating from differing organizational classes, to upgrade from an "Investigative allegation" to an "Independently corroborated claim."

6. URL and citation reconciliation

Without rigorous URL canonicalization, the pipeline will interpret identical sources accessed via different paths as distinct entities, failing to deduplicate events and breaking the PROV-O provenance linkage. Normalization must occur at the point of ingestion, adhering to RFC 3986 standards for Uniform Resource Identifiers35. The reconciliation module applies deterministic rules to clean and bind source records, ensuring the underlying evidence base is accurately measured.

7. Candidate retention and deficit calculation

A robust, fail-forward editorial pipeline must completely eliminate the risk of resetting successfully validated work due to a downstream error. If a composition agent times out, or if a single candidate event triggers a safety filter, discarding the entire daily batch wastes API resources and deletes valid OSINT research. To resolve this, the system implements an Orchestration-based Saga pattern1. The Saga pattern divides the monolithic pipeline into a sequence of isolated, idempotent local transactions3. Fail-Forward Retention Mechanics:

1. Independent Persistence: The moment a candidate event passes the local validation phase, it is committed to a resilient state store (e.g., PostgreSQL or DynamoDB) using its stable\_local\_id. This commitment occurs independently of any external provider response or downstream composition success.

2. Preservation of Mappings: The candidate's PROV-O provenance graph, source mappings, and validation results are serialized via JSON-LD and immutably persisted alongside the candidate record41.

3. Compensating Transactions: If the final composition step fails, the orchestrator issues a compensating transaction. This action rolls back the failed composition state but leaves the research and validation states entirely untouched2.

4. Process Resumption: The pipeline can retry the composition stage utilizing the retained JSON-LD database, entirely bypassing the need for redundant web research. If a specific candidate is consistently causing the failure, the orchestrator quarantines only that defective candidate and resumes processing the remainder of the batch.

Deficit Model Following the initial research and validation pass, the orchestrator evaluates the retained candidate pool against the publication's portfolio criteria. This evaluation calculates explicit deficits, preventing the system from blindly searching the internet. The pipeline measures the following deficits:

8. Supplemental-research strategy

Supplemental research in this architecture is strictly reactive. It is never executed as a broad, unfocused sweep; it is dispatched solely to repair the explicit shortfalls calculated by the Deficit Model. Targeted Dispatch Mechanism: When the orchestrator identifies a deficit, it constructs a highly constrained prompt for the research agent. For example, if the calculation reveals a regional breadth deficit (e.g., zero events originating from South America), the supplemental request will dictate: "Execute retrieval targeting South American geopolitical developments occurring within the past 24 hours. Exclude all results pertaining to North America, Europe, or the topic of global trade." The orchestrator permits a maximum of two repair attempts per deficit. If the system fails to discover valid candidates after these attempts, it logs a terminal condition for that specific deficit, appending an audit warning that regional parity could not be achieved, and proceeds to composition with the available data. To prevent the research agent from filling a quota by retrieving old, previously published events, the system cross-references the duplicate\_fingerprint and near\_duplicate\_fingerprint against the historical archive35. If a newly retrieved candidate represents a near-duplicate of an event published the previous week, it is automatically rejected. Newly validated candidates are seamlessly merged into the existing state store, expanding the pool without resetting or overwriting the previously accepted events.

9. Quality-gate matrix

The evaluation of candidate events must abandon opaque, holistic LLM scoring (e.g., prompting a model to "rate this article out of 10"). Such scoring masks hallucinations, obscures bias, and fails to provide actionable feedback23. Instead, the pipeline employs a deterministic, transparent gate matrix that strictly separates mandatory viability checks from portfolio-level balancing goals. Mandatory Gates (Binary Pass/Fail): If a candidate fails any of the following gates, the retention\_status is updated to Rejected, the rejection\_reason is logged, and the candidate is dropped from the active pool.

• Source Validity: URLs must resolve via HTTP status 200, the domain must not exist on the editorial disinformation blocklist, and the payload must pass heuristic checks for AI-generated spam.
• Claim Support (Hallucination Check): Utilizing cross-lingual NLI models (e.g., mDeBERTa-v3), the system verifies that the generated concise\_factual\_summary is strictly entailed by the source text7. Any detection of contradiction or a neutral state (indicating an unsupported claim) triggers immediate rejection45.
• Chronology: The parsed EDTF timestamp20 must align precisely with the target publication date window.
• Duplication: The event's duplicate\_fingerprint must not match any entity currently in the state store or recently published archive.
• Citation Completeness: Every atomic claim within the summary must possess a cryptographic link to at least one valid source ID in the PROV-O graph.

Portfolio-level Gates (Balancing Goals): These gates evaluate the candidate pool collectively. Failure does not result in immediate rejection but rather triggers the Deficit Model or informs the final selection algorithm.

• Geographic & Topic Diversity: Evaluated to ensure the final edition represents a balanced global perspective.
• Source Diversity & Corroboration: Evaluated to prioritize candidates supported by multiple independent primary sources.
• Uncertainty Labeling: Verifies the presence of appropriate epistemic distancing language based on the candidate's evidence\_status.
• Language Readiness: Monitors the translation pipeline to ensure parity constraints are met before merging into the final publication package.
• Editorial Neutrality & Safety Review: Flags candidates containing highly sensitive or legally perilous content for manual human review prior to publication.

10. Bilingual composition and parity controls

Publishing an immutable edition in both English and Spanish introduces severe synchronization vulnerabilities. The system must guarantee that factual claims, numbers, and source trails remain absolutely identical across languages while permitting natural, idiomatic expression. Bilingual Design Recommendation: Hybrid Process Generating the languages sequentially (e.g., drafting in English and translating the output to Spanish) often causes cultural nuances to be lost and propagates minor errors downstream. Generating them entirely separately creates factual divergence, where the Spanish agent might select different data points than the English agent46. The optimal architecture is a Hybrid Process:

1. Unified Structured Evidence Record: The system centralizes all validated facts, dates, numbers, and actor attributions into a single, language-agnostic JSON-LD graph.

2. Parallel Generation: Separate English and Spanish composition agents draft their respective texts simultaneously, drawing exclusively from the identical JSON-LD root. This allows each agent to construct sentences idiomatically without being constrained by the syntax of the other language.

3. Strict Parity Validator: The drafted texts are subjected to a rigorous cross-lingual factual consistency check.

Automated Parity Checks: To ensure the parallel generation did not introduce discrepancies, the system executes the following automated checks:

• Omitted qualifiers & Stronger certainty: An NLI model analyzes both texts to ensure the Spanish draft does not assert as absolute fact what the English draft correctly labels as an allegation.
• Changed numbers & Dates: Deterministic regular expressions extract and compare all integers, percentages, and dates across both texts.
• Actor reversal & Missing negation: Dependency parsing ensures the subject, action, and object relationships match symmetrically in both languages.
• Translation Quality Threshold: The semantic equivalence is evaluated using the COMET-22 metric. A strict threshold of \>= 0.82 is enforced to guarantee high translation fluency and accuracy48.

While automated systems handle factual parity, professional human Spanish review remains essential for validating cultural register and selecting highly sensitive geopolitical terminology, where literal translations may inadvertently carry unintended political bias.

11. Final validation and targeted repair

The composition contract serves as the final barrier before publication. This contract is rigidly designed: it receives only validated candidate records from the Saga state store. It is mathematically prohibited from adding new events, introducing new facts, or executing new web research. It must preserve all stable event IDs and source mappings, producing a bounded, structured output containing the English and Spanish text alongside their uncertainty fields. Once the composition contract generates the final edition, a "Final Validation" agent audits the entire package. Final Validation Checks:

• Unsupported factual clauses: A final NLI entailment scan ensures no hallucinations slipped through during the drafting phase.
• Citation loss & Wrong-claim citation: Verifies that every sentence maps correctly to the original source IDs provided in the JSON-LD graph.
• Headline exaggeration: A semantic similarity check ensures the headline does not overstate the claims present in the summary.
• Date/Timezone errors: Verifies absolute compliance with ISO 8601 UTC standards50.
• Missing "what is unknown" language: Enforced specifically for events carrying an Unresolved evidence state.
• Event count & ID mismatch: Ensures the English and Spanish editions map 1:1, containing the exact same number of events with identical stable IDs.

Targeted Repair Boundaries If the composition is mostly usable but contains a localized defect, the system relies on targeted repair rather than discarding the entire edition.

• Deterministic local repair: Utilized for minor formatting errors, broken Markdown links, or missing tracking metadata. The system resolves these programmatically.
• Targeted model repair: If a specific sentence in one event fails the NLI entailment check (indicating a hallucination)25, the system quarantines only that sentence. A repair agent is prompted: "The preceding sentence contradicts the source data. Rewrite to align strictly with the provided text."
• Candidate removal: If targeted repair fails after two attempts, the defective event is entirely removed from the composition. The remainder of the edition proceeds.
• Process quarantine: There is a hard boundary beyond which automatic repair is deemed unsafe. If the removal of defective events causes the total event count to drop below the minimum acceptable threshold (e.g., \< 8 events), or if systemic corruption is detected across multiple events, the entire edition is halted, quarantined, and flagged for immediate human review.

12. Atomic publication and correction lifecycle

To fulfill its mandate as a trusted, neutral publication, the deployment of the Daily Brief must be an atomic operation. This prevents partial updates, broken links, or states where the English edition is live but the Spanish edition is missing. Atomic Publication Workflow:

1. Build in temporary location: The English edition, Spanish edition, source map, and metadata (Schema version, Process ID, Publication Time) are compiled into a hidden staging directory.

2. Validate every file: The system ensures all JSON schemas parse correctly and HTML/Markdown is perfectly formed.

3. Verify parity & bindings: A final checksum confirms that cross-lingual IDs and URL mappings are intact.

4. Compute hashes: SHA-256 hashes are generated for all content payloads, finalizing the digital chain of custody14.

5. Atomically promote: Utilizing atomic symlink swapping (in traditional server architectures) or atomic state updates (in object storage like S3), the temporary directory replaces the live directory instantaneously. This ensures a user never encounters a partially published state.

6. Update supervisor & deduplicate: The orchestrator logs the successful promotion. If a duplicate publish command is received, the system verifies the hashes; if identical, the command acts as a no-op.

7. Immutable Anchoring: The hashes of the finalized edition are anchored to a blockchain utilizing OpenTimestamps (RFC 6962 compliant timestamp tokens). This provides cryptographically verifiable proof of publication at a specific point in time, protecting the publication against historical tampering or allegations of retroactive editing9.

8. Recover inconsistencies: If artifact promotion and supervisor updates become inconsistent (e.g., network failure mid-swap), the system automatically rolls back to the previous atomic state and alerts the engineering team.

Corrections Model When an error is discovered post-publication, the system must adhere to strict transparency protocols. It must never silently rewrite history.

• The original, flawed edition is preserved via S3 Object Lock (WORM storage), maintaining the immutable record53.
• A new revision is generated and appended to the revision history.
• The system integrates Schema.org's ClaimReview and MediaReview structured data55 into the JSON-LD metadata of the new revision. This explicitly identifies the changed claims while retaining the old source mappings for forensic comparison.
• An explicit "Correction Note" is surfaced on both the English and Spanish user interfaces, detailing precisely what was altered and explaining the rationale for the correction.

13. Failure-mode analysis

A resilient architectural design assumes partial AI failure is inevitable and builds recovery paths accordingly57. The following narrative details the system's response to primary failure modes.

• Valid evidence is discarded: If the Saga state comparison reveals that the post-composition candidate count is lower than the pre-composition validated count (e.g., the LLM randomly dropped an event), the orchestrator intercepts the payload. It restores the dropped candidates directly from the JSON-LD state store and re-injects them into the compilation stage, bypassing the LLM.
• Source URLs are not reconciled: If duplicate domains or text blocks are detected late in the pipeline by the Jaccard similarity scanner, the system merges them into a single independence\_group and recalculates the corroboration deficit.
• Composition invents or drops citations: If the Final Validation step discovers a PROV-O ID mismatch (a hallucinated citation)25, the system executes targeted model repair, instructing the LLM to rewrite the summary utilizing only the provided source IDs.
• English and Spanish records diverge: If the mDeBERTa-v3 cross-lingual NLI returns a Contradiction state59, the system initiates targeted repair of the diverging Spanish sentence, forcing it to align with the English structured baseline, subsequently verified by COMET-22.
• A single defective event blocks the entire edition: If a target event consistently fails NLI verification (caught in a hallucination loop), the Candidate Removal protocol is triggered. The single event is quarantined, and provided the total event count remains viable, publication of the broader edition proceeds.
• Valid research is lost when composition fails: Because the Orchestration Saga pattern persists research state independently1, a total failure of the composition stage merely triggers a compensating transaction. The system retries composition using the saved JSON-LD database, incurring zero additional web research costs.

14. Deterministic fixtures and evaluator benchmark

To ensure the quality gates and NLI evaluators function without regression over time, the system continuously benchmarks the pipeline against synthetic deterministic fixtures.

Synthetic Example 1: A fully acceptable event

Context: A verified election outcome reported independently by Reuters, the BBC, and local state media.Pipeline Execution: The extraction agent accurately decomposes the reports into atomic claims. The URL normalizer correctly groups the local and international reports into distinct independence groups, yielding a corroboration\_count of 3\. The EDTF parser records the date as 2026-08-01.Evaluation: The event attains an evidence\_status of Verified public fact. The mDeBERTa-v3 NLI model registers strict entailment between the summary and the source texts. The event easily passes all mandatory and portfolio gates and is integrated seamlessly into the bilingual composition.

Synthetic Example 2: A salvageable event with a citation mismatch

Context: A major climate summit announcement. The research agent successfully extracts the core facts. However, during drafting, the composition agent attributes a specific quote to an NGO report (Source B) when the PROV-O graph indicates it actually originated from an official press release (Source A).Pipeline Execution: The event is assigned an evidence\_status of Official statement. During the Final Validation phase, the validation agent detects the PROV-O mapping error (a hallucinated citation).Evaluation: Because the underlying text is factually accurate and merely misattributed, the system does not discard the event. It executes a deterministic targeted repair, rewriting the citation clause to properly map the quote to Source A. The repaired, accurate event is then included in the final edition.

Synthetic Example 3: An event that must be rejected

Context: Unverifiable, highly emotive footage of a military border skirmish begins circulating on social media, rapidly aggregated by heavily biased, state-sponsored blogs.Pipeline Execution: The event is ingested and assigned an evidence\_status of Investigative allegation due to its unverified nature.Evaluation: The source independence check reveals a corroboration\_count of 1, as algorithmic clustering determines all the blogs share the exact same text network (circular reporting). Furthermore, the NLI evaluator detects that the composition agent drafted a headline assuming the skirmish is confirmed, directly contradicting the high uncertainty indicated in the raw source text. The event violates both the minimum corroboration gate and the editorial neutrality gate. The system immediately quarantines the candidate, logs the rejection reason, and prompts the orchestrator to request supplemental research on a different topic.

15. Phased implementation roadmap

Phase 1: Data Model & W3C PROV Integration (Weeks 1-3)

• Implement the Candidate-Event JSON-LD schema across all backend services.
• Establish the PostgreSQL/DynamoDB state store to support Orchestration Saga pattern persistence.
• Integrate EDTF ISO 8601-2 parsing libraries for robust temporal data handling.

Phase 2: OSINT Extraction & Quality Gates (Weeks 4-7)

• Deploy RFC 3986 URL normalization and Jaccard similarity deduplication logic.
• Implement atomic claim decomposition utilizing the FActScore methodology.
• Integrate mDeBERTa-v3 models for NLI factual consistency checking at the quality gate level.

Phase 3: Hybrid Bilingual Composition (Weeks 8-10)

• Develop parallel LLM drafting pipelines capable of generating text exclusively from the structured JSON-LD root.
• Deploy cross-lingual NLI and COMET-22 thresholding mechanisms to enforce English/Spanish parity.

Phase 4: Atomic Publication & Immutability (Weeks 11-12)

• Implement atomic deployment utilizing symlink swapping or S3 Object Lock state updates.
• Integrate OpenTimestamps for blockchain anchoring of all published editions.
• Finalize and deploy Schema.org ClaimReview and MediaReview correction workflows.

16. Acceptance criteria

To consider the architectural overhaul complete and ready for production, the system must verifiably meet the following rigorous thresholds:

• Provenance Retention: 100% of candidates passing the local validation stage must be successfully stored independently of LLM composition success, proven via simulated composition timeouts.
• Parity Verification: The cross-lingual pipeline must consistently achieve a \>= 0.82 COMET-22 score and demonstrate 0% detected semantic contradiction between English and Spanish outputs across a 500-event test suite48.
• Hallucination Elimination: The integration of atomic claim mapping and NLI gating must reduce published hallucinated citations to \< 0.1%, benchmarked against a 1,000-event synthetic adversarial dataset25.
• Cost Efficiency: Supplemental research API calls must be triggered only when the deficit model mathematically demands it, reducing redundant computational and token spend by an estimated 40% compared to the monolithic baseline.
• Atomic Rollback: Simulated deployment failures (e.g., interrupted network transfers) must result in a 0-millisecond user-facing downtime, with the system cleanly and automatically restoring the previous immutable state.

Diagrammatic Representations

While standard markdown restricts complex image rendering, the architecture and provenance flows are represented below via structural relationship tables, detailing the specific interactions between nodes.

Provenance Graph Structure (PROV-O Mapping)

Editorial Pipeline Sequence (Saga Orchestration)

Works cited

1. Pattern: Saga \- Microservices.io, https://microservices.io/patterns/data/saga.html

2. Saga Design Pattern \- Azure Architecture Center | Microsoft Learn, https://learn.microsoft.com/en-us/azure/architecture/patterns/saga

3. Saga Pattern Made Easy \- DEV Community, https://dev.to/temporalio/saga-pattern-made-easy-4j42

4. SAGA Pattern \- Deep Thought, https://deep-thought.norwin.at/tech-kb/web-development/SAGA-Pattern

5. PAV ontology: provenance, authoring and versioning \- PMC, https://pmc.ncbi.nlm.nih.gov/articles/PMC4177195/

6. 5\. Provenance information \- FAIR Cookbook, https://faircookbook.elixir-europe.org/content/recipes/reusability/provenance.html

7. DeBERTa-v3-large-mnli-fever-anli-ling-wanli vs mDeBERTa-v3-base-xnli-multilingual-nli-2mil7 \- AIModels.fyi, https://www.aimodels.fyi/models/compare/deberta-v3-large-mnli-fever-anli-ling-wanli-moritzlaurer-vs-mdeberta-v3-base-xnli-multilingual-nli-2mil7-moritzlaurer

8. Large Language Models for Multilingual Previously Fact-Checked Claim Detection \- arXiv, https://arxiv.org/html/2503.02737v3

9. OpenTimestamps \- Wikipedia, https://en.wikipedia.org/wiki/OpenTimestamps

10. How The Bitcoin Blockchain Is Fighting Fraud In Guatemala's Presidential Elections, https://bitcoinmagazine.com/culture/bitcoin-blockchain-is-fighting-fraud-in-guatemalas-presidential-elections

11. Strengthening Atrocity Cases with Digital Open Source Investigations \- Lieber Institute, https://lieber.westpoint.edu/strengthening-atrocity-cases-digital-open-source-investigations/

12. Advancing human rights investigations now and for the future \- Medium, https://unhumanrights.medium.com/advancing-human-rights-investigations-now-and-for-the-future-67ae9be1129a

13. WHO PUSHED THE KEYS: F.A.C.T. Attribution Framework for Digital Forensics \- Medium, https://voodootomato.medium.com/who-pushed-the-keys-f-a-c-t-attribution-framework-for-digital-forensics-db18aa02d419

14. Chain of Custody for Open-Source Evidence | Next Sight, https://www.next-sight.com/resources/chain-of-custody-osint

15. Digital forensics: how to acquire digital evidence that holds up in court, https://pasqualepillitteri.it/en/news/7671/digital-forensics-acquire-digital-evidence-court

16. PROV-DM: The PROV Data Model \- W3C, https://www.w3.org/TR/prov-dm/

17. Humanitarian data infrastructures for missing migrants: A multimodal and ethics-integrated framework. \- Open Research Europe, https://open-research-europe.ec.europa.eu/articles/6-118

18. Reuters Handbook of Journalism Standards and Values \- Media Reform Coalition, https://www.mediareform.org.uk/wp-content/uploads/2015/12/Reuters\_Handbook\_of\_Journalism.pdf

19. Principles of Ethical Journalism, https://journalismauthority.com/principles-of-ethical-journalism

20. Convert EDTF to Regular Dates Without Needing to Code \- Matthew Lincoln, PhD, https://matthewlincoln.net/2021/03/20/convert-edtf-boundaries.html

21. Best Practices to Extract and normalise historical dates | Elara "Aether\_Forge\_88" Reed, https://digitalrelics.uk/posts/named-entity-history/extract-historical-dates

22. Extended Date/Time Format (EDTF) Specification \- Library of Congress, https://www.loc.gov/standards/datetime/edtf.html

23. FActScore: Fine-grained Atomic Evaluation of Factual Precision in Long Form Text Generation \- arXiv, https://arxiv.org/html/2305.14251v2

24. LLM Hallucination Statistics 2026: AI Gets Facts Wrong Up to 82% of the Time, https://sqmagazine.co.uk/llm-hallucination-statistics/

25. CiteAudit: You Cited It, But Did You Read It? A Benchmark for Verifying Scientific References in the LLM Era \- arXiv, https://arxiv.org/html/2602.23452v3

26. Phantom References: Hallucinated Citations That Survive Peer Review at Top‑Tier Conferences \- arXiv, https://arxiv.org/html/2607.00738v1

27. Atomic Contrastive Verification: Fine-Grained Fact-Checking via Claim Decomposition and Knowledge Graph-Grounded Contrastive Reasoning \- MDPI, https://www.mdpi.com/2227-7390/14/10/1769

28. A Closer Look at Claim Decomposition \- ResearchGate, https://www.researchgate.net/publication/382634843\_A\_Closer\_Look\_at\_Claim\_Decomposition

29. (PDF) Manipulative questions in internet discourse. The case of a 4chan/8chan conspiracy theorist QAnon \- ResearchGate, https://www.researchgate.net/publication/385652199\_Manipulative\_questions\_in\_internet\_discourse\_The\_case\_of\_a\_4chan8chan\_conspiracy\_theorist\_QAnon

30. covert action and intelligence | Criminal homework help \- SweetStudy, https://www.sweetstudy.com/files/intelligence-fromsecretstop-markm-lowenthal-pdf-4864979

31. 2022 SE1 Intel Disciplines & PAI.indd \- from MIPB, https://mipb.ikn.army.mil/media/b3uf3baa/mipb-2022-04-se1-se1-full-issue.pdf

32. USIR260228a – February 28, 2026 \- Airwars, https://airwars.org/civilian-casualties/usir260228a-february-28-2026/

33. Semantic Similarity for Zero-Shot Hate Speech Detection in Low-Resource Languages, https://www.researchgate.net/publication/401510361\_Semantic\_Similarity\_for\_Zero-Shot\_Hate\_Speech\_Detection\_in\_Low-Resource\_Languages

34. DecMetrics: Structured Claim Decomposition Scoring for Factually Consistent LLM Outputs \- arXiv, https://arxiv.org/html/2509.04483v1

35. How to normalize a URL in Java? \- Stack Overflow, https://stackoverflow.com/questions/2993649/how-to-normalize-a-url-in-java

36. public-key-directory-specification/Specification.md at main \- GitHub, https://github.com/fedi-e2ee/public-key-directory-specification/blob/main/Specification.md

37. How can I normalize a URL in python \- Stack Overflow, https://stackoverflow.com/questions/120951/how-can-i-normalize-a-url-in-python

38. Zone-h Alternative ((better)) Jul 2026, http://15.168.174.150/pond/northern-oasis/zone-h-alternative-a480ki

39. Web-Search is coming to a screeching performance halt as Google shuts down their free search index, and traffic defenders like Cloudflare challenge AI at every gateway. What are our options? : r/LocalLLaMA \- Reddit, https://www.reddit.com/r/LocalLLaMA/comments/1tcaboi/websearch\_is\_coming\_to\_a\_screeching\_performance/

40. Payment System Design: Ledger, Idempotency, and Settlement \- Ajit Singh, https://singhajit.com/payment-system-design/

41. Cross-linking BioThings APIs through JSON-LD to facilitate knowledge exploration \- PMC, https://pmc.ncbi.nlm.nih.gov/articles/PMC5796402/

42. MIDAS Catalog JSON-LD Metadata Architecture, https://midasnetwork.us/midas-catalog-json-ld-metadata-architecture/

43. URL normalization for de-duplication of web pages \- ResearchGate, https://www.researchgate.net/publication/221614473\_URL\_normalization\_for\_de-duplication\_of\_web\_pages

44. Beyond Translation: LLM-Based Data Generation for Multilingual Fact-Checking \- arXiv, https://arxiv.org/html/2502.15419v1

45. Primers • Factuality in LLMs \- aman.ai, https://aman.ai/primers/ai/factuality-in-LLMs/

46. Are LLMs Breaking MT Metrics? Results of the WMT24 Metrics Shared Task \- Statistical and Neural Machine Translation, https://www2.statmt.org/wmt24/pdf/2024.wmt-1.2.pdf

47. How to Evaluate Speech Translation with Source-Aware Neural MT Metrics \- arXiv, https://arxiv.org/html/2511.03295v3

48. https://futureagi.com/blog/evaluating-llm-translation-quality-2026/\#:\~:text=Run%20COMET%2D22%20in%20the,COMET%2D22%20%3E%3D%200.82.

49. Evaluating LLM Translation Quality (2026) \- Future AGI, https://futureagi.com/blog/evaluating-llm-translation-quality-2026/

50. ISO 8601 \- Wikipedia, https://en.wikipedia.org/wiki/ISO\_8601

51. What is Certificate Transparency and Why It Matters for Your, https://inventivehq.com/blog/what-is-certificate-transparency-and-why-it-matters

52. Standard-Compliant Blockchain Anchoring for Timestamp Tokens \- MDPI, https://www.mdpi.com/2076-3417/15/23/12722

53. Amazon S3 Object Lock \- AWS, https://aws.amazon.com/s3/features/object-lock/

54. Managing object immutability with Object Lock (WORM) \- OVHcloud Documentation, https://docs.ovhcloud.com/en/guides/storage-and-backup/object-storage/s3-managing-object-lock

55. ClaimReview \- Schema.org Type, https://schema.org/ClaimReview

56. Fact-Checking in the Age of AI: Navigating Truth, Entities, and SEO \- WordLift, https://wordlift.io/blog/en/article-fact-checker-ai/

57. Belief-Calibrated Multi-Agent Consensus Seeking for Complex NLP Tasks \- OpenReview, https://openreview.net/pdf?id=AYqtMLRwzj

58. Delayed Verification Destabilizes Multi-Agent LLM Belief: Instability Thresholds and Optimal Corrector Placement \- arXiv, https://arxiv.org/html/2606.27409v1

59. Hybrid natural language processing tool for semantic annotation of medical texts in Spanish, https://pmc.ncbi.nlm.nih.gov/articles/PMC11708069/