I need to brief a teammate on Arc finality for small payment confirmation. What are the two or three facts I should lead with?
· llm:deepseek:deepseek-v4-pro
> ⚠ Low confidence — Each summary sentence is tied to a verbatim excerpt and model-checked; completeness and independent factual correctness remain unverified. Evidence assessment: 1 sub-claim remains below the evidence threshold. Treat this as provisional.
Model-written summary with sentence-level citations. Each sentence is followed by the verbatim source text it was checked against; sentences without a qualifying excerpt were removed.
Research target 1
Requested topic (unverified): “What is the definition of Arc finality in the context of payment confirmation?”
Arc finality means every transaction is either unconfirmed or final, with no intermediate state. Source text: “Arc provides deterministic finality: every transaction is either unconfirmed or final, with no intermediate state.”
Research target 2
Requested topic (unverified): “How long does it take for a payment to reach finality on Arc?”
Arc delivers irreversible transaction settlement in under one second. Source text: “Arc’s deterministic finality delivers irreversible transaction settlement in under one second.”
Research target 3
Requested topic (unverified): “What are the conditions or mechanisms that ensure finality on Arc?”
Finality is ensured by a Byzantine Fault Tolerant consensus protocol where a block becomes irreversible once more than two-thirds of validators sign off on it. Source text: “This guarantee comes from the network’s consensus layer, which uses a Byzantine Fault Tolerant (BFT) consensus protocol—once more than two-thirds of validators sign off on a block, that block is irreversible.”
Research target 4
Requested topic (unverified): “What are the risks or limitations of relying on Arc finality for small payments?”
Arc is designed for sub-second settlement, but that does not mean every stage of a payment or crosschain workflow finishes within the same timeframe. Source text: “Arc is also designed for sub-second settlement, but that does not mean every stage of a payment or crosschain workflow finishes within the same timeframe.”
Evidence gap: the recorded assessment remains below the support threshold for this target.
Summary sentences are model-written and model-checked, not independently verified; they claim no more than their excerpts and are not a complete synthesis. Excerpts establish source grounding, not that a source is correct. Source statements may be wrong or conflicting. Payment states remain in the separate receipt.
Next steps to complete this research
These are suggested follow-up steps; this run has not performed them. They do not change the recorded evidence or payment state.
- “Payment Systems Comptroller's Handbook”: Original text was unavailable. Check the publisher URL and provide an accessible original of the same document; this failure does not establish that the document does not exist.
- “Day 7: What Is “Finality,” and Why Does Sub-Second ...”: Original text was unavailable. Check the publisher URL and provide an accessible original of the same document; this failure does not establish that the document does not exist.
Evidence ledger — recorded source excerpts
Research targets are unverified topics. Coverage is an estimate of excerpt support, not proof of entailment, factual truth or a complete answer.
Requested topic (unverified): “What is the definition of Arc finality in the context of payment confirmation?”
100% estimated“Arc provides deterministic finality: every transaction is either unconfirmed or final, with no intermediate state.” [S1] Deterministic finality and settlement - Arc Docs
Requested topic (unverified): “How long does it take for a payment to reach finality on Arc?”
100% estimated“Arc’s deterministic finality delivers irreversible transaction settlement in under one second.” [S1] Deterministic finality and settlement - Arc Docs
Requested topic (unverified): “What are the conditions or mechanisms that ensure finality on Arc?”
100% estimated“This guarantee comes from the network’s consensus layer, which uses a Byzantine Fault Tolerant (BFT) consensus protocol—once more than two-thirds of validators sign off on a block, that block is irreversible.” [S1] Deterministic finality and settlement - Arc Docs
Requested topic (unverified): “What are the risks or limitations of relying on Arc finality for small payments?”
10% estimated“Arc is also designed for sub-second settlement, but that does not mean every stage of a payment or crosschain workflow finishes within the same timeframe.” [S3] Deterministic Finality in Arc's USDC Settlement Process | Dan Nguyen posted on the topic | LinkedIn
What if a source were missing?
Temporarily leave out one source to see which research targets retain excerpts in this report.
Showing the original excerpt ledger.
What is the definition of Arc finality in the context of payment confirmation?
1 recorded excerpt remain.
Inspect remaining excerpts
“Arc provides deterministic finality: every transaction is either unconfirmed or final, with no intermediate state.”
S1 · arc.io · Deterministic finality and settlement - Arc Docs · version 2e09bd2546282e834734904c03f1bbce463a7ba933bef69b82827b13cc480ea6
How long does it take for a payment to reach finality on Arc?
1 recorded excerpt remain.
Inspect remaining excerpts
“Arc’s deterministic finality delivers irreversible transaction settlement in under one second.”
S1 · arc.io · Deterministic finality and settlement - Arc Docs · version 2e09bd2546282e834734904c03f1bbce463a7ba933bef69b82827b13cc480ea6
What are the conditions or mechanisms that ensure finality on Arc?
1 recorded excerpt remain.
Inspect remaining excerpts
“This guarantee comes from the network’s consensus layer, which uses a Byzantine Fault Tolerant (BFT) consensus protocol—once more than two-thirds of validators sign off on a block, that block is irreversible.”
S1 · arc.io · Deterministic finality and settlement - Arc Docs · version 2e09bd2546282e834734904c03f1bbce463a7ba933bef69b82827b13cc480ea6
What are the risks or limitations of relying on Arc finality for small payments?
1 recorded excerpt remain.
Inspect remaining excerpts
“Arc is also designed for sub-second settlement, but that does not mean every stage of a payment or crosschain workflow finishes within the same timeframe.”
S3 · linkedin.com · Deterministic Finality in Arc's USDC Settlement Process | Dan Nguyen posted on the topic | LinkedIn · version d4b51a5e5cf3041c4a6449804f91c738de4f94d171de41514165cf710395b641
Targets are requested topics, not verified assertions. Excerpts do not prove truth or independent corroboration. This view keeps the answer, confidence and payments unchanged and makes no new requests.
Research evidence matrix
Compare unverified research targets with cited sources and inspect recorded excerpts. An empty cell means no inspectable excerpt was recorded; it does not establish whether a claim is true, false, or disputed. Coverage and agent confidence do not prove entailment, measured accuracy or complete synthesis.
| Research target (unverified) | Inspection status | [S1] Deterministic finality and settlement - Arc DocsPublication: arc.ioPublished: Not recorded | [S3] Deterministic Finality in Arc's USDC Settlement Process | Dan Nguyen posted on the topic | LinkedInPublication: linkedin.comPublished: Not recorded |
|---|---|---|---|
| What is the definition of Arc finality in the context of payment confirmation? | Recorded excerpt | Inspect 1 excerptArc provides deterministic finality: every transaction is either unconfirmed or final, with no intermediate state. | No excerpt recorded |
| How long does it take for a payment to reach finality on Arc? | Recorded excerpt | Inspect 1 excerptArc’s deterministic finality delivers irreversible transaction settlement in under one second. | No excerpt recorded |
| What are the conditions or mechanisms that ensure finality on Arc? | Recorded excerpt | Inspect 1 excerptThis guarantee comes from the network’s consensus layer, which uses a Byzantine Fault Tolerant (BFT) consensus protocol—once more than two-thirds of validators sign off on a block, that block is irreversible. | No excerpt recorded |
| What are the risks or limitations of relying on Arc finality for small payments? | Recorded excerpt | No excerpt recorded | Inspect 1 excerptArc is also designed for sub-second settlement, but that does not mean every stage of a payment or crosschain workflow finishes within the same timeframe. |
Reference export
2 article references. Recorded titles, links and dates; observed scholarly records also include supplied authors, DOI and journal metadata with read limits. Review metadata before using in a paper. Import RIS into Zotero with File → Import.
Cited sources and references
- 1Deterministic finality and settlement - Arc Docsarc.ioFree public reference · no creator payment · extracted html text75%
- 3Deterministic Finality in Arc's USDC Settlement Process | Dan Nguyen posted on the topic | LinkedInlinkedin.comFree public reference · no creator payment · extracted html text25%
Loading feedback…
Decision log · 95 steps
Breaking down: "I need to brief a teammate on Arc finality for small payment confirmation. What are the two or three facts I should lead with?"
Identified 4 research target(s) to investigate; these are not established facts
Deep mode: up to 4 paid/cached/public reads plus one bounded gap-expansion pass when needed.
Web search: 5/5 planned queries attempted, 4 succeeded, 24 public page previews/leads, 1 unavailable queries. Previews and supplied URLs are discovery only. Public reads spend no USDC; model and service operating costs remain separate.
Discovered 2 verified creator source(s) and 54 free public reference(s)
Claim-aware portfolio (exhaustive; bounded selection, not a claim of global optimality) selected 3/11 positive proposal(s): 3 free/cache selections + 0 paid fresh selections, predicting 4/4 claim(s) above the evidence floor with $0.000000/$0.025000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (4/4); paid reading may proceed within the budget.
Official Arc documentation on deterministic finality and settlement; authoritative source for definition, timing, and mechanisms. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3; 0 fetch USDC, 1 attention slot).
The preview discusses payment systems and finality in wholesale payments, which could provide general context for target 2 (conditions/mechanisms) or target 3 (risks). However, it may not specifically cover Arc. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — selected for the claim-aware evidence portfolio (targets claims 3, 4; 0 fetch USDC, 1 attention slot).
Directly relevant article on Arc deterministic finality for payments; likely covers definition, timing, and mechanisms. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — selected for the claim-aware evidence portfolio (targets claims 1, 2, 3; 0 fetch USDC, 1 attention slot).
arXiv rate limit policy is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
BIS paper on gold and geopolitical risks is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Chip Huyen's agents article is about AI agents, not payment finality. - free public feed reference; no purchase or creator reward.
Cloudflare Workers module registry article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Creative Commons heritage roundtable is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
DeepMind private AI compute article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
DOAJ open access interview is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Docker ecosystem event article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
DuckDB Jev article is about SQL conditions, not Arc payment finality. - free public feed reference; no purchase or creator reward.
Eugene Yan's QA evaluation article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Go SIMD article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Google Research federated learning article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Lilian Weng's LLM agents article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Microsoft Research Quine article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Netlify WebMCP challenge is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Ollama Jev-style decision models are unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
OpenAI Developers plugin guide is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
OpenAlex novelty score discussion is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
PostgreSQL dbForge release is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
PyTorch media processing article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Rust 1.99.0 announcement is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Sebastian Raschka's post-training article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Spotify Portal article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Stripe OUSD stablecoin article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Supabase build anything article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Tailscale Meta Muse article is unrelated to Arc payment finality. - free public feed reference; no purchase or creator reward.
Article about NASA engineering excellence, unrelated to Arc finality or payment confirmation. - free public feed reference; no purchase or creator reward.
Article about vLLM disaggregated serving, unrelated to Arc finality or payment confirmation. - free public feed reference; no purchase or creator reward.
Article about Wikimedia community meetup, unrelated to Arc finality or payment confirmation. - free public feed reference; no purchase or creator reward.
Article about x402 Foundation launch, unrelated to Arc finality or payment confirmation. - free public feed reference; no purchase or creator reward.
Wikipedia article on general concept of finality, not specific to Arc or payment confirmation. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Dictionary page for 'conditions', unrelated to Arc finality. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Article on Circle's Arc and deterministic finality; likely covers definition, timing, and mechanisms. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.025000 fetch-budget caps, so this proposal stays unspent.
Dictionary definition of 'finality', not specific to Arc or payment confirmation. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Dictionary definition of 'conditions', unrelated to Arc finality. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Arc blog on cross-border payments; may discuss finality in payment context, but less directly focused. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.025000 fetch-budget caps, so this proposal stays unspent.
Ethereum single slot finality article, not about Arc. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
LinkedIn post on deterministic finality in Arc's USDC settlement; likely covers definition and timing. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.025000 fetch-budget caps, so this proposal stays unspent.
Dictionary definition of 'condition', unrelated to Arc finality. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
General article on finality in payments; may provide context but not Arc-specific. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.025000 fetch-budget caps, so this proposal stays unspent.
Facebook post about Magic: The Gathering rules, unrelated to Arc finality. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Circle documentation on finality and block confirmations; includes Arc testnet data, relevant to timing and mechanisms. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.025000 fetch-budget caps, so this proposal stays unspent.
Dictionary definition of 'conditions', unrelated to Arc finality. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Circle blog on USDC on Arc; mentions deterministic settlement finality, relevant to definition and mechanisms. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.025000 fetch-budget caps, so this proposal stays unspent.
California court rule on finality, unrelated to Arc payment confirmation. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
General payment finality article; may provide comparative context but not Arc-specific. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.025000 fetch-budget caps, so this proposal stays unspent.
Dictionary definition of 'condition', unrelated to Arc finality. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
The preview is about ARC Pay, a travel industry payment processing product, not Arc finality for payment confirmation. No target is worth investigating. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
The preview discusses the finality of death in grief, unrelated to Arc finality for payments. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
The preview mentions finality and sub-second settlement, which could address targets 1 and 2 (time to finality and mechanisms). The original page may contain relevant details. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.025000 fetch-budget caps, so this proposal stays unspent.
The preview is a weather forecast, unrelated to Arc finality. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
The preview is about Keryx release notes with documentation changes, not Arc finality. No target is worth investigating.
The preview is about recovering a Keryx paid research job, unrelated to Arc finality. No target is worth investigating.
READ Deterministic finality and settlement - Arc Docs - selected original public page, 0 USDC; not a cache hit.
Read extracted public text from https://docs.arc.io/arc/concepts/deterministic-finality - S1; quote matching establishes source grounding, not fact verification.
READ Payment Systems | Comptroller's Handbook - selected original public page, 0 USDC; not a cache hit.
Public page unavailable (transport-unavailable); no evidence admitted. Continuing research.
READ Arc deterministic finality: why it matters for payments - selected original public page, 0 USDC; not a cache hit.
Read extracted public text from https://superapp.spendthebits.com/insights/arc-deterministic-finality-payments - S2; quote matching establishes source grounding, not fact verification.
Sub-claim "What is the definition of Arc finality in the context of pay…": 100% covered by S1 — S1 explicitly defines Arc finality as deterministic: every transaction is either unconfirmed or final, with no intermediate state; once more than two-thirds of validators sign off on a block, that block is irreversible; every transaction in a committed block is immediately and irreversibly settled; no confirmation windows, no reorganization risk, no probabilistic uncertainty. This fully answers the definition in the context of payment confirmation.
Sub-claim "How long does it take for a payment to reach finality on Arc…": 100% covered by S1 — S1 states Arc's deterministic finality delivers irreversible transaction settlement in under one second, and the Malachite BFT consensus finalizes blocks in under one second, with a comparison table showing Arc <1 s. This directly answers the time to finality.
Sub-claim "What are the conditions or mechanisms that ensure finality o…": 100% covered by S1 — S1 explains the mechanism: Arc uses a Byzantine Fault Tolerant (BFT) consensus protocol (Malachite BFT); once more than two-thirds of validators sign off on a block, that block is irreversible; every transaction in a committed block is immediately and irreversibly settled. This fully covers the conditions/mechanisms ensuring finality.
Sub-claim "What are the risks or limitations of relying on Arc finality…": 0% covered — Neither S1 nor S2 addresses risks or limitations of relying on Arc finality for small payments. S1 only states benefits (no retry logic, rollback mechanisms, confirmation-count thresholds) and S2 mentions low fees and zero reorganization risk, but no risks or limitations are discussed. This sub-claim is entirely unanswered.
The first three sub-claims are fully covered by S1. The fourth sub-claim on risks/limitations has zero coverage. Among the skipped sources, the following are free and likely to address risks or limitations of Arc finality for small payments: 'Deterministic Finality in Arc's USDC Settlement Process' (public:web:e8e404...), 'Day 7: What Is “Finality,” and Why Does Sub-Second ...' (public:web:034599...), and 'Deep Dive: Why Circle Built Arc and How It Changes Payments' (public:web:6035eb...). These are prioritized because their previews suggest discussion of settlement nuances, sub-second finality details, and potential limitations. All are free, so they fit within the remaining budget of 0.025.
READ original public page https://www.linkedin.com/posts/dan-nguyen-031b1427a_so-far-weve-looked-at-how-usdc-works-inside-activity-7493888948210036736-2Kui, 0 USDC - S3
Public gap read unavailable (transport-unavailable); claim remains unknown.
READ original public page https://www.fintechwrapup.com/p/deep-dive-why-circle-built-arc-and, 0 USDC - S4
Final check — "What is the definition of Arc finality in the context of pay…": 100% assessed by S1, S2, S3, S4
Final check — "How long does it take for a payment to reach finality on Arc…": 100% assessed by S1, S2, S3, S4
Final check — "What are the conditions or mechanisms that ensure finality o…": 100% assessed by S1, S2, S3
Final check — "What are the risks or limitations of relying on Arc finality…": 10% assessed by S2, S3
Final coverage assessment — S1 and S2 directly define Arc finality as deterministic, irreversible settlement with no intermediate states, achieved via BFT consensus requiring >2/3 validator signatures, and occurring in under one second. S3 adds the nuance that finality occurs at block commit, not submission. S4 corroborates sub-second finality and no reorgs. Risks/limitations for small payments are not explicitly addressed in any source; only general benefits and fee predictability are mentioned. The assessment does not establish a complete supported answer for every requested part.
Synthesizing a grounded answer from 4 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
Delivering 4 summary sentence(s), each tied to one checked verbatim excerpt; complete synthesis remains unverified.
Source-matched public excerpt (no creator reward) — S1, research target 1, proposed support 100% (estimate, not entailment): “Arc provides deterministic finality: every transaction is either unconfirmed or final, with no intermediate state.”
Source-matched public excerpt (no creator reward) — S1, research target 2, proposed support 100% (estimate, not entailment): “Arc’s deterministic finality delivers irreversible transaction settlement in under one second.”
Source-matched public excerpt (no creator reward) — S1, research target 3, proposed support 100% (estimate, not entailment): “This guarantee comes from the network’s consensus layer, which uses a Byzantine Fault Tolerant (BFT) consensus protocol—once more than two-t…”
Source-matched public excerpt (no creator reward) — S3, research target 4, proposed support 80% (estimate, not entailment): “Arc is also designed for sub-second settlement, but that does not mean every stage of a payment or crosschain workflow finishes within the s…”
Prepared a sentence-cited summary from 2 source(s)
Confidence: Low — Each summary sentence is tied to a verbatim excerpt and model-checked; completeness and independent factual correctness remain unverified. Evidence assessment: 1 sub-claim remains below the evidence threshold.
arc.io contributed 75% - free public reference; reward share withheld
linkedin.com contributed 25% - free public reference; reward share withheld
Keryx operating fee withheld: reviewed authority, unclaimed-source proof or funding capacity is unavailable. The answer remains available.
Done. Spent $0 across 0 confirmed/simulated payment(s) to creators.
Sign in with the original report owner to review its decisions.
Read checkpoints
Read checkpoint evidence is unavailable for this report. Historical, private and unsupported native runs are not reconstructed.
Portable research receipt
Take the evidence trail with you
One deterministic JSON bundle binds the answer, visible decisions, exact article versions, claim evidence and a Circle-settlement snapshot under SHA-256. Retain the digest to detect later changes; the self-check is not a publisher or Keryx signature.
Recorded purchase outcomes
Did the exact article versions bought for this answer appear in its citations? This view scores retained BUY decisions against payment observations recorded in the same dispatch trace.
Recorded settlement bookkeeping only; Circle and chain settlement have not been independently rechecked here.
This is a partial retained trace sample, not a full payment ledger. An absent matching payment does not prove that no payment occurred; excluded and unconfirmed costs remain unknown.
- Recorded network
- eip155:5042
- Dispatch recorded at
- 2026-10-12T23:02:20.756Z
Participant cohort: unknown. No outside-customer usage is inferred.
0 scored exact-version purchases from 0 recorded BUY decisions; 0 BUY decisions unscored. 0 of 0 trace payment observations excluded.
Each unique source + item + content version with positive matching recorded settled access counts once. Duplicate BUYs, missing identities, zero/unconfirmed access and incompatible payment observations cannot create a scored purchase. CACHE and SKIP decisions are outside this sample.
- Exact-version citation hit rate
- Unmeasured
- Recorded access cost of uncited purchases
- Unmeasured
No scored purchases; the hit rate is unmeasured.
Counts only scored purchases. Descriptive access cost, not causal regret or proof that the purchase was useless.
Predicted value and observed citations
Bins compare the recorded predicted value with citation occurrence in this one dispatch. Small samples do not validate a probability model.
| Value band | Purchases | Predicted mean (0–1) | Citation rate |
|---|---|---|---|
| 0–0.2 | 0 | Unmeasured | Unmeasured |
| 0.2–0.4 | 0 | Unmeasured | Unmeasured |
| 0.4–0.6 | 0 | Unmeasured | Unmeasured |
| 0.6–0.8 | 0 | Unmeasured | Unmeasured |
| 0.8–1 | 0 | Unmeasured | Unmeasured |
Missed value, cost per supported claim, budget alternatives and counterfactual outcomes are unmeasured. No extra reading or learning was performed.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.