We need a graceful stop procedure for a Node worker on Windows. Use https://nodejs.org/api/process.html#signal-events and https://nodejs.org/api/process.html#event-exit to give a shutdown checklist covering stopping new jobs, finishing or journaling in-flight work, async cleanup and a hard deadline. Distinguish Windows signal limitations and the process exit event from POSIX expectations. Mark unproven application design advice explicitly.
10/4/2026, 11:38:10 PM · llm:deepseek:deepseek-v4-flash
> ⚠ Low confidence — Only source excerpts are delivered; complete synthesis and per-assertion support remain unverified. Evidence assessment: 6 sub-claims remain below the evidence threshold within budget. Treat this as provisional.
Source excerpts only. The draft is withheld as a conclusion; complete synthesis is unverified. Qualifying source excerpts are quoted below. Research targets are topics to investigate, not established conclusions.
Research target 1
Requested topic (unverified): “What does the Node.js process documentation say about signal events, including which signals are supported or limited on Windows compared with POSIX?”
- “Windows does not support signals so has no equivalent to termination by signal, but Node.js offers some emulation with process.kill(), and subprocess.kill():”
Research target 2
Requested topic (unverified): “What does the Node.js process documentation say about the process exit event, including how it differs from signal-based termination expectations on POSIX?”
Evidence gap: no qualifying excerpt for this research target.
Research target 3
Requested topic (unverified): “What checklist steps does the Node.js process documentation support for stopping new jobs during a graceful shutdown?”
- “Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding scheduling any additional work for the event loop:”
Evidence gap: the recorded assessment remains below the support threshold for this target.
Research target 4
Requested topic (unverified): “What checklist steps does the Node.js process documentation support for finishing or journaling in-flight work during a graceful shutdown?”
- “Calling process.exit() will force the process to exit as quickly as possible even if there are still asynchronous operations pending that have not yet completed fully, including I/O operations to process.stdout and process.stderr.”
Evidence gap: the recorded assessment remains below the support threshold for this target.
Research target 5
Requested topic (unverified): “What checklist steps does the Node.js process documentation support for asynchronous cleanup during a graceful shutdown?”
- “Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding scheduling any additional work for the event loop:”
Evidence gap: the recorded assessment remains below the support threshold for this target.
Research target 6
Requested topic (unverified): “What checklist steps does the Node.js process documentation support for enforcing a hard deadline during a graceful shutdown?”
Evidence gap: no qualifying excerpt for this research target.
Research target 7
Requested topic (unverified): “Which parts of the requested shutdown checklist are unproven application design advice rather than documented Node.js process behavior?”
Evidence gap: no qualifying excerpt for this research target.
Excerpts establish source grounding, not factual truth, entailment or whole-paper coverage. Support and coverage are estimates, not certification of a complete answer. Source statements may be wrong or conflicting. Draft conclusions are withheld; inspect the original text and obtain further review. 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.
- “How to Handle SIGTERM and Graceful Shutdown Code Reference”: 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.
- “Process Node.js v26.10.0 Documentation”: the extracted text was truncated. Read the missing section of the same version before making whole-document conclusions; retain this snapshot for comparison.
- “Node.js Process Lifecycle: Normal Behavior, Startup, Signals, and Shutdown”: the extracted text was truncated. Read the missing section of the same version before making whole-document conclusions; retain this snapshot for comparison.
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 does the Node.js process documentation say about signal events, including which signals are supported or limited on Windows compared with POSIX?”
80% estimated“Windows does not support signals so has no equivalent to termination by signal, but Node.js offers some emulation with process.kill(), and subprocess.kill():” [S1] Process | Node.js v26.10.0 Documentation
Requested topic (unverified): “What does the Node.js process documentation say about the process exit event, including how it differs from signal-based termination expectations on POSIX?”
0% estimatedNo qualifying excerpt recorded
Requested topic (unverified): “What checklist steps does the Node.js process documentation support for stopping new jobs during a graceful shutdown?”
10% estimated“Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding scheduling any additional work for the event loop:” [S1] Process | Node.js v26.10.0 Documentation
Requested topic (unverified): “What checklist steps does the Node.js process documentation support for finishing or journaling in-flight work during a graceful shutdown?”
10% estimated“Calling process.exit() will force the process to exit as quickly as possible even if there are still asynchronous operations pending that have not yet completed fully, including I/O operations to process.stdout and process.stderr.” [S1] Process | Node.js v26.10.0 Documentation
Requested topic (unverified): “What checklist steps does the Node.js process documentation support for asynchronous cleanup during a graceful shutdown?”
20% estimated“Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding scheduling any additional work for the event loop:” [S1] Process | Node.js v26.10.0 Documentation
Requested topic (unverified): “What checklist steps does the Node.js process documentation support for enforcing a hard deadline during a graceful shutdown?”
0% estimatedNo qualifying excerpt recorded
Requested topic (unverified): “Which parts of the requested shutdown checklist are unproven application design advice rather than documented Node.js process behavior?”
0% estimatedNo qualifying excerpt recorded
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. 3 targets already had no inspectable excerpts.
What does the Node.js process documentation say about signal events, including which signals are supported or limited on Windows compared with POSIX?
1 recorded excerpt remain.
Inspect remaining excerpts
“Windows does not support signals so has no equivalent to termination by signal, but Node.js offers some emulation with process.kill(), and subprocess.kill():”
S1 · nodejs.org · Process | Node.js v26.10.0 Documentation · version a150a1e5cc16719f37019c87e1959f28e2c0ecef9f818f324270aa988eabed60
What does the Node.js process documentation say about the process exit event, including how it differs from signal-based termination expectations on POSIX?
No inspectable excerpts in the original report.
What checklist steps does the Node.js process documentation support for stopping new jobs during a graceful shutdown?
1 recorded excerpt remain.
Inspect remaining excerpts
“Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding scheduling any additional work for the event loop:”
S1 · nodejs.org · Process | Node.js v26.10.0 Documentation · version a150a1e5cc16719f37019c87e1959f28e2c0ecef9f818f324270aa988eabed60
What checklist steps does the Node.js process documentation support for finishing or journaling in-flight work during a graceful shutdown?
1 recorded excerpt remain.
Inspect remaining excerpts
“Calling process.exit() will force the process to exit as quickly as possible even if there are still asynchronous operations pending that have not yet completed fully, including I/O operations to process.stdout and process.stderr.”
S1 · nodejs.org · Process | Node.js v26.10.0 Documentation · version a150a1e5cc16719f37019c87e1959f28e2c0ecef9f818f324270aa988eabed60
What checklist steps does the Node.js process documentation support for asynchronous cleanup during a graceful shutdown?
1 recorded excerpt remain.
Inspect remaining excerpts
“Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding scheduling any additional work for the event loop:”
S1 · nodejs.org · Process | Node.js v26.10.0 Documentation · version a150a1e5cc16719f37019c87e1959f28e2c0ecef9f818f324270aa988eabed60
What checklist steps does the Node.js process documentation support for enforcing a hard deadline during a graceful shutdown?
No inspectable excerpts in the original report.
Which parts of the requested shutdown checklist are unproven application design advice rather than documented Node.js process behavior?
No inspectable excerpts in the original report.
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] Process | Node.js v26.10.0 DocumentationPublication: nodejs.orgPublished: Not recorded |
|---|---|---|
| What does the Node.js process documentation say about signal events, including which signals are supported or limited on Windows compared with POSIX? | Recorded excerpt | Inspect 1 excerptWindows does not support signals so has no equivalent to termination by signal, but Node.js offers some emulation with process.kill(), and subprocess.kill(): |
| What does the Node.js process documentation say about the process exit event, including how it differs from signal-based termination expectations on POSIX? | No inspectable excerpt recorded | No excerpt recorded |
| What checklist steps does the Node.js process documentation support for stopping new jobs during a graceful shutdown? | Recorded excerpt | Inspect 1 excerptRather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding scheduling any additional work for the event loop: |
| What checklist steps does the Node.js process documentation support for finishing or journaling in-flight work during a graceful shutdown? | Recorded excerpt | Inspect 1 excerptCalling process.exit() will force the process to exit as quickly as possible even if there are still asynchronous operations pending that have not yet completed fully, including I/O operations to process.stdout and process.stderr. |
| What checklist steps does the Node.js process documentation support for asynchronous cleanup during a graceful shutdown? | Recorded excerpt | Inspect 1 excerptRather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding scheduling any additional work for the event loop: |
| What checklist steps does the Node.js process documentation support for enforcing a hard deadline during a graceful shutdown? | No inspectable excerpt recorded | No excerpt recorded |
| Which parts of the requested shutdown checklist are unproven application design advice rather than documented Node.js process behavior? | No inspectable excerpt recorded | No excerpt recorded |
Reference export
1 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
- 1Process | Node.js v26.10.0 Documentationnodejs.orgFree public reference · no creator payment · extracted html text (bounded excerpt)100%
Decision log · 68 steps
Breaking down: "We need a graceful stop procedure for a Node worker on Windows. Use https://nodejs.org/api/process.html#signal-events and https://nodejs.org/api/process.html#event-exit to give a shutdown checklist covering stopping new jobs, finishing or journaling in-flight work, async cleanup and a hard deadline. Distinguish Windows signal limitations and the process exit event from POSIX expectations. Mark unproven application design advice explicitly."
Identified 7 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: 4/4 planned queries attempted, 4 succeeded, 24 public page previews, 0 unavailable queries. Snippets are discovery only. Public reads spend no USDC; model and service operating costs remain separate.
Discovered 0 verified creator source(s) and 24 free public reference(s)
Claim-aware portfolio (exhaustive; bounded selection, not a claim of global optimality) selected 3/8 positive proposal(s): 3 free/cache selections + 0 paid fresh selections, predicting 7/7 claim(s) above the evidence floor with $0.000000/$0.015000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (7/7); paid reading may proceed within the budget.
This is the exact Node.js process documentation page cited in the question (nodejs.org/api/process.html). The preview already shows the Windows signal limitation text ('Windows does not support signals so has no equivalent to termination by signal, but Node.js offers some emulation with process.kill()') and SIGHUP-on-Windows behavior, directly supporting the Windows-vs-POSIX signal distinction and the process exit event sections. Free public read, so CACHE (read the original page). - 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, 4, 5, 6, 7; 0 fetch USDC, 1 attention slot).
The preview explicitly warns that Windows has no real POSIX signal model and Node only emulates a few signal names, recommending a programmatic shutdown trigger (e.g. IPC from a parent). This directly supports the Windows signal-limitation and checklist-design claims. Free public read. - 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, 7; 0 fetch USDC, 1 attention slot).
Preview covers stopping new work before draining, draining in-flight work with a deadline, and a single canonical shutdown function for SIGTERM/SIGINT — matching the checklist claims for stopping new jobs, finishing in-flight work, and hard deadline. Free public read. - 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, 6; 0 fetch USDC, 1 attention slot).
Deno docs preview shows a deadline safety-net timer, stopping the listener so no new connections are accepted, draining in-flight requests, and clearing timers/signal listeners so the event loop can exit — relevant to stopping new jobs, async cleanup, and hard deadline checklist steps (cross-runtime but conceptually transferable). Free public read. - 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.015000 fetch-budget caps, so this proposal stays unspent.
GitHub issue preview states that on Windows child.kill('SIGTERM') is implemented by Node as forceful, abrupt termination, so graceful cleanup is skipped — concrete evidence for the Windows signal limitation claim. Free public read. - 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.015000 fetch-budget caps, so this proposal stays unspent.
Preview discusses letting the process exit naturally via process.exitCode rather than calling process.exit(), and the event loop draining when no work remains — relevant to the process exit event and async cleanup/hard-deadline design claims. Free public read. - 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.015000 fetch-budget caps, so this proposal stays unspent.
Preview contains a signal table (SIGHUP/SIGINT/SIGQUIT/SIGKILL, handleable vs not, Node default actions) useful for distinguishing handleable signals from SIGKILL and for the POSIX-vs-Windows framing. Free public read. - 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.015000 fetch-budget caps, so this proposal stays unspent.
Preview explains SIGTERM is listenable/ignorable unlike SIGKILL and that graceful shutdown releases resources like file handles and DB connections, supporting the in-flight/async cleanup checklist claims. Free public read. - 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.015000 fetch-budget caps, so this proposal stays unspent.
Preview is a basic SIGTERM handler calling server.close() then process.exit(0); it is redundant with the official Node docs and the more complete graceful-shutdown guides already selected, and adds little on Windows limitations or the exit event. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Preview is a bare Express/Kubernetes shutdown gist with no substantive text on Windows signals, exit event, or deadline handling; redundant with better sources. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Kubernetes exit-code-143 article is about SIGTERM in K8s, not Node.js process semantics or Windows signal limitations; off-topic for the cited Node docs claims. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
ASP.NET Core graceful shutdown is a different runtime; its generic 'stop accepting new work' framing is already covered by the Node-specific sources. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Python asyncio signal-handler article is a different language/runtime and does not address Node.js process signals, Windows limitations, or the exit event. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Note about Node stdout sync/async on Windows vs POSIX is tangential to shutdown signals and the exit event; not needed for the checklist claims. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
GeeksforGeeks signal-events page is a secondary tutorial; the official Node process docs already cover signal events more authoritatively, so this is redundant. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Medium process-events guide is generic and redundant with the official docs and the more detailed shutdown guides already selected. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Red Hat article on Node non-blocking I/O is about event-loop architecture, not shutdown signals, Windows limitations, or the exit event. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
StackOverflow question on Windows equivalent of process.on('SIGINT') is topically relevant, but the preview is only a question stub and the official Node docs plus the Node lifecycle source already cover the Windows signal limitation more reliably. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Quora question about Node on Windows vs Linux process spawning is vague and not about signal handling or the exit event. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
node-ipc npm package page is about IPC transport, not Node process signal semantics or shutdown checklist steps. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Reddit thread about Windows events vs Linux is unrelated to Node.js process signals and shutdown. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Preview only hints at logging before process termination; too thin to add value beyond the official exit-event documentation already selected. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Preview mentions SIGTERM vs SIGKILL and process.exit() but is a secondary article redundant with the official Node docs and RisingStack source already chosen. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Reddit deep-dive preview is fragmentary and secondary; the official Node docs and dedicated guides already cover the same ground. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
READ Process | Node.js v26.10.0 Documentation - selected original public page, 0 USDC; not a cache hit.
Read extracted public text from https://nodejs.org/api/process.html - S1; quote matching establishes source grounding, not fact verification.
READ Node.js Process Lifecycle: Normal Behavior, Startup, Signals, and Shutdown - selected original public page, 0 USDC; not a cache hit.
Read extracted public text from https://www.thenodebook.com/node-arch/node-process-lifecycle - S2; quote matching establishes source grounding, not fact verification.
READ How to Handle SIGTERM and Graceful Shutdown | Code Reference - selected original public page, 0 USDC; not a cache hit.
Public page unavailable (transport-unavailable); no evidence admitted. Continuing research.
Sub-claim "What does the Node.js process documentation say about signal…": 70% covered by S1 — S1 directly states signal events are emitted on receiving a signal and references POSIX signal names, notes SIGHUP on Windows when console closes with unconditional termination ~10s later, and states Windows does not support signals so has no equivalent to termination by signal, with some emulation via process.kill(). This answers the core Windows-vs-POSIX limitation. Small gap: no full enumeration of supported signals or SIGINT/SIGTERM Windows specifics beyond the general statement.
Sub-claim "What does the Node.js process documentation say about the pr…": 30% covered by S1 — S1 provides process.exit() forcing exit despite pending async work and recommends setting process.exitCode to exit naturally, which is related to exit behavior, but the supplied passages do not directly describe the 'exit' event itself or contrast it with POSIX signal termination. Topical context only.
Sub-claim "What checklist steps does the Node.js process documentation …": 10% covered by S1 — S1 mentions avoiding scheduling additional work for the event loop when using process.exitCode, which is adjacent, but no explicit procedure for stopping new jobs (e.g., closing listeners/queues) is supplied. Topical context only.
Sub-claim "What checklist steps does the Node.js process documentation …": 10% covered by S1 — S1 notes process.exit() abandons pending asynchronous operations and recommends letting the event loop drain, which implies finishing work, but no explicit finish-or-journal checklist is provided. Topical context only.
Sub-claim "What checklist steps does the Node.js process documentation …": 20% covered by S1 — S1's guidance to set process.exitCode and avoid scheduling additional work so the process exits naturally is relevant to async cleanup, but no explicit async cleanup steps are documented in the supplied passages. Topical context only.
Sub-claim "What checklist steps does the Node.js process documentation …": 10% covered by S1 — S1 mentions Windows unconditionally terminating Node.js about 10 seconds after SIGHUP, which is a platform deadline, but no documented hard-deadline enforcement procedure is supplied. Topical context only.
Sub-claim "Which parts of the requested shutdown checklist are unproven…": 40% covered by S1, S2 — S1 and S2 provide some documented behavior (process.exit() abandons async work; prefer process.exitCode; reserve process.exit() for hard timeouts/fatal errors) that helps distinguish documented behavior from advice, but the supplied passages do not systematically mark which checklist items are unproven application design advice. Partial.
Coverage is adequate for the core documented Windows signal limitation (0.7) and partial for distinguishing advice (0.4). Remaining gaps concern the process 'exit' event and explicit checklist steps for stopping new jobs, finishing/journaling in-flight work, async cleanup, and hard deadlines. However, the remaining budget is only 0.015, and all skipped sources are priced at 0, so no affordable source can be bought; shouldBuyMore is false because no purchase is possible within budget. The skipped sources also appear to be third-party or non-Node-process references rather than the requested Node.js process documentation.
Final check — "What does the Node.js process documentation say about signal…": 80% assessed by S1
Final check — "What does the Node.js process documentation say about the pr…": 60% assessed by S1
Final check — "What checklist steps does the Node.js process documentation …": 10% assessed by S1
Final check — "What checklist steps does the Node.js process documentation …": 10% assessed by S1
Final check — "What checklist steps does the Node.js process documentation …": 20% assessed by S1
Final check — "What checklist steps does the Node.js process documentation …": 10% assessed by S1
Final check — "Which parts of the requested shutdown checklist are unproven…": 70% assessed by S1
Final coverage assessment — The supplied Node.js process documentation excerpts directly answer the signal-event and exit-event sub-claims, including Windows signal limitations and the process.exit/exitCode distinction. They do not document a shutdown checklist for stopping new jobs, finishing or journaling in-flight work, asynchronous cleanup, or a hard deadline; those are application design recommendations. The second source is mostly unrelated or only tangentially mentions shutdown deadlines and process.exitCode, so it provides little direct support. The assessment does not establish a complete supported answer for every requested part.
Synthesizing a grounded answer from 2 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
Delivering qualified source excerpts; complete synthesis and per-assertion support remain unverified.
Below support/reward gate — S1, research target 1, proposed support 30% (estimate, not entailment): “Signal events will be emitted when the Node.js process receives a signal.”
Source-matched public excerpt (no creator reward) — S1, research target 1, proposed support 90% (estimate, not entailment): “Windows does not support signals so has no equivalent to termination by signal, but Node.js offers some emulation with process.kill(), and s…”
Below support/reward gate — S1, research target 2, proposed support 20% (estimate, not entailment): “Calling process.exit() will force the process to exit as quickly as possible even if there are still asynchronous operations pending that ha…”
Below support/reward gate — S1, research target 2, proposed support 20% (estimate, not entailment): “Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding sc…”
Source-matched public excerpt (no creator reward) — S1, research target 3, proposed support 50% (estimate, not entailment): “Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding sc…”
Source-matched public excerpt (no creator reward) — S1, research target 4, proposed support 40% (estimate, not entailment): “Calling process.exit() will force the process to exit as quickly as possible even if there are still asynchronous operations pending that ha…”
Source-matched public excerpt (no creator reward) — S1, research target 5, proposed support 40% (estimate, not entailment): “Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding sc…”
Below support/reward gate — S1, research target 6, proposed support 30% (estimate, not entailment): “It can have a listener installed, however Node.js will be unconditionally terminated by Windows about 10 seconds later.”
Prepared source excerpts citing 1 source(s); complete synthesis is unverified
Confidence: Low — Only source excerpts are delivered; complete synthesis and per-assertion support remain unverified. Evidence assessment: 6 sub-claims remain below the evidence threshold.
nodejs.org contributed 100% - free public reference; reward share withheld
Done. Spent $0 across 0 confirmed/simulated payment(s) to creators.
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.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.