Illustrative deliverable · checked October 4, 2026
Three claims. Original references. A clear next action.
A source-review record for English technical content. Each finding preserves the original claim, the reference that bears on it, its applicable conditions and what still needs review.
C1 · Revise unit notation
Binary and decimal capacity
Original claim
One MiB equals 1,000,000 bytes.
Reference and location
NIST: Binary prefixes · “Examples and comparisons with SI prefixes,” mebibyte and megabyte rows.
Source comparison
The comparison distinguishes MiB (1,048,576 bytes) from MB (1,000,000 bytes). The original sentence combines the binary symbol with the decimal quantity.
Suggested wording
One MiB equals 1,048,576 bytes. If the intended quantity is decimal, use “One MB equals 1,000,000 bytes.”
Conditions and remaining checks
This checks unit definitions. A product's storage label, capacity reporting or reserved space must be checked against that product's documentation; the definition alone does not establish its actual capacity.
C2 · Revise error behavior
HTTP status and a fetch promise
Original claim
The fetch() promise automatically rejects when the server returns HTTP 404.
An HTTP 404 response alone does not reject the fetch promise. The request can fulfill with a Response whose status the caller must inspect. Network failures and invalid schemes are separate error cases.
Suggested wording
When fetch receives an HTTP 404 response, check response.status or response.ok and handle it explicitly; the status alone does not reject the fetch promise.
Conditions and remaining checks
This describes the Fetch API. Application wrappers may explicitly throw on HTTP errors. Cancellation and later response-body parsing failures also require separate review. No client application has been run for this example.
C3 · Wording supported within stated scope
Invalid JSON text
Original claim
JSON.parse() throws a SyntaxError when its input string is not valid JSON.
The documented exception matches the claim about an invalid JSON input string. Preserve the distinction between invalid JSON text and an exception thrown by other application code.
Suggested wording
Keep the original sentence with the reference. Do not extend it to claim that every exception in a JSON-processing workflow is a SyntaxError.
Conditions and remaining checks
No reviver callback or application error handler was tested. Runtime behavior for a particular application needs its own test; this is a documentation comparison.
What a scoped pilot would deliver
Up to three agreed claims from authorized, public English technical material.
Original references and locations, relevant conditions, wording suggestions and unresolved issues for each claim.
A dated record of research assistance and any separately agreed human review.
One clarification round within the original scope.
Scope, price, payment recipient, timing, cancellation and material handling must be agreed before an order is accepted. Source gaps can remain unresolved. Medical, legal and investment advice, execution of customer systems and report certification are outside this pilot.
Spark's automatic Trust State is a separate evidence result. This sample does not change a KNE knowledge record, promote a source or turn a documentation comparison into certified knowledge.